sage -t is still supported, no? I use it all the time, even with meson editable install.

What's the issue with the deleted test?

sage -t is still supported, no? I use it all the time, even with meson editable install.

What's the issue with the deleted test?

The sage script in the root does provide -t, but not the sage cli that is installed by meson. The tests in CI are picking up only the installed sage script.

The tests are more or less outdated/not very important.

I'd rather be careful and do a # needs !meson. (Is the feature flag already there?)

With #39030 there is only going to be a meson build...

Is src/conftest_inputtest.py still useful after this? And the exception for it in conftest.py?

Is src/conftest_inputtest.py still useful after this? And the exception for it in conftest.py?

Good observation. It's no longer used, indeed, and thus I've removed it now as well.

Tobias is the one who added these tests, so "they're not very important" is a more compelling argument than usual. In the near future we will (want to) be able to tell people to run pytest rather than a weird sage command, so removing the test for the old way (that breaks under the new way) seems reasonable to me.

Not related, but is it intended that the Meson/Windows jobs are passing even though the test phase fails?

FWIW there's no way to test for meson per se, but there are several variables that are meaningless outside of sage-the-distro and are usually unset (distro packages tend to have similar problems).

Thanks for the review!

Not related, but is it intended that the Meson/Windows jobs are passing even though the test phase fails?

Yes, as we don't have any meaningful way to run the tests on Windows now (in a way that make most of them pass). The important part is that the compilation is successful on Win.

FWIW there's no way to test for meson per se, but there are several variables that are meaningless outside of sage-the-distro and are usually unset (distro packages tend to have similar problems).

With #39030, sage-the-distro will also finally use the meson backend. Afterwards we can indeed remove all those special variables, and also determine features during build time and not runtime.