Bump Acts v3.0.0 -> v5.0.0; include Fatras in build

• New version includes (among other things) fix to propagator that is causing crashes in simulation
• Fatras component needed for simulation

FYI @jchapman, @mduehrss, @yfhan.

added 1 commit

• 220bace1 - Bump Acts v3.0.0 -> v5.0.0; include Fatras in build

Compare with previous version

Pinging other relevant parties: @asalzbur, @pagessin, @bschlag

Is this MR compatible with Tracking/Acts?

AE Build SUCCESS
Build logfiles are available at Jenkins [AE-MERGE-REQUEST-CC7 #444]

AE Build SUCCESS
Build logfiles are available at Jenkins [AE-MERGE-REQUEST-CC7 #445]

Right now it is not. We‘ll make the necessary changes and let you know.

I suggest holding this MR until then.

I've discussed with @corentin, who will make an MR to athena master that makes the necessary changes.

Perfect.

I hope this is not super-super urgent, right...?

I have a couple of updates in the pipeline for which I plan to create the 2.0.98 tag today. But I'd rather leave this in flight for a couple more days, until those updates have been merged into athena master.

I will also probably need a couple of day to test the Tracking/Acts with v5.0.0

@akraszna, Not "super-super" -- just "super." ;)

No, we can of course wait.

added 1 commit

• 8fd868c9 - Update forcedownload step to reflect v5.0.0 tag date

Compare with previous version

added 9 commits

• 8fd868c9...f26102cd - 7 commits from branch atlas:master
• b578774e - Bump Acts v3.0.0 -> v5.0.0; include Fatras in build
• 011a5897 - Update forcedownload step to reflect v5.0.0 tag date

Compare with previous version

AE Build SUCCESS
Build logfiles are available at Jenkins [AE-MERGE-REQUEST-CC7 #447]

AE Build SUCCESS
Build logfiles are available at Jenkins [AE-MERGE-REQUEST-CC7 #448]

Note that Athena,master now uses LCG_98python3_ATLAS_4 which contains boost-1.73.0, while atlasexternals is at LCG_97apython3_ATLAS_1 which contains boost-1.72.0.

This causes issues linking Acts in Athena packages since the former requires the exact boost version as it was compiled against (see here).

Hm, I'm not sure that boost has a stable ABI, so I'm not sure it would even be possible to loosen that restriction.

After testing myself, it seems there is in fact no issue/crash with the v3.0.0 propagation. However, we do need -DACTS_BUILD_FATRAS:BOOL=ON for Acts. If more time is needed to adapt the Tracking/Acts codes for v5.0.0, we can close this and just add ActsFatras to the build and hold off on the version-bump until later.

I have updated Tracking/Acts to work with Acts5.0.0 I am just waiting on some test to be sure everything is working as it used to. Hopefully I can open a PR for it tomorrow.

mentioned in merge request athena!40619 (merged)

I opened a MR for the update of the Tracking/Acts code : MR#40619. Which would need to go in after this is merged.

@akraszna Any word on this? Looks like athena!40619 (merged) is ready.

I was waiting for you guys to let me know when this can go in. Is it now?

Note that since last week we updated the externals of athena master twice.

• athena!40606 (merged)
• athena!40743 (merged)

So I was pretty happy with this update being delayed. But if you guys are ready now, I can give you a new tag with this included.

added 18 commits

• 011a5897...32e396cb - 16 commits from branch atlas:master
• 79ace32f - Bump Acts v3.0.0 -> v5.0.0; include Fatras in build
• 57afb13c - Update forcedownload step to reflect v5.0.0 tag date

Compare with previous version

AE Build SUCCESS
Build logfiles are available at Jenkins [AE-MERGE-REQUEST-CC7 #459]

resolved all threads

merged

mentioned in commit 89992218

Here you go: https://gitlab.cern.ch/atlas/atlasexternals/-/tags/2.0.101