-
Notifications
You must be signed in to change notification settings - Fork 106
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
Correctly pass dbsUrl to the locationsFromMSPileup method #11906
Correctly pass dbsUrl to the locationsFromMSPileup method #11906
Conversation
Jenkins results:
|
aaa02b3
to
2748054
Compare
Jenkins results:
|
Since it was a short fix, I have tested it by patching directly the testbed workqueue and just restarting the threads. Here [1] is the output. It clearly fixes the issue and I also expect the relevant workflows to be able to advance their status. Here is one to check later: tivanov_TaskChain_PUMCRecyc_Feb2024_Val_v2_240215_150924_2146 [1]
|
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.
Thanks Todor, it looks good to me.
Fixes #11903
Status
READY
Description
We were wrongly passing the whole
dbs
object to thelocationsFromMSPileup
method inWMCore.WorkQueue.DataLocationMapper
and later trying to parse it as a string in order to find out whether it was a testbed instance or not. This is used later as a marker to the actual MSPileup instance we are currently configured against.With this fix we are now refering to the
dbs.dbsURL
attribute in this parsing procedure which should fix the issue. But the question, whether using thedbsURL
in order to find out theMSPileup
instance is the optimal way, still remains.Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
None