Stream: general

Topic: fail tests on first failure


Nikita Popov (Nov 02 2018 at 15:33, on Zulip):

When using x.py test, how can I stop immediately when the first failure is encountered? I'm running tests on the emscripten target, which is very slow for some reason.

oli (Nov 02 2018 at 15:34, on Zulip):

I don't think that's possible, but I'd like that, too

oli (Nov 02 2018 at 15:35, on Zulip):

What's funny is that there's a --no-fail-fast flag

Nikita Popov (Nov 02 2018 at 15:36, on Zulip):

Hm, is it possible to make the output verbose to see test names as they are run? -v does not seem to get passed through to the tests, it only shows verbose info for the build steps.

oli (Nov 02 2018 at 15:37, on Zulip):

not while they are run, you get the verbose dump at the end

oli (Nov 02 2018 at 15:37, on Zulip):

hmm... the source around --no-fail-fast is weird

Nikita Popov (Nov 02 2018 at 15:38, on Zulip):

And as an unrelated question, can I put a different builder on type = pull_request in Travis or is that going to get killed?

oli (Nov 02 2018 at 15:39, on Zulip):

that... should work, but you'll have to remove it before it gets merged

Nikita Popov (Nov 02 2018 at 23:34, on Zulip):

It did indeed work :)

lqd (Nov 04 2018 at 20:57, on Zulip):

Hm, is it possible to make the output verbose to see test names as they are run?

yes: verbose-tests = true in config.toml (which is how tests are run in CI if memory serves)

Last update: Nov 22 2019 at 00:10UTC