vtk-m: Changed test method names and skipping non-applicable tests to use new API

[AcriusWinter]

Update standalone test API. See below comment for test output.

Supersedes #35807 updates for the package

https://spack.readthedocs.io/en/latest/packaging_guide.html#stand-alone-tests

[AcriusWinter]

spack test run vtk-m
==> Spack test 7x3itvd7jreqc4s2kgtokomt7azuwhw2
==> Testing package vtk-m-2.1.0-k4ixr3n
============================== 1 passed of 1 spec ==============================

[tldahlgren]

Confirmed spack install --test=root vtk-m~examples fails to build because the test raises an exception (as expected).

Almost there. A couple of minor changes.

[tldahlgren]

IMO the test purpose needs to be clearer.

[tldahlgren]

spack test run vtk-m ==> Spack test 7x3itvd7jreqc4s2kgtokomt7azuwhw2 ==> Testing package vtk-m-2.1.0-k4ixr3n ============================== 1 passed of 1 spec ==============================

Please paste the test summary so it shows the parts.

[AcriusWinter]

========================= SUMMARY: vtk-m-2.1.0-k4ixr3n =========================
VtkM::test_smoke_test .. PASSED
============================= 1 passed of 1 parts ==============================

[tldahlgren]

Looks like CI succeeded (per contents of the link) but is being reported as failed.

@spackbot run pipeline

[spackbot-app]

I'm sorry, gitlab does not have your latest revision yet, I can't run that pipeline for you right now.

One likely possibility is that your PR pipeline has been temporarily deferred, in which case, it is awaiting a develop pipeline, and will be run when that finishes.

Please check the gitlab commit status message to see if more information is available.

Details

Unexpected response from gitlab: {'error': 'invalid_token', 'error_description': 'Token is expired. You can either do re-authorization or token refresh.'}

[tldahlgren]

@spackbot run pipeline

[spackbot-app]

I'm sorry, gitlab does not have your latest revision yet, I can't run that pipeline for you right now.

One likely possibility is that your PR pipeline has been temporarily deferred, in which case, it is awaiting a develop pipeline, and will be run when that finishes.

Please check the gitlab commit status message to see if more information is available.

Details

Unexpected response from gitlab: {'error': 'invalid_token', 'error_description': 'Token is expired. You can either do re-authorization or token refresh.'}

[tldahlgren]

@spackbot run pipeline

[spackbot-app]

I'm sorry, gitlab does not have your latest revision yet, I can't run that pipeline for you right now.

One likely possibility is that your PR pipeline has been temporarily deferred, in which case, it is awaiting a develop pipeline, and will be run when that finishes.

Please check the gitlab commit status message to see if more information is available.

Details

Unexpected response from gitlab: {'error': 'invalid_token', 'error_description': 'Token is expired. You can either do re-authorization or token refresh.'}

[tldahlgren]

@spackbot run pipeline

[spackbot-app]

I'm sorry, gitlab does not have your latest revision yet, I can't run that pipeline for you right now.

One likely possibility is that your PR pipeline has been temporarily deferred, in which case, it is awaiting a develop pipeline, and will be run when that finishes.

Please check the gitlab commit status message to see if more information is available.

Details

Unexpected response from gitlab: {'error': 'invalid_token', 'error_description': 'Token is expired. You can either do re-authorization or token refresh.'}

[mvandenburgh]

@spackbot run pipeline

[spackbot-app]

I'm sorry, gitlab does not have your latest revision yet, I can't run that pipeline for you right now.

One likely possibility is that your PR pipeline has been temporarily deferred, in which case, it is awaiting a develop pipeline, and will be run when that finishes.

Please check the gitlab commit status message to see if more information is available.

Details

Unexpected response from gitlab: {'error': 'invalid_token', 'error_description': 'Token is expired. You can either do re-authorization or token refresh.'}

[mvandenburgh]

@spackbot run pipeline

[spackbot-app]

I've started that pipeline for you!