-
Notifications
You must be signed in to change notification settings - Fork 128
Fix startup tests #37925
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
Fix startup tests #37925
Conversation
This will need a build packages from branch run as the failing systems tests don't run on Windows or OSX as part of normal PR testing |
Since we switched to pip install --editable instead of calling setup.py directly, we no longer get an executable file in the build output, so this test needed adjusting. It was also attempting to do a for loop and returning at the first entry so we fixed that. Co-authored-by: Jonathan Haigh <jonathan.haigh@stfc.ac.uk>
056e996
to
77a832d
Compare
This was never tested previously, and the dev build does not create a mantidworkbench entry point, conda-build does that, hence I've deleted it.
The startup script isn't going to exist any more, so change the command used for debugging workbench.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
System tests passing on all operating systems 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mantid launching from both vs and pycharm
Since we switched to
pip install --editable
instead of callingsetup.py
directly (#37775), we no longer get an executable file in the build output, so this test needed adjusting. It was also attempting to do a for loop and returning at the first entry so we fixed that.On Linux it was trying to test
mantidworkbench
as an entry point but:mantidworkbench
entry point is created byconda-build
, not when you do a dev build, so this wouldn't have worked previously anyway.To test:
https://builds.mantidproject.org/job/build_packages_from_branch/876/
Reviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.