TrigMC software release coordination: PTD's logbook - page for July 2018


Use reverse chronological order.

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.

Requests still open: 1 - rel 2018-07-09T2159


[ ] !NNNNN Title (opened by XYZ)


[x] !12806 Sweeping !12397 from 21.0 to 21.0-TrigMC. Update FTK AOD creation for data BS files (opened by Atlas Nightlybuild)

8.04am Request appeared overnight. Pipeline has already completed successfully. Merged OK.


[x] New TrigMC release out of r2018-07-09-T2159 (requested by John Baines)

6.35pm Around lunchtime today John requested that a new release be made out of a specific nightly (more than one week old: 9/7/2018). It is the first time that I do this for 21.0-TrigMC, under the new Gitlab system. Oleg provided a link to the instructions on how to do this. I spent some time working through the instructions, and then completed the three steps specified there: (i) Create a Jira ticket for CVMFS installation; (ii) Tag the release in git; (iii) Update the release candidate number. The actual JIRA ticket requesting the release went in at 5.48pm, and was assigned to Alessandro de Salvo; I have not heard anything back yet. I have emailed John and Oleg 10 minutes ago to let them know that the request has been submitted.

18/7/2018 8.19am On JIRA: Oana posted a message last night to tell Alessandro that the RPMs have now been copied to the official location, so that Alessandro can deploy the release. She also mentioned how I can do this the next time (see my JIRA ticket). No reply from Alessandro yet.

18/7/2018 2.34pm Alessandro has now confirmed that the installation is complete and has closed the JIRA ticket. I have emailed John and Oleg to let them know as much.

[x] !12815 version.txt: Update release candidate number to 21.5.7 (opened by myself)

6.41pm This MR was triggered by step (iii) above. CI pipeline has started (but is it really needed to waste resources on a pipeline for this entirely trivial change? Should I simply "Merge Immediately"?)

6.58pm Have looked in git for past MRs of this type (i.e. simply updating version.txt). In some cases the pipeline has been allowed to run and only then was the MR approved, but also found several cases where it seems that the MR was submitted and immediately merged, which seems to have avoided the pipeline starting. Therefore decided to approve this MR now -- seems to have merged OK. (Nevertheless, the pipeline continues to run... Next time, submit it and then immediately approve, to see if that avoids the pipeline starting in the first place.)

18/7/2018 8.10am Just out of curiosity, checked the pipeline status: completed successfully.


[x] !12721 sweeping MR 12251 to 21.0-TrigMC (opened by Tulay Cuhadar Donszelmann)

1.03pm Request was opened Friday, late. Only saw it now (Sunday). Simple sweep. Will merge next.

1.04pm Merged OK.


[x] EventOverlayJobTransforms-00-06-32-13 for the next rel., TrigMC (Requested by Andrzej Olszewski)

6.30pm (CERN) Andrzej asks that the above tag be added to TrigMC 20.7 cache, and that a build be requested immediately, as he has done all required validation and testing.

6.47pm Branch tag added to the cache (not, as AO wrote in his request) and marked as "accepted". Will ask for immediate build now.

7.21pm Update: it turns out that the next cache should indeed be was built and released almost a month ago, but - for some reason - the cache was not closed and the new one ( opened), as requested... Therefore, I have had to revert to the earlier tag (EOJT...-32-11, as it turns out), and have now asked the Release Shifters again to close this cache, open, and sweep tags from to this latest one. Only once this is done can I add the EOJT-...32-13 tag to the cache and then proceed with requesting a build and release... Waiting.

7.39pm Oana Vickey Boeriu has responded that the above requests are now done. Will check and proceed with request for new release asap.

7.45pm I have now added the EOJT-...32-13 tag to the TrigMC cache and marked it as accepted.

7.50pm I have now emailed the release shifters asking to make a release out of the cache, then close it etc...

7.54pm e-mailed Andrzej Olszewski et al to let them know we are now back on track.

11/7/2018 (CERN) 8.55am In email contact with Oana, to confirm that the release(s) from last night showing in NICOS are OK, and that she can proceed with distribution, etc. Note that there are two rel_3 showing: I am guessing that one was triggered by Oana making a release out of TrigMC and the other is the habitual nightly (they should therefore be identical - but at the moment one of them is still not finished, in the process of completing the tests).

11/7/2018 11.48am Oana has confirmed the release is now available and is awaiting Grid distribution. Have emailed the developers and atlas-trig-rel-coord accordingly.

11/7/2018 11.52am Also: have checked that has been closed and opened, as requested.


[x] !12484 Update xAODBTaggingEfficiency file to recommended for r21. Fix for ATLASRECTS-4511 (opened by Tim Martin)

12.26pm CI pipeline failed (...! Tim M describes it as a "bit of a chicken-and-egg situation"; see !12357 in June 2018 logbook page...)

1.31pm Julie requested that I go ahead and Merge, without waiting for CI pipeline, to get out of this catch-22 situation. Merged OK.

-- PedroTeixeiraDias - 28 Jun 2018

Physics WebpagesRHUL WebpagesCampus Connect • Royal Holloway, University of London, Egham, Surrey TW20 0EX; Tel/Fax +44 (0)1784 434455/437520

Topic revision: r13 - 18 Jul 2018 - PedroTeixeiraDias

This site is powered by the TWiki collaboration platformCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding RHUL Physics Department TWiki? Send feedback