New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runTheMatrix.py -i all whitelists CERN even if files are elsewhere #22278
Comments
A new Issue was created by @wmtford Bill Ford. @davidlange6, @Dr15Jones, @smuzaffar, @fabiocos can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign pdmv |
New categories assigned: pdmv @fabozzi,@prebello,@GurpreetSinghChahal you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@fabiocos PdmV has been dealing with it so far. It is an eventual issue, not always happening. |
-1 |
@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos |
Hi, the command line option --ibeos introduced recently by @smuzaffar with PR #22072 |
I would like to note that an even more common command does not work as intended:
which is suggested as a test before submitting any PR. As a result, a user cannot reproduce all of the PR integration tests. As an example from a recent PR, the workflow
executes
which gives no results when run by a user, but somehow the same command returns a non-zero list of files when run within the official PR tests. From an earlier reply, I suppose that this happens because the user does not have the same stale cache that is used by the PR integration tests. If no code changes will be implemented, may I suggest transferring the files used by the integration tests back to T2_CH_CERN using a PhEDEx user category that is not auto-managed to avoid being removed by the dynamic data placement algorithm? |
@christopheralanwest as [1] shows, there is some [1] https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-22262/26154/runTheMatrix-results/4.22_RunCosmics2011A+RunCosmics2011A+RECOCOSD+ALCACOSD+SKIMCOSD+HARVESTDC/cmdLog (ctrl-f 'ibeos') |
With the --ibeos option I can successfully run runTheMatrix.py as a user on lxplus. On other cites (cmslpc at FNAL, or my usual T3_US_COLORADO), the dasquery step works, but then step2 fails, presumably because the ibeos environment isn't compatible with these non-CERN sites: |
@wmtford , can you please provide the log file of the failed tests with --ibeos? |
Yes, here is the output of runTheMatrix.py: |
@smuzaffar and @wmtford @carolinecollard for your information. |
@prebello , T2_CH_CERN restriction was added to make sure that we transfer dataset/blocks to CERN under ib-relval group. This is not needed any more as now IBs/PR use files from ibeos area. I have no objections on dropping this restriction or adding a command-line option to drop this. Let me know which option whould you prefer (adding new command-line option is safe though)? |
I think @prebello left PdmV since some time. |
Thanks for pointing this to us. Adding new command-line would be a good option. Could you provide the PR? @smuzaffar |
#31535 adds |
Some workflows in runTheMatrix.py with the recycle option seek a GEN_SIM dataset that exists only at FNAL. The dasquery step fails because the command contains the requirement site=T2_CH_CERN. Could a command-line option --allsites, valid in conjunction with -i, be added to runTheMatrix.py that would allow the user of suppress this site requirement?
For example, in CMSSW_10_0_0_pre2 the command
runTheMatrix.py --command=--number=10 -w 2017 -l 10859.0 -i all
generates at step1
dasgoclient --limit 0 --query 'file dataset=/RelValQCD_Pt_3000_3500_13/CMSSW_10_0_0_pre2-100X_upgrade2018_realistic_v1-v1/GEN-SIM site=T2_CH_CERN'
But looking in DAS I find that this dataset exists only at T1_US_FNAL.
The query is generated in
Configuration/PyReleaseValidation/python/MatrixUtil.py
where we find
I can run successfully by reversing the comments in these two pairs of lines.
The text was updated successfully, but these errors were encountered: