-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
DB lock issue durring unit tests #26741
Comments
A new Issue was created by @smuzaffar Malik Shahzad Muzaffar. @davidlange6, @Dr15Jones, @smuzaffar, @fabiocos, @kpedro88 can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign db |
New categories assigned: db @ggovi you have been requested to review this Pull request/Issue and eventually sign? Thanks |
Any idea why is this appearing just now? This code seems untouched since a while... |
This is just race condition. If both tests run on same time then there is a chance that there will be lock on the local db file. |
@smuzaffar yes, I understand that, the point is why it starts to systematically hit us now... |
is it very frequent now? |
the second test was added on Jan 23 this year ( #25722 ) |
well I would say we are seeing it in several PR tests, while this was not the case until recently. But the IB looks clean from this point of view, are unit tests run there differently? |
No, unit tests in IBs are run the same way. Only thing is that in IBs we run all tests that is why there is less chance of collision. |
#26762 should fix this issue |
this has been fixes via #26762 |
@ggovi , during PR tests of cms-data/RecoBTag-Combined#23 unit test
testConditionDatabase_2
failed due to locking issue [a]. I think issue is that there are two tests ( https://github.com/cms-sw/cmssw/search?q=cms_conditions_3.db&unscoped_q=cms_conditions_3.db ) which are usingcms_conditions_3.db
file. Can you please provide a fix for this?[a]
The text was updated successfully, but these errors were encountered: