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

ci: Debugging ubuntu pytest gh runner #781

Closed

Conversation

gtdang
Copy link
Collaborator

@gtdang gtdang commented May 29, 2024

Debugging ubuntu pytest gh runner. #780

@gtdang gtdang requested review from jasmainak, rythorpe and ntolley May 29, 2024 21:05
@gtdang
Copy link
Collaborator Author

gtdang commented May 29, 2024

  1. I've edited the gh action to run the MPI test noted in our Parallel backends guide. The Linux runners are not returning the expected results. The Mac runners are returning the expected result.

Linux Runners

numprocs=1
numprocs=1
NEURON -- VERSION 8.2.4 HEAD (1d87d5d39) 2024-02-09
Duke, Yale, and the BlueBrain Project -- Copyright 1984-2022
See http://neuron.yale.edu/neuron/credits

NEURON -- VERSION 8.2.4 HEAD (1d87d5d39) 2024-02-09
Duke, Yale, and the BlueBrain Project -- Copyright 1984-2022
See http://neuron.yale.edu/neuron/credits

Hello from proc 0
Hello from proc 0

Expected result

numprocs=2
NEURON -- VERSION 8.2.4 release/8.2 (1d87d5d39) 2024-02-09
Duke, Yale, and the BlueBrain Project -- Copyright 1984-2018
See http://neuron.yale.edu/neuron/credits

Hello from proc 0
Hello from proc 1

The Linux runners seem to be duplicating a single process when it should be splitting into two processes.

  1. Running the pytest with verbose I've confirmed the unbuntu runners are stalling on the pytest step at test_dipole.py>test_cell_response_backends. This test requires MPI.

@gtdang gtdang requested a review from hollandjg May 29, 2024 21:13
@ntolley
Copy link
Contributor

ntolley commented May 30, 2024

Thanks for digging into this @gtdang!

I wonder if other repo's that test with MPI are experiencing the same issue...

@jasmainak
Copy link
Collaborator

was a new ubuntu release made that broke the runners?

@gtdang gtdang force-pushed the debug-linux-gh-runner-pytest branch from fef3441 to 0c68568 Compare May 30, 2024 15:42
@gtdang gtdang force-pushed the debug-linux-gh-runner-pytest branch from 0c68568 to 361fde9 Compare May 30, 2024 15:47
@gtdang
Copy link
Collaborator Author

gtdang commented May 30, 2024

was a new ubuntu release made that broke the runners?

They did release updated GitHub runner images in the last week. I've tested all 3 versions of Ubuntu that they offer and they all have the same issue... All 3 images were updated though. I need to look into how to run previous releases.

@jasmainak
Copy link
Collaborator

perhaps this is helpful: https://github.com/mpi4py/setup-mpi ?

@gtdang gtdang closed this Jun 25, 2024
@gtdang gtdang deleted the debug-linux-gh-runner-pytest branch August 29, 2024 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants