search

mantidproject / mantid

Main repository for Mantid code
https://www.mantidproject.org
GNU General Public License v3.0
210 stars 121 forks source link

Delete caches if they are corrupted for Geometry Caches in LoadInstrument #33439

Closed Pasarus closed 1 year ago

Pasarus commented 2 years ago

When loading with hashes of geometry, if it fails to load due to corruption, we should delete the GeometryCache and try again instead of just falling over.

Load-[Notice] Load started (child)
LoadInstrument-[Error] Error in execution of algorithm LoadInstrument:
LoadInstrument-[Error] Unable to parse File: in "/home/abc/.mantid/instrument/geometryCache/OSIRISafdb7c83e1a2f642d8ef1b462e13bcff5717fdc7.vtp"
Load-[Notice] Load successful, Duration 0.08 seconds
LoadParameterFile-[Notice] LoadParameterFile started (child)
LoadParameterFile-[Notice] LoadParameterFile successful, Duration 0.01 seconds
ISISIndirectEnergyTransfer-[Error] Error in execution of algorithm ISISIndirectEnergyTransfer:
ISISIndirectEnergyTransfer-[Error] "'OSI97919_mon' does not exist."
ISISIndirectEnergyTransfer-[Error]   at line 194 in '/jenkins_workdir/workspace/main_nightly_deployment_prototype/Framework/PythonInterface/plugins/algorithms/WorkflowAlgorithms/ISISIndirectEnergyTransfer.py'
ISISIndirectEnergyTransfer-[Error]   caused by line 503 in '/jenkins_workdir/workspace/main_nightly_deployment_prototype/scripts/Inelastic/IndirectReductionCommon.py'
ISISIndirectEnergyTransfer-[Error]   caused by line 54 in '/jenkins_workdir/workspace/main_nightly_deployment_prototype/Framework/PythonInterface/mantid/kernel/_aliases.py'
EISISIndirectEnergyTransfer-[Notice] ISISIndirectEnergyTransfer started
stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

stale[bot] commented 1 year ago

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.