Conversation
|
trigger build SBNSoftware/icaruscode@dummy-test2 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard 🚨 For more details about the failed phase, check the ci_tests ICARUS phase logs parent CI build details are available through the CI dashboard |
|
@leoaliaga (and @kindofblue99 and @vitodb) Is this PR still relevant with the semi-recent CI changes Vito made in PR #874? I just want to make sure I don't accidentally close this PR if it needs to be integrated. |
|
As far as I can tell this PR just adds an empty line to a file with the purpose to have a neutral code change to test the trigger build comment to test ICARUS code suite with the CI. |
Just for CI test