Stream: t-compiler

Topic: x.py test quick failure


oli (Mar 17 2020 at 17:50, on Zulip):

I'd love that, too. I don't think it exists

pnkfelix (Mar 17 2020 at 19:36, on Zulip):

(I saw this and said "wait, surely that's not true; surely we have a --fail-fast or --max-errors or something ... but from reviewing compiletest --help, it does not seem to exist...)

pnkfelix (Mar 17 2020 at 19:37, on Zulip):

turning --quiet mode off might help, at least in terms of letting you see for yourself which test is actually failling?

lqd (Mar 17 2020 at 19:40, on Zulip):

Maybe a long sleep + bell sound + UI notification script to be executed -on-fail :)

pnkfelix (Mar 17 2020 at 19:41, on Zulip):

the --on-fail only works at the granularity of x.py's tests, not within individual compiletest suites, right?

pnkfelix (Mar 17 2020 at 19:41, on Zulip):

(because x.py already fails fast by default; the problem is that the src/test/ui suite is huge.)

lqd (Mar 17 2020 at 20:26, on Zulip):

I don't really know, --on-fail doesn't work locally for me

centril (Mar 18 2020 at 11:18, on Zulip):

you want to use --pass check btw when running UI tests; otherwise you're testing the runtime stuff as well

Bastian Kauschke (Mar 18 2020 at 13:29, on Zulip):

thx

Last update: May 29 2020 at 17:05UTC