GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.
The crash (ATR-21788) appears in this test: test_trigP1_v1Phys_ROSRate_build and this is fixed by not returning if the calo cluster collection is empty, so that the roi needed in the next algorithm is created, and so on...
Tagging @tamartin@malconad@ademaria