-
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
Workflow 180.1 fails #44536
Comments
assign generators |
New categories assigned: generators @alberto-sanchez,@bbilin,@GurpreetSinghChahal,@mkirsano,@menglu21,@SiewYan you have been requested to review this Pull request/Issue and eventually sign? Thanks |
cms-bot internal usage |
A new Issue was created by @makortel. @smuzaffar, @antoniovilela, @rappoccio, @makortel, @Dr15Jones, @sextonkennedy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
The workflow was added in #44316, that was merged in CMSSW_14_1_X_2024-03-22-2300, in which the failures appeared. |
@stahlleiton disables the workflow in #44540 |
[a] lheevent/runcmsgrid.sh
|
My current plan was to create a temporary directory with a different name per job (using lhe1t2m3p$RANDOM) outside of the current CMSSW directory to avoid clashing with settings of different CMSSW environments (i.e. the working directory and the gridpack settings). But if it is fine to create a different CMSSW directory inside another one, then I can simply do it as you proposed |
few other workflows, e.g. 523.0, do the same. So it should be fine to create cmssw dev area inside another. |
Great, then I will move to that approach and test it |
I tried to run multiple relval test using the same gridpack before and after the fix, and it managed to pass after removing the use of the temporary directory (while it failed using the temp dir as seen before). I made a PR to the genproduction repository updating the bash script and will create a PR to CMSSW to update the gridpack. |
The issue in worflow 180.1 should now be addressed in #44671 |
Were there any issues seen in the IBs after PR 44671 was integrated yesterday? If not, then we can probably close this issue as resolved. |
Thanks! |
Step 1 of workflow 180.1 fails in all(?) IBs with
e.g. https://cmssdt.cern.ch/SDT/cgi-bin/logreader/slc7_amd64_gcc12/CMSSW_14_1_X_2024-03-22-2300/pyRelValMatrixLogs/run/180.1_Starlight_DoubleDiffraction_5360_HI_2023/step1_Starlight_DoubleDiffraction_5360_HI_2023.log#/
The text was updated successfully, but these errors were encountered: