Skip to content
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

Speed up CorrectFlightPaths unit test #8500

Closed
mantid-builder opened this issue Aug 5, 2013 · 1 comment
Closed

Speed up CorrectFlightPaths unit test #8500

mantid-builder opened this issue Aug 5, 2013 · 1 comment
Assignees
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Maintenance Unassigned issues to be addressed in the next maintenance period.
Milestone

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: Russell Taylor

This ticket is blocks : TRAC7521

This test has been shown to be one of our slowest unit tests; indeed on OS X it has been observed to take well over a minute! This needs to be improved to ideally ~1s but at least 3-4s across all platforms.

The first task is to refactor to not load a data file and use in-memory constructed test data instead. Just this step may well solve the speed problem on its own.


Keywords: Maintenance

@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 7655

@mantid-builder mantid-builder added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 3.0 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
None yet
Development

No branches or pull requests

2 participants