This issue attempts to answer the question of why (some) test uploads fail and don't show up on sdk.testing.exaworks.org.
There is one test driver in ci/tests/test.py, first and last updated on Jul 20 2022. It appears to generate the correct json. In particular, the key data.results.<testname>.status is present. I was looking at this file and wondering what is wrong.
There is another test driver in .github/test.py, last updated Apr 5 2022. It lacks the above key, causing the testing service not to accept the input. This is the file used by the github CI and possibly by other CI deployments. If your CI deployment is using this driver, it won't work.
mturilli
commented
1 year ago
This issue attempts to answer the question of why (some) test uploads fail and don't show up on sdk.testing.exaworks.org.
There is one test driver in
ci/tests/test.py, first and last updated on Jul 20 2022. It appears to generate the correct json. In particular, the keydata.results.<testname>.statusis present. I was looking at this file and wondering what is wrong.There is another test driver in
.github/test.py, last updated Apr 5 2022. It lacks the above key, causing the testing service not to accept the input. This is the file used by the github CI and possibly by other CI deployments. If your CI deployment is using this driver, it won't work.