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
This is why #4918, which we want for the upcoming release, is failing tests. Its CWL on ARM test run also is not running any tests.
We need to figure out why these tests are all getting skipped and fix it.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1571
The text was updated successfully, but these errors were encountered:
adamnovak
changed the title
Provisioner and CWL-on-ARM integration tests fail on master bwcause no tests are run
Provisioner and CWL-on-ARM integration tests fail on master because no tests are run
May 16, 2024
It looks like the CWL on ARM test is failing because the CWL on ARM test was cut in #4892, but the logic to require it in Gitlab for periodic tests or for PRs that touch CWL stuff was not removed.
The provisioner tests are failing because src/toil/test/wdl/wdltoil_test.py::WDLKubernetesClusterTest is included in the list of tests to run, but that class does not exist. Having the nonexistent class in the list causes all the tests to fail to be loaded for some reason, without producing an error about a missing class.
This problem was introduced in #4859 when the class was moved to toil/src/toil/test/wdl/wdltoil_test_kubernetes.py instead, but CI did not notice that the change affected the provisioner integration test job and did not run it for the PR.
In https://ucsc-ci.com/databiosphere/toil/-/jobs/67645 and https://ucsc-ci.com/databiosphere/toil/-/jobs/67642, for the last run of scheduled tests that managed to get past the build stage, neither integration test job ran any tests, and so the jobs failed.
This is why #4918, which we want for the upcoming release, is failing tests. Its CWL on ARM test run also is not running any tests.
We need to figure out why these tests are all getting skipped and fix it.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1571
The text was updated successfully, but these errors were encountered: