Skip to content
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

temporarily remove premix relval from those executed by the bare matrix #7247

Conversation

franzoni
Copy link

@ktf @davidlange6 @mdhildreth
in light of: https://hypernews.cern.ch/HyperNews/CMS/get/swReleases/4150/1/1/1/1/1/2/1/1/1/1/1/1/1.html , premixing input samples for relval workflows won't appear before pre6.
This is a hook to remove 14 failing workflows in all IB's for the next few days, to be re-brought back as soon as it makes sense. NOTE: single workflows remain runnable, selected explicitly by -l
I sign this one, up to you wether merging or not.

@franzoni
Copy link
Author

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes or unless it breaks tests.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes (tests are also fine). This pull request will be automatically merged.

cmsbuild added a commit that referenced this pull request Jan 16, 2015
…l-CMSSW_7_4_X_2015-01-16-1400

temporarily remove premix relval from those executed by the bare matrix
@cmsbuild cmsbuild merged commit 854a182 into cms-sw:CMSSW_7_4_X Jan 16, 2015
@cmsbuild
Copy link
Contributor

@davidlange6
Copy link
Contributor

Ciao @franzoni
Even if I think this will just let us forget these workflows until long after they work, two things that should be changed/clarified:
A) why not do for all perpetually failing workflows (those much longer than these)
B) how does a user now run premiering workflows without editing files?

Thanks

@franzoni
Copy link
Author

hello @davidlange6,
here's some comments:

let us forget these workflows until long after they work

Why ? With premixing being one of key validation goals of 74, putting them back as soon as they make sense content-wise is not likely to be forgotten.

A) why not do for all perpetually failing workflows (those much longer than these)
the cause and remedy for this batch are easily identifiable. For other ~permanently failing workflows notified, we=offline/PdmV have taken measures to address the causes or remove them.

B) how does a user now run premiering workflows without editing files?
The handful of experts in need of the workflow definitions can uncomment two lines in a file.
While my opinion is clear, I don't mind, really: if uncommenting 2 lines is more of a pain than the the standing errors, things can be left as they were ("up to you wether merging or not"). I've placed the PR, you/ @ktf can judge what the best effective solution is.

@davidlange6
Copy link
Contributor

Ciao - My new PR (#7254) solves both problem B and turns off another set of broken workflows that we've been ignoring.. We still have the traditional addmonojet and some generator workflows to turn off in the next round of cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants