Feedback from individual steps in JSON approach

-in the log file, there is no a colored printout for each step (tra, digi, reco, AT) if it was successful -if not, the script is exited -> therefore the CI can fail now and possible problems can be spot on each new MR directly

added CI/CD Framework Simulation labels

assigned to @f.uhlig

changed milestone to %OCT23

enabled an automatic merge when the pipeline for 097dcf03 succeeds

aborted the automatic merge because target branch was updated

@f.uhlig Can you help me understand why some tests failed, because locally everything is working as expected, success/failure is according to the individual steps (I explicitly checked also for failure ;)

added 6 commits

• 097dcf03...bb2fb8db - 4 commits from branch computing:master
• 3dabfceb - safety checks if step are executed successfully
• 13cfc4a2 - cosmetics

Compare with previous version

@f.kornas,

to give you a hint, when checking the CDash page I saw that all tests are failing for the FairSoft apr21p2 and FairRoot v18.6.7. The tests pass on the same operating systems when using the newer versions nov22p1, v18.8.0.

The problem is still that the printouts are not passed to the output. One only sees the output of the shell script run_json.sh.

Okay, then I know what the problem is. Its the caller function introduced by Lucas back in time, as they work only for nov22p1, v18.8.0.

Maybe I have to reset according changes manually...

added 7 commits

• 13cfc4a2...39e6ec31 - 3 commits from branch computing:master
• add73cc4 - safety checks if step are executed successfully
• 159e526a - cosmetics
• eb2f4a09 - make compatible with fs apr21p1 and fr v18.6.7
• 2a720c93 - same for run_reco

Compare with previous version

added 1 commit

• 9f555022 - clang format

Compare with previous version

added 1 commit

• 2f554fa6 - fix fairrootfilesink compatibility to apr21p2 v18.6.7

Compare with previous version

added 7 commits

• 384380a8 - 1 commit from branch computing:master
• 25afd588 - safety checks if step are executed successfully
• 5762238b - cosmetics
• 8dd4fb53 - make compatible with fs apr21p1 and fr v18.6.7
• 69257389 - same for run_reco
• bdad209b - clang format
• cc818c54 - fix fairrootfilesink compatibility to apr21p2 v18.6.7

Compare with previous version

Compatibility to fs apr21p2 and fr v18.6.7 should be restored now, at least locally everything works.

@f.uhlig Only one job crashed, but its some timeout when loading libraries. Do you have an idea what could be the issue?

@f.kornas,

I have restarted the failing job.

Dear @f.uhlig, @p.-a.loizeau,

you have been identified as code owner of at least one file which was changed with this merge request.

Please check the changes and approve them or request changes.

added CodeOwners label

approved this merge request

added 9 commits

• cc818c54...2ba38019 - 3 commits from branch computing:master
• 99528b7e - safety checks if step are executed successfully
• e2a25a4d - cosmetics
• 30901006 - make compatible with fs apr21p1 and fr v18.6.7
• 78352e4c - same for run_reco
• 19412205 - clang format
• aff03dd1 - fix fairrootfilesink compatibility to apr21p2 v18.6.7

Compare with previous version