-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
try 3 at unscheduled in 76x #10479
try 3 at unscheduled in 76x #10479
Conversation
…ed: Configuration/PyReleaseValidation/python/relval_standard.py (twice) Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py
…uration/PyReleaseValidation/python/relval_steps.py
…Configuration/PyReleaseValidation/python/relval_standard.py Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py
…lows: std, premix, pu, unsch (removed) Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py (removal of ALCAELE) Conflicts: Configuration/PyReleaseValidation/python/relval_pileup.py Configuration/PyReleaseValidation/python/relval_steps.py Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py
Conflicts: Configuration/PyReleaseValidation/python/relval_standard.py
Conflicts: Configuration/PyReleaseValidation/python/relval_steps.py
…ill come for tracked/untracked parameters
…orized away into MatrixUtil
…MS/get/hlt/3914/2.html while TLR is scrutinized
Comparison is ready The workflows 4.53 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 |
unit test problem is unrelated |
try 3 at unscheduled in 76x
'-s':'RAW2DIGI,L1Reco,RECO,EI,PAT,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@miniAODDQM', | ||
'--runUnscheduled':'', | ||
'--conditions':'auto:run2_mc', | ||
'--magField' : '38T_PostLS1', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we overriding mag field from xml here? (and in all other places)
I ran our reco tests on this
The magnetic field issue should be fixed |
@slava77 , thanks for the report, I will fix the MagFied by today. |
Combining two PRs
#10054 (cherry picked to 76x) + #10457