Issue warnings when lazy-download is not used. #6476
Conversation
Previously, when lazy-download was not used because: - The cache directory was not writable, - The cache filesystem was too small, OR - The cache filesystem was thought to be on a remote filesystem, then lazy-download was turned off without warning. This made debugging issues difficult - especially as turning off lazy-download can cause merges to go many times slower. We now issue a reasonably-worded warning when this happens.
|
A new Pull Request was created by @bbockelm (Brian Bockelman) for CMSSW_7_3_X. Issue warnings when lazy-download is not used. It involves the following packages: Utilities/StorageFactory @cmsbuild, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks. |
|
(I forgot to mention - the warnings only occur when lazy-download would otherwise have been used.) |
|
+1 |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar |
|
+1 |
Issue warnings when lazy-download is not used.
Previously, when lazy-download was not used because:
then lazy-download was turned off without warning.
This made debugging issues difficult - especially as turning off
lazy-download can cause merges to go many times slower. Whether lazy-download
is used is logged in the FrameworkJobReport - but often it takes an expert to decode
those!
We now issue a reasonably-worded warning when this happens.