Added test specs for e4s 23.05 and 23.08. #242
Conversation
| @@ -0,0 +1,26 @@ | |||
| #This buildtest was generated from spack-test-23.05-template.yaml | |||
| buildspecs: | |||
| py-warpx_spack-test_23.05: | |||
There was a problem hiding this comment.
please remove this test we dont have this installed in the gcc spack environment for e4s/23.05 i just checked
siddiq90@login27> spack -e gcc find py-warpx
==> No package matches the query: py-warpx
|
@wspear hold up i just realized we have spack tests for 23.08 in this PR #240 take a look at https://github.com/buildtesters/buildtest-nersc/tree/devel/buildspecs/e4s/spack_test/perlmutter. I see we have 23.05 tests too. I guess if you see any packages we have missed, we can add them. |
|
Yeah, I thought that was already all done. I thought the spack_test path was for the spack internal tests so I didn't look for the e4s testsuite tests there before making the new PR. |
I think lets close this PR and you can work on E4S Testsuite tests for these stacks see issue #203. So only add test s for ones that have tests from E4S Testsuite. I dont know if there is an overlap with tests from spack test and E4S Testsuite for package X. If that is the case just simply skip from E4S Testsuite unless we see failure from spack test. Right now there are 50 failures see https://my.cdash.org/viewTest.php?onlyfailed&buildid=2452793 so its not looking good and we may want to resort to E4S Testsuite for some of these |
| #This buildtest was generated from spack-test-23.05-template.yaml | ||
| buildspecs: | ||
| aml_e4s-testsuite_23.05: | ||
| type: spack |
Fixed input parsing for testgen script (needed a 3rd argument, only checked for the first 2).