Advanced Tupling test: Do not rely on a reference file

Advanced Tupling test: Do not rely on a reference file as some lines appear in different order depending on platform. cc @dfazzini

Avoids random test failures as in !535 (merged)

added DPA-WP3 lhcb-run3-cleanup labels

/ci-test --merge

added testing label

added ci-test-triggered label

That's a better way to test. Nice. (I added the testing label.)

• [2021-06-28 16:42] Validation started with lhcb-master-mr#2523
• [2021-06-29 01:19] Validation started with lhcb-run3-cleanup#249
• [2021-06-30 01:15] Validation started with lhcb-run3-cleanup#250
• [2021-07-01 01:10] Validation started with lhcb-run3-cleanup#251

Hey @pkoppenb, this reminds me - in our planning (milestones and my colorful tables) we don't actually have a WP3 task for validation/testing. Shall we add one and for example link this MR to it? For sure it would be good to discuss and track unit testing for DaVinci towards proper coverage.

mentioned in merge request Phys!945 (merged)

olá @erodrigu . I though we decided not to as any new feature should be tested.

@pkoppenb It seems to me that everything is fine. Just one question: is this just a temporary solution or not? I mean, should we investigate more deeply on how to ensure the correct order of the various algorithm and then go back to the previous testing method?

changed the description

mentioned in commit 9d00383d

merged

resolved all threads