tweak DeterministicMixer to work with gsl3

fixes http://lhcb-nightlies.web.cern.ch/logs/build/nightly/lhcb-lcg-dev4/1428/x86_64-centos7-gcc9-opt/LHCb/#show_Kernel_LHCbMath/Kernel_LHCbMath_128

added cleanup label

@cattanem: which architecture should I specify to test with gsl3?

added 1 commit

• 2e951743 - tweak DeterministicMixer to work with gsl3

Compare with previous version

added 1 commit

• d240d3be - tweak DeterministicMixer to work with gsl3

Compare with previous version

mentioned in merge request !2794 (merged)

assigned to @ascarabo

assigned to @cattanem

Thanks a lot!

added lhcb-lcg-dev3 lhcb-lcg-dev4 lhcb-run2-patches-dev4 labels

removed lhcb-run2-patches-dev4 label

is there a way to tell the ci-test to run the equivalent of the -dev3 or -dev4 slot, so that one can check with a lower latency? I checked using a mocked-up version in godbold (and then verified that it didn't break the gcc9-opt build), but that's not the same thing...

Let's at least test the 'standard' set of platforms:

/ci-test --merge

added ci-test-triggered label

• [2020-10-09 11:38] Validation started with lhcb-lcg-dev3#1414
• [2020-10-09 11:42] Validation started with lhcb-master-mr#1416
• [2020-10-09 11:55] Validation started with lhcb-lcg-dev3#1414
• [2020-10-09 13:24] Validation started with lhcb-lcg-dev3#1414
• [2020-10-10 00:05] Validation started with lhcb-lcg-dev4#1429
• [2020-10-10 00:05] Validation started with lhcb-lcg-dev3#1415
• [2020-10-11 00:04] Validation started with lhcb-lcg-dev3#1416
• [2020-10-11 00:13] Validation started with lhcb-lcg-dev4#1430
• [2020-10-12 00:05] Validation started with lhcb-lcg-dev4#1431
• [2020-10-13 00:05] Validation started with lhcb-lcg-dev4#1432
• [2020-10-13 00:05] Validation started with lhcb-lcg-dev3#1418

mentioned in issue lhcb-core/LbNightlyTools#74 (closed)

mentioned in issue Moore#213 (closed)

assigned to @rcurrie and unassigned @ascarabo

I have no idea why this was assigned to me - removing myself...

unassigned @cattanem

approved this merge request