-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propery locate podman images #1891
Propery locate podman images #1891
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1891 +/- ##
==========================================
- Coverage 83.99% 83.95% -0.04%
==========================================
Files 46 46
Lines 8152 8152
Branches 2170 2168 -2
==========================================
- Hits 6847 6844 -3
- Misses 836 838 +2
- Partials 469 470 +1
|
91cb49e
to
2e4eedd
Compare
I have just seen at https://github.com/common-workflow-language/cwltool/actions/runs/5937318373/job/16099520096?pr=1891 that there are several tests which are not passed now, due the error messages are apparently different. But I don't know why, because I have tried to reproduce it from command line, and it returned what it was expected:
|
@jmfernandez The test is looking for the exact phrase |
2e4eedd
to
1918418
Compare
I still don't understand the reason of the "irreproducibility" of the test failure. Along today I got the test failure at least twice when all the tests were run, but not always. And never when only the failing test is run (through In any case, I have updated the failing test case, but I'm afraid it is not the real workaround / solution. |
1918418
to
873b6f1
Compare
This approach avoids the issue about podman using "canonical" image tags just using the "inspect" subcommand.
This udocker/podman pull command was being done even when `--disable-pull` parameter is passed to `cwltool`, and it should not be needed, as all container image pulls should have happened at this point.
Also, cosmetic changes to fix some flake8 complaints.
…st second of the job running.
The failing test shows that there seems to be some kind of unpredictable slowness when When I was debugging the source of this condition I was tracing the source. Next line calls cwltool code: Line 108 in bd89c56
which ends leading to next code snippet at Lines 967 to 985 in bd89c56
I detected it was remaining stuck at line 984, whose monitoring body for this use case is at Lines 507 to 537 in bd89c56
and then it is waiting just at line 528 until the timeout happens Line 528 in bd89c56
I did a test where I removed the process termination, and it finished properly later than the timelimit. So, I raised the cwltool/tests/wf/timelimit.cwl Line 14 in bd89c56
to 20, and it started working! |
Also, I realized that the max memory usage monitoring being done was happening only once, after the first second of the process running. And that both the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @jmfernandez !
Use docker/podman/udocker inspect to check container images are already in the local registry.
Additionally, removed superfluous udocker/podman pull, which was done even when
--disable-pull
parameter is passed.This should fix issue #1884