1. ART nightlies on Panda;

• Mostly OBSOLETE - the old nightlies page (NICOS): see rel 21, under ATN group (not GIT group); rel 20.7 nightlies are also available from this page.
• Use new ART page here.

• Use new ART page here. (Some basic info I've put together on how to navigate these new pages is available here.)

For each shift date show the NEW MRs, and any related relevant comments/questions; note down when I (or some one else) merged/closed each request, and mark the MR as done/closed by ticking the box ([x]). If an MR takes longer than a day to merge, leave it listed under the original shift date, but add comments prefaced with the date of the comment/action. Only MRs that are still active should have the box unticked ([ ]).

Therefore each MR will only appear once in the log, under the date of the day when I first became aware of it.

• OBSOLETE - the old nightlies page (NICOS): see rel 21, under ATN group (not GIT group); rel 20.7 nightlies are also available from this page.

nn/5/2018

27/6/2018

[ ] 12357 Update trig mc to 21.1.31 and.21.0.73 (opened by Julie Hart Kirk)

11.35am CI pipeline has failed (about a min. ago). Wait for it to re-run.

28/6/2018 10.52am CI pipeline running.

25/6/2018

[x] 12336 Sweeping 12026 from 21.0 to 21.0-TrigMC. rm FullChainTests (opened by Atlas Nightlybuild)

10.47am Pipeline still running. Waiting for it to complete before merging.

2.00pm Pipeline failed.

26/6/2018 7.30am Pipeline still showing as failed.

26/6/2018 11.06am Pipeline is now re-running. (Someone triggered it in the usual way by entering the comment "Jenkins please retry a build".)

26/6/2018 2.09pm CI pipeline failed (again) about an hour ago.

26/6/2018 6.11pm CI pipeline running again. I have set it to merge automatically when pipeline succeeds.

27/6/2018 11.34am CI pipeline succeeded yesterday evening at 20.08, and was automatically merged then.

16/6/2018

[x] 12172 Sweeping 12027 from 21.0 to 21.0-TrigMC. remove memleak test (opened by Atlas Nightlybuild)

8.50pm Merged OK.

15/6/2018

[x] EventOverlayJobTransforms-00-06-32-11 (requested by Andrzej Olszewski)

12.45pm Andrzej Olszewski requests updating the TrigMC-20.7.9.8.8 cache with the EventOverlayJobTransforms-00-06-32-11 tag. The only changes wrt the previous tag are config files; Andrzej has validated the changes. He thinks it is therefore safe to proceed to a build immediately, which he is requesting.

1.08pm I have added the new tag to the cache and marked it as "accepted". Have also emailed atlas-sw-release-shifters@cern.ch requesting a build without waiting for the next nightly.

17/6/2018 1.30pm Installation and distribution happened yesterday. Have now notified all concerned that the new release is available.

9/6/2018

[x] 11925 Sweeping 11771 from 21.0 to 21.0-TrigMC. 21.0 clean licenceandcopyright [InDet] (opened by Atlas Nightlybuild)

8.33pm Merged OK.

4/6/2018

[x] EventOverlayJobTransforms-00-06-32-10 (requested by Andrzej Olszewski)

Andrzej Olszewski has asked for an update to TrigMC-20.7.9.8.7, namely to update to EventOverlayJobTransforms-00-06-32-10 urgently and request a build immediately.

This cache is still managed with the old Tag Collector system. The last activity on it seems to have been in November 2016, with a couple of tags added by Tulay Donszelmann. I have checked that even if the latest tag available is -00-06-39, the one currently in the cache is -00-06-32-09 (so the update probably does not involve a huge amount of change wrt the current version). I have checked the nightlies (still being built every night) and there is nothing unusual there.

9.20am The request came from Andrzej on Friday night, but I only saw it now. He seems to request that we progress to a build without going through the usual nightly test. I have emailed him to check that this is the case, before accepting the tag and requesting the build, as there is always a risk that the build has problems otherwise.

9.36am Andrzej has replied to my email: he is happy to wait for the nightly and have the build tomorrow, if the nightly is OK.

5/6/2018 10am Checked the nightly (seems OK) and mailed Andrzej to invite him to look at the results and confirm that he wants me to go ahead with making a release out of this nightly.

6/6/2018 10.53am Andrzej has just now replied to my message and confirmed that, having looked at the test results, he is happy to go ahead with the release.

6/6/2018 11.03am I have accepted the tag into the cache, and emailed atlas-sw-release-shifters@cern.ch requesting that they make a release out of the rel_2 cache (yesterday's nightly) and install it on the Grid.

6/6/2018 11.58: Oana Vickey Boeriu (release shifter) has confirmed tha the release has been built (see details in the usual place, here), and that installation on the Grid is in progress.

6/6/2018 3.00pm (Grid deployment started 1h30 ago) Emailed developers and atlas-trig-relcoord@cern.ch to let them know that the release is now available and deployed on the Grid.

23/5/2018

[x] 11567 Pseduo-merge of Trigger ART tests to 21.0-TrigMC (opened by Tim Martin)

(What exactly is a pseudo-merge? Is this a sweep from 21.1 to TrigMC?)

12.24pm Request was opened less than an hour ago but it is showing "pipeline failed", therefore won't try to merge.

4.35pm In reply to my question as to "pseudo-merge", Tim says: "It's a made-up name for a merge which is actually committed as a cherry-pick so as to move code only from a small number of packages rather then the whole code base (as true merges do)." Therefore: also need to wait for pipeline to be successfully complete before attempting merge. (Pipeline has not yet restarted... presumably because there is no point in doing so until Tim figures out & fixes the cause of it having failed in the first place...)

5.37pm CI pipeline completed OK (even though I could not see that it was running...?) Merged OK.

18/5/2018

[x] 11457 Update trig mc to 21.1.29 and.21.0.71 (opened by Julie Kirk)

11.07am CI pipeline has been running for about 1h50m.

1.56pm Pipeline still running (4h40m so far).

3.40pm Pipeline finished OK, about one hour ago (so was around 5 hours total). Merged OK.

17/5/2018

[x] 11408 Sweeping 11383 from 21.1 to 21.0-TrigMC. ATR-18112: Configure FTKRefit for BS_idperf chain (opened by Atlas Nightly Build)

10.40am CI pipeline still running.

10.41am pipeline successfully completed (!) Merged OK.

16/5/2018

[x] 11357 add protection to FTK_DataProviderSvc to create VertexCollection even when vertexing not run (opened by John Baines)

9.23am Was merged by Tim, 10 mins ago.

15/5/2018

[x] 11138 Sweeping 11138 from 21.0 to 21.0-TrigMC. Hardware configuration improvements for FTKSim (opened by Atlas Nightly Build)

2.12pm Merged OK.

14/5/2018

[x] 11290 add j15_ftk to MC_pp_v7 (ATR-18086) (opened by Ligang Xia)

3.36pm Was only opened a few minutes ago but is already ready for merge...? No tests needed?

3.42pm There is only one commit, and it corresponds to a simple change to what appears to be a configuration file (MC_pp_v7.py; exact details/diff here). So that is probably why there is no need to re-build and re-test.

3.46pm Merged OK.

4.30pm Still "Merged", but noticed that the pipeline is now running...(?!). Not sure how this was available to Merge prior to the whole process being completed...?

15/5/2018 2.07pm CI pipeline concluded OK. Closing this logbook entry.

[x] 11287 Merge branch '21.1-FTKSIM-46' into '21.1' -- push to 21.0-TrigMC (opened by John Baines)

3.30pm CI pipeline running

15/5/2018 2.10pm CI pipeline concluded OK (yesterday). Merged OK by Tim yesterday.

11/5/2018

[x] 11180 Sweeping !11172 from 21.1 to 21.0-TrigMC. protect against seg. fault in VertexCollectionSortingTool if called with just one Vertex (opened by Atlas Nightlybuild, original author John Baines)

Merged OK, 11.21am

10/5/2018

[x] 11169 Cherry-pick of !11007 to 21.0 TrigMC (opened by John Baines)

CI pipeline still running, 3.30pm.

Merged OK, 6.33pm

[x] 11144 Cherry pick 10575 10964 into 21.0-TrigMC (opened by Claire Antel)

Merged OK, 2.14pm

[x] 11127 cherry-pick into 21.0-TrigMC of !10414 Backward compatible change to read FTK track parameters that are encoded in FP16 (half-float) format (opened by John Baines)

Merged OK, 2.10pm

[x] 11083 Update 21.0-TrigMC to release/21.0.69 (opened by Tim Martin)

Now ready to Merge, but when I try to merge it, it fails (i.e. goes back to green button "Merge") with the following message:

GitLab: File "DataQuality/DataQualityConfigurations/config/HLT/HLTidtrk/collisions_run.config" is larger than the allowed size of 2 MB.

I've alerted Tim to this, who has in turn asked colleagues with the required access level to circumvent the issue and accept the MR.

11/5/2018: now showing "There are merge conflicts", MR button greyed out.

11/5/2018: Edward Moyse accepted MR, 12.43pm.

15/6/2018

TrigMC software release coordination: PTD's logbook - May 2018

nn/5/2018

11/5/2018

10/5/2018

11083 Bla text text