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

Fix execution of MPI-enabled SP tests #799

Merged
merged 3 commits into from
Aug 7, 2017
Merged

Conversation

jougs
Copy link
Contributor

@jougs jougs commented Aug 3, 2017

This fixes #791 by using the absolute path of the script in the invocation of python. It also handles skipped tests properly in our custom Python test harness.

@jougs jougs requested review from heplesser and sdiazpier August 3, 2017 16:33
Copy link
Contributor

@heplesser heplesser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good as a fix for the current issue. I am not really happy, though, with the way in which we here "highjack" the suite() method to run MPI tests. But we can get back to that once we have come to a conclusion on #761.

@jougs jougs added this to the NEST 2.12.1 milestone Aug 7, 2017
@jougs jougs added ZC: Infrastructure DO NOT USE THIS LABEL ZC: PyNEST DO NOT USE THIS LABEL I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Bug Wrong statements in the code or documentation ZP: PR Created DO NOT USE THIS LABEL labels Aug 7, 2017
@jougs jougs requested review from gtrensch and removed request for sdiazpier August 7, 2017 10:04
@gtrensch
Copy link
Contributor

gtrensch commented Aug 7, 2017

Looks good to me, even though there are lines longer than 80. (*.py.in will not run through the PEP8 check) I'm entirely happy with this. Approved!

@heplesser heplesser merged commit ebe26d0 into nest:master Aug 7, 2017
@jougs jougs deleted the fix-791 branch August 31, 2023 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Bug Wrong statements in the code or documentation ZC: Infrastructure DO NOT USE THIS LABEL ZC: PyNEST DO NOT USE THIS LABEL ZP: PR Created DO NOT USE THIS LABEL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PyNEST tests occur problem "python: can't open file 'test_sp/mpitest_issue_578_sp.py' "waitting for solution
3 participants