Externals Update, master branch (2021.03.12.)

Updated all projects to atlasexternals-1.0.103. Which has only a single update wrt. atlasexternals-1.0.102 (atlasexternals@2.0.102...2.0.103): It updates the behaviour of the atlas_generate_reflex_dictionary(...) CMake function to fix one of the issues described in ATEAM-717.

• For a more detailed explanation of the issue see: atlasexternals!824 (merged)

While the modification in the CMake code is simple, we do need to be careful with it. So I'm asking for full-build and full-unit-tests to make sure that no dictionary would be harmed in the process. (@mnowak's comment in https://its.cern.ch/jira/browse/ATEAM-717?focusedCommentId=3738119&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3738119 makes me a bit worried...)

added bugfix full-build full-unit-tests labels

changed the description

build area is cleaned as MR is labeled as full-build

This merge request affects 8 packages:

• Projects/AnalysisBase
• Projects/AthAnalysis
• Projects/AthDataQuality
• Projects/AthGeneration
• Projects/AthSimulation
• Projects/Athena
• Projects/DetCommon
• Projects/VP1Light

Affected files list will not be printed in this case

Adding @krumnack ,@jchapman ,@akraszna ,@rbianchi as watchers

added Build master review-pending-level-1 labels

Jenkins please retry a build

What happened? I assumed with full-build and full-unit-tests this long of a build would be par for the course...

No idea - it seems the jenkins pipeline died twice right after the start.

From the jenkins log:

22:55:50 “Warning: JENKINS DETERMINED THAT THE BUILD JOB FOR MR ID 336775, HASH a3550762 OS CentOS COMPILER gcc8 IS ALREADY RUNNING” 22:55:50 “Info: JOB IS RECOGNIZED AS DUPLICATE AND THEREFORE STOPPED” 22:55:50 Build step 'Execute shell' marked build as failure

@aundrus or @tsulaia do you know why jenkins stops this pipeline right away ?

Just guessing: maybe the first pipeline is indeed still running, and GitLab wrongly reports its failure? I've seen that many times in the past.

Alex should know for sure what's going on here.

I edited the description of the MR after creating it. That probably triggered a second pipeline, which Jenkins killed.

I also think that the original build is still running. (Hopefully on the tests by now...)

CI Result FAILURE (hash a3550762)

	Athena	AthSimulation	AthGeneration	AnalysisBase	AthAnalysis	DetCommon
externals
cmake
make
required tests
optional tests

Full details available on this CI monitor view
Athena: number of compilation errors 0, warnings 0
AthSimulation: number of compilation errors 0, warnings 0
AthGeneration: number of compilation errors 0, warnings 0
AnalysisBase: number of compilation errors 0, warnings 0
AthAnalysis: number of compilation errors 0, warnings 0
DetCommon: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 29842]

CI failures are not related to this MR. They were fixed in !41536 (merged) . From my perspective it is OK to merge this one. Any objections from anyone?

removed review-pending-level-1 label

added review-approved label

At this point it should be safe to merge. Note that the update is not incremental build hostile. I just wanted to make sure that with all dictionary generations re-done from scratch, we would still not see any unexpected issues.

resolved all threads

merged

mentioned in commit 6e94885b

added sweep:ignore label