Difference: TrigMC_Log2018_11 (15 vs. 16)

Revision 1628 Nov 2018 - PedroTeixeiraDias

Line: 1 to 1
 
META TOPICPARENT name="PTD_TrigMC_LogBook_2018"

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

Line: 22 to 22
  [x] Check nightlies
Changed:
<
<
11.23am Had a quick look at the nightlies (GIT and ATN): exact same overall test results as the previous nightly, as exected given that there were no new MRs since previous nightly.
>
>
11.23am Had a quick look at the nightlies (GIT and ATN): exact same overall test results as the previous nightly (as expected, given that there were no new MRs since previous nightly).
 
Changed:
<
<
[ ] !16299 Merge nightly/21.1/2018-11-27T2139 into the branch 21.0-TrigMC (opened by Rafal Bielski)
>
>
[x] !16299 Merge nightly/21.1/2018-11-27T2139 into the branch 21.0-TrigMC (opened by Rafal Bielski)
 
Changed:
<
<
11.05am This MR was opened about an hour ago. It is step 2 of the plan to phase out Run-2 trigger releases, to give way to the preparations for the Run-3 releases. It brings TrigMC in line with the 21.1 branch (step 1, see !16228 below, was to bring TrigMC in line with 21.0.). The CI pipeline is listed as "failed"... but based on what happened with !16228, I am guessing it could just be a communication issue (eg along the lines of can't communicate with job server, threfore job appears to have "failed" even thought it is running happily along...). (For !16228, results from the supposedly "failed" pipeline job, appeared out of nowhere several hours later... and it then turned out the pipeline had successfully passed all steps.)
>
>
11.05am This MR was opened about an hour ago. It is step 2 of the plan to phase out Run-2 trigger releases, to give way to the preparations for the Run-3 releases. It brings TrigMC in line with the 21.1 branch (step 1, see !16228 below, was to bring TrigMC in line with 21.0.). The CI pipeline is listed as "failed"... but based on what happened with !16228, I am guessing it could just be a communication issue (eg along the lines of can't communicate with job server, tehrefore job appears to have "failed" even thought it is running happily along...). (For !16228, results from the supposedly "failed" pipeline job, appeared out of nowhere several hours later... and it then turned out the pipeline had successfully passed all steps.)

3.24pm CI pipeline results have now appeared, as expected: all OK. Merged OK.

 

27/11/2018

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 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