You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In github actions, unit tests that run extract.instrument_altitude_to_model_pressure crash the CI environment. Tests run for about 6 hours and then fails due to timeout. Tests run in ~18 min on other environments in GA.
To Reproduce
Look through the unit test logs for #113 and for the test branch tst/troubleshoot_branch. All tests succeed on mac and ubuntu, adding manual skip marks to these tests remove the windows issue.
Expected behavior
Code should work on other platforms?
Screenshots
n/a
Desktop (please complete the following information):
Windows 2022
Python 3.9 and 3.10
Only tested in GA. Don't have a method of testing directly.
Additional context
These tests were using a skip statement for older versions of pysat. Local tests were used to verify, but none of the core developers are using windows. The pysat 3.0.2 release revealed this in GA, since these tests were now automatically run in a windows environment.
The text was updated successfully, but these errors were encountered:
jklenzing
changed the title
BUG: extract.instrument_altitude_to_model_pressure hangs on windows
BUG: instrument_altitude_to_model_pressure hangs on windows
Aug 10, 2022
Describe the bug
In github actions, unit tests that run
extract.instrument_altitude_to_model_pressure
crash the CI environment. Tests run for about 6 hours and then fails due to timeout. Tests run in ~18 min on other environments in GA.To Reproduce
Look through the unit test logs for #113 and for the test branch
tst/troubleshoot_branch
. All tests succeed on mac and ubuntu, adding manualskip
marks to these tests remove the windows issue.Expected behavior
Code should work on other platforms?
Screenshots
n/a
Desktop (please complete the following information):
Additional context
These tests were using a skip statement for older versions of pysat. Local tests were used to verify, but none of the core developers are using windows. The pysat 3.0.2 release revealed this in GA, since these tests were now automatically run in a windows environment.
The text was updated successfully, but these errors were encountered: