Adding CI for checking the build and the built image #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding CI for the Docker image will help identify what works and what doesn't. This patch adds a CI workflow, which consists of
The latter uses a separate reusable workflow and a shell script invoked within Docker. Output notebooks and log files (
*.log
) are saved as artifacts. Intermediate results are also saved, to be used in the subsequent dependent jobs.Some remarks:
a1
-a6
) do not appear to be well maintained. Moreover, I am not sure about their dependency tree, specifically which notebook requires the output of others (as represented by theneeds
andoutputs
parameters of each job). Consequently, they fail to run.4a
fails but it will be fixed in another PR.4a
notebook on GitHub does not include the limit bySCANDAL
(printedno SCANDAL
). So, I do not include3c
as a dependency for4a
, but I guess it is OK to include it to generate the limit.3a
randomly fails due to freezing in training (you may need to re-run failed jobs). A possible cause isnum_workers
passed inDataLoader
, which is by default set to 8, and causes the following warning:timeout
parameter of the reusable workflow) to catch the above freezing and to save failed notebooks. Maybe thistimeout
should be extended if there is a more time-consuming cell.See also a workflow run on my branch.