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.

Sign up for GitHub

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

Jump to bottom

Integration Test in ExperimentInfoTest #8947

Closed
OwenArnold opened this issue Oct 9, 2013 · 3 comments
Closed

Integration Test in ExperimentInfoTest #8947

OwenArnold opened this issue Oct 9, 2013 · 3 comments
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
Maintenance

Comments

@OwenArnold
Copy link
Contributor

This issue was originally TRAC 8102

APITest, ExperimentInfoTest, testAllDatesInIDFs is quite a costly test, which touches the file system multiple times. This should be a system test not a unit test.

Keywords: MAINT
@OwenArnold
Copy link
Contributor Author

@NickDraper (2014-02-14T11:05:00):
Bulk move to assigned at the introduction of the triage step

@OwenArnold OwenArnold added 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
@NickDraper NickDraper added this to the Release 3.6 milestone Oct 2, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestone: Release 3.7 May 20, 2016
@peterfpeterson peterfpeterson added this to To do in Maintenance Nov 20, 2018
@stale
Copy link

stale bot commented Feb 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 23, 2021
@stale
Copy link

stale bot commented Mar 2, 2021

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

@stale stale bot closed this as completed Mar 2, 2021
Maintenance automation moved this from Icebox to Done Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
Mantid Maintenance
Status: Done
Maintenance
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NickDraper @OwenArnold