-
Notifications
You must be signed in to change notification settings - Fork 4
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
BROKEN: disabling tests #45
Comments
It looks like the three missing NIRISS AMI tests in the 2019-01-28 nightly appear because the process running that folder crashed upon hitting the disable file @cdsontag put in there to test:
The missing tests sort lexicographically after the disabled test, and therefore did not run. They also crashed on the 2019-01-28 Python 3 run, which doesn't check for missing tests. |
CC'ing @ibusko since this is affecting HST tests as well. |
Still crashes on disable files as of 20190423. Same exact error and traceback. |
Investigation so far: It's dying in run_dir L102 because m has no .lst() method. There is a previous comment about m.list(), so this looks likely to have been the result of a list->lst sweep gone wrong somehow. At L84, m is set to pandokia.run_file.get_runner_mod( runner ) The .jeng files are using the ttd runner which probably maps to https://github.com/spacetelescope/pandeia_test/blob/master/test_utilities/pandokia_runner_ttd.py which has a method named list (line 31), but not a method named lst which suggests that the list->lst sweep to remove the use of reserved keywords broke an API that external runners were depending on. Next steps:
|
The documentation on adding runners was indeed updated to change the API. |
Looks like it. In pandeia:
and yet in last night's nightly run, there are 0 tests showing as disabled.
To be VERY clear, we should disable a single engine test and verify that IT also does not show up in the Disable column of pandokia.
The text was updated successfully, but these errors were encountered: