[SYCL][E2E] Mark non spir build targets as unsupported in AddressSanitizer tests

[ayylol]

No description provided.

[ayylol]

Note for reviewers, a majority of asan tests were never built for non-spir triples, but from my testing they are able to compile fine for nvptx other than the two tests changed in this pr. I'm doing this to enable prebuilt e2e testing on nvidia for precommit ci #16813.

It's likely that more markup will be needed to disable the other triples for these tests, once I work on enabling prebuilt e2e testing for AMD, but I just wanted to do the smallest needed changes here.

[AllanZyne]

Hi @ayylol, although these tests can be built on cuda or amd, we don't have plan to support them.
I think these tests are already skipped on cuda and amd now, so it should not affect your pre-ci test, right?

[ayylol]

Hi @AllanZyne,

I think these tests are already skipped on cuda and amd now, so it should not affect your pre-ci test, right?

Yes, that's right they are currently skipped in the precommit ci for nvidia/amd. However the changes im trying to do is enabling nvidia for the build-only test mode, since that mode works without having access to any devices it ignores device-specific features (like cpu/gpu, backend) when taking into account the requirement statements. So instead to mark a test as not being able to compile there are the target-* features, which do work in the build-only mode as well.

although these tests can be built on cuda or amd, we don't have plan to support them.

Would it be preferable then to disable all of these for the non-spir triples? I can add the REQUIRES: target-spir to the lit.local.cfg file so that it applies to all tests in this folder.

[AllanZyne]

Hi @AllanZyne,

I think these tests are already skipped on cuda and amd now, so it should not affect your pre-ci test, right?

Yes, that's right they are currently skipped in the precommit ci for nvidia/amd. However the changes im trying to do is enabling nvidia for the build-only test mode, since that mode works without having access to any devices it ignores device-specific features (like cpu/gpu, backend) when taking into account the requirement statements. So instead to mark a test as not being able to compile there are the target-* features, which do work in the build-only mode as well.

Ok, I see.

although these tests can be built on cuda or amd, we don't have plan to support them.

Would it be preferable then to disable all of these for the non-spir triples? I can add the REQUIRES: target-spir to the lit.local.cfg file so that it applies to all tests in this folder.

Yep, it would be better to disable all for the non-spir triples. Thanks.