Simplify Data Workflows in Tests (No JSON Check)#49020
Simplify Data Workflows in Tests (No JSON Check)#49020AdrianoDee wants to merge 1 commit intocms-sw:masterfrom
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49020/46220 |
|
please test |
|
A new Pull Request was created by @AdrianoDee for master. It involves the following packages:
@AdrianoDee, @DickyChant, @Moanwar, @antoniovagnerini, @miquork, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummaryThe workflows 2025.0010001, 2025.0000001, 2024.0040001, 2024.0030001, 2024.0020001, 2024.0010001, 2024.0000001, 2023.0020001 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
|
|
|
please test |
|
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummaryThe workflows 2025.0010001, 2025.0000001, 2024.0070001, 2024.0050001, 2024.0040001, 2024.0030001, 2024.0020001, 2024.0010001, 2024.0000001, 2023.0020001 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
|
|
please test |
|
The golden JSONs are also available through CVMFS: If the bot has access to it, this could be a good retry option in case the EOS connection fails. |
Right! Nice, I think it does (@smuzaffar?). I would leave this fix to go in and then push the extra check on |
|
Also: are the tests stuck? |
|
+1 Size: This PR adds an extra 16KB to repository Comparison SummaryThe workflows 2025.0010001, 2025.0000001, 2024.0070001, 2024.0050001, 2024.0040001, 2024.0030001, 2024.0020001, 2024.0010001, 2024.0000001, 2023.0020001 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
|
|
+pdmv |
|
REMINDER @sextonkennedy, @mandrenguyen, @ftenchini: This PR was tested with #48999, please check if they should be merged together |
|
hold |
|
Pull request has been put on hold by @AdrianoDee |
|
Closed in favor of #49051 |
PR description:
Lately (with #48490), spurious DAS errors appear frequently in the tests (see e.g. #49014 (comment)). This is due to random glitches in accessing https://cms-service-dqmdc.web.cern.ch/CAF/certification/ when running the tests (no access to EOS is available). This results in not finding any certification JSON files to use for skimming the datasets. One possibility could be to allow for a few retries in case of failures, but I find it anyway risky.
So this PR proposes simply to skip the golden JSON check when running the tests (so when
JENKINS_PREFIXis defined).I'm opening this as a draft just until the files are copied to CERN.
PR validation:
Running the standard tests.