Sometimes, we expect certain tests to fail specifically when they are run in the build environment.
For example, racket-packet-socket tries to get raw access to an ethernet device, which will clearly fail in the build sandbox. This makes it look like there are failing tests in racket-packet-socket in all the places that the build-server's output is shown to users (e.g. build-server UI itself; package catalog UI), even though that's sort-of not really the case.
It would be nice to have some way of saying either "I expect this and that file to fail its tests in this or that way when run on the build server", or "O build-server, do not run tests for this and that file!"
Sometimes, we expect certain tests to fail specifically when they are run in the build environment.
For example,
racket-packet-sockettries to get raw access to an ethernet device, which will clearly fail in the build sandbox. This makes it look like there are failing tests inracket-packet-socketin all the places that the build-server's output is shown to users (e.g. build-server UI itself; package catalog UI), even though that's sort-of not really the case.It would be nice to have some way of saying either "I expect this and that file to fail its tests in this or that way when run on the build server", or "O build-server, do not run tests for this and that file!"