gh: Fix windows and kernel tests for gh actions #7525
Conversation
CT Test Results 3 files 143 suites 1h 36m 25s ⏱️ Results for commit 74f7ee4. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts
// Erlang/OTP Github Action Bot |
This will hopefully get rid of error messages that the disk is full.
garazdawi
force-pushed
the
lukas/gh/fix-windows-and-kernel
branch
from
74f7ee4
to
7b3aa4d
Compare
| @@ -217,7 +217,7 @@ release_tests_spec: make_emakefile | |||
| $(INSTALL_DATA) $(ERL_FILES) $(HRL_FILES) "$(RELSYSDIR)" | |||
| $(INSTALL_DATA) $(APP_FILES) $(EXTRA_FILES) "$(RELSYSDIR)" | |||
| $(INSTALL_DATA) \ | |||
| kernel.spec kernel_smoke.spec kernel_bench.spec logger.spec \ | |||
| kernel.spec kernel_smoke.spec kernel_bench.spec kernel_gh.spec logger.spec \ | |||
There was a problem hiding this comment.
is this a list determining test execution scope?
is there unnecessary overlap between kernel.spec and kernel_gh.spec?
same question. for stdlib below.
There was a problem hiding this comment.
It is a list of all files to be copied when releasing tests. There is an overlap between kernel.spec and kernel_gh.spec because it is not possible to include specs into each other (as far as I know).
$APP.spec is what is normally run, while in GH actions we run $APP_gh.spec if it exists.
|
It is merged to maint and master, this PR is however targeted at master. |
No description provided.