-
Notifications
You must be signed in to change notification settings - Fork 100
Open
Description
We have some cases where a GHA action fails, but the log doesn't say why.
This happened first in #1605. The log of the gcc-12, C++=20 job contained lines up to the install step, but nothing else. I tried to debug this with tmate, but all was fine there. So, I disabled that job in #1605.
I see this now in #1592 with the gcc-14 job. The same "up to install" happens in https://github.com/UCL/STIR/actions/runs/17897628450/job/50890961904.
Interesting is a previous job in that PR https://github.com/UCL/STIR/actions/runs/17852412177/job/50763741374, where the log ends with
+ ctest --output-on-failure -C RelWithDebInfo
Test project /home/runner/work/STIR/STIR/build
Start 1: test_ROIs
1/71 Test #1: test_ROIs ....................................................................... Passed 0.46 sec
Start 2: test_warp_image
2/71 Test #2: test_warp_image ................................................................. Passed 0.13 sec
Start 3: test_DynamicDiscretisedDensity
3/71 Test #3: test_DynamicDiscretisedDensity .................................................. Passed 0.12 sec
Start 4: test_ScatterSimulation
Metadata
Metadata
Assignees
Labels
No labels