Ticket #6681 (assigned)
A number of unit tests fail if all (histogram) workspaces are managed.
Reported by: | Russell Taylor | Owned by: | Roman Tolchenov |
---|---|---|---|
Priority: | critical | Milestone: | Backlog |
Component: | Framework | Keywords: | Maintenance |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description (last modified by Nick Draper) (diff)
i.e. If ManagedWorkspace.LowerMemoryLimit = 0 is added to the Mantid.(user.)properties file so that all new Workspace2D's are instead a ManagedWorkspace2D or a ManagedRawFileWorkspace2D
On my Mac, the following unit tests fail (on the current master branch):
381 - DataHandlingTest_LoadDetectorInfoTest (Failed) 388 - DataHandlingTest_LoadGSSTest (Failed) 392 - DataHandlingTest_LoadInstrumentTest (Failed) 411 - DataHandlingTest_LoadQKKTest (Failed) 414 - DataHandlingTest_LoadRaw3Test (Failed) 446 - DataHandlingTest_SaveDaveGrpTest (Failed) 475 - AlgorithmsTest_ApplyTransmissionCorrectionTest (Failed) 511 - AlgorithmsTest_CreateLogPropertyTableTest (Failed) 558 - AlgorithmsTest_GroupWorkspacesTest (Failed) 570 - AlgorithmsTest_MedianDetectorTestTest (Failed) 645 - WorkflowAlgorithmsTest_SANSSolidAngleCorrectionTest (Failed) 667 - CurveFittingTest_FitPowderDiffPeaks2Test (Failed) 730 - CrystalTest_IntegratePeakTimeSlicesTest (Failed) 737 - CrystalTest_PeakIntegrationTest (Failed)
It's true we have a system test job that is supposed to be checking things in this scenario, but this unnerves me somewhat - the only discernible difference between managed & in-memory workspaces should be performance.
Change History
comment:2 Changed 7 years ago by Nick Draper
- Owner set to Roman Tolchenov
- Status changed from new to assigned
- type changed from defect to task
We should at least understand this, and decide where to go from there.
comment:5 Changed 7 years ago by Nick Draper
- Priority changed from major to critical
- Keywords Maintenance added
comment:6 Changed 7 years ago by Nick Draper
- Description modified (diff)
- Milestone changed from Release 2.6 to Backlog
comment:8 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.0 to Backlog
Moved out to backlog as not enough time in R3.0
comment:9 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 7527
Moved to r2.6 at the end of r2.5