Updated refs for S29r2 after first round of validations

Corrected name of S29r2 stripping test and updated reference after changes to S29r2 after first round of validations

@erodrigu FYI - hopefully it will run ok in the nightlies.

• [2018-01-19 00:18] Validation started with lhcb-2017-patches#268
• [2018-01-20 00:17] Validation started with lhcb-2017-patches#269
• [2018-01-21 00:20] Validation started with lhcb-2017-patches#270
• [2018-01-22 00:22] Validation started with lhcb-2017-patches#271
• [2018-01-23 00:25] Validation started with lhcb-2017-patches#272
• [2018-01-24 00:20] Validation started with lhcb-2017-patches#273
• [2018-01-25 00:20] Validation started with lhcb-2017-patches#274
• [2018-01-26 00:18] Validation started with lhcb-2017-patches#275
• [2018-01-27 00:19] Validation started with lhcb-2017-patches#276
• [2018-01-28 00:18] Validation started with lhcb-2017-patches#277
• [2018-01-29 00:18] Validation started with lhcb-2017-patches#278

Hi @sreicher, there are still small differences. Are you going to update the ref file or I should go on and accept this MR. It's a minor thing. While at it, let me know the timescale for the release of the patched projects, so Stripping and then DaVinci. Thanks.

Hi @erodrigu I'll have another look right now. I'm waiting for Michael to finish one study before we can tag the Stripping, so hopefully this will happen today or Monday. We'd like to launch the second validation early next week and hence would require a DaVinci patch by then. The Stripping tag will be v11r5p2.

Ah, I guess it's because I forgot to commit my changes to the Stripping yesterday night. It should run successfully now but we'll know for sure tomorrow morning.

OK, thanks.

@sreicher, there is only an error in the nighlies. Will you update the ref, in which case I wait for your OK to merge this? Your time is my time :-).

added 6 commits

• 17e9ba53...729e9786 - 2 commits from branch 2017-patches
• fb0c8068 - Partially revert commit d29cbd.
• dd7306dc - Update ref for S29r2 test; change dependence of StrippingCache to MergedConfDB.
• 602f7db8 - Merge branch 'prepare-v42r7p2' into S29r2_update_strip_ref_after_val
• d9467b45 - Update S29r2 test ref.

Compare with previous version

@erodrigu I think we're ready to go now. Note that I merged in !144 (merged) here as I needed it to get the build of TurboCache to work when testing locally. I've also updated CMakeLists.txt and added release notes for v42r7p2 though you may want to add to that. Stripping v11r5p2 has been tagged.

Last night's nightly builds failed due to an unrelated error in GitLHCBCOND, but Sunday's were OK. The test of S29r2 in DV failed with unexpected stdout but this seems to be down to changes the 2017-patches version of LHCb vs v42r6p1. I expect we want to stick with the latter (and Phys v23r7) for the release for S29r2 anyway. Maybe we can set up the lhcb-prelease slot appropriately?

regarding today's failure, it might be related to an update happening at about the same time, see https://its.cern.ch/jira/browse/LHCBCNDB-667 Hopefully, it is only bad luck and won't repeat.

Thanks @malexand! I will prepare the patched DaVinci asap (need also to check the changes in Analysis). Seems then that MR!144 won't be necessary anymore. I will close it after checking things. Yes the stack will use Phys v23r7.

mentioned in commit 0dafa217

merged

Minor correction: I would in fact prefer to prepare a Phys v23r7p1 to pick up little things. Those are not related to Stripping but it makes sense to me to release with as much as possible, to avoid orphan code for some time, meaning code not in any release. OK with you? This of course means you have to retag your Stripping release. Please let me know. Thanks.

OK, that's fine. I'll just retag Stripping v11r5p2 and make it depend on Phys v23r7p1.

Appreciated .

Stripping v11r5p2 is now retagged.