Stream: t-compiler/help

Topic: x.py workflow


tmandry (Apr 03 2019 at 18:39, on Zulip):

Why is it that running ./x.py check seems to blow away any existing build I had for tests?

tmandry (Apr 03 2019 at 18:39, on Zulip):

When I re-run tests after a check, it has to start from scratch

tmandry (Apr 03 2019 at 18:40, on Zulip):

Maybe I'm confused about the cause here, though

QuietMisdreavus (Apr 03 2019 at 18:42, on Zulip):

x.py check always uses incremental, so it always creates incremental artifacts

QuietMisdreavus (Apr 03 2019 at 18:42, on Zulip):

if you weren't using incremental before, this is the same as completely invalidating any artifacts you had before

tmandry (Apr 03 2019 at 18:43, on Zulip):

I am using incremental, though..

centril (Apr 03 2019 at 19:59, on Zulip):

I always pass in -i just to be sure

tmandry (Apr 03 2019 at 21:03, on Zulip):

that's what I'm doing :)

tmandry (Apr 03 2019 at 21:04, on Zulip):

well now that I know it's just me, I can try to figure out what else I'm doing

varkor (Apr 03 2019 at 22:52, on Zulip):

x.py check and x.py build do not play nicely with each other

varkor (Apr 03 2019 at 22:54, on Zulip):

https://github.com/rust-lang/cargo/issues/3501

varkor (Apr 03 2019 at 22:54, on Zulip):

it seems plausible this might be causing the problem?

ange (Apr 11 2019 at 20:12, on Zulip):

x.py check and x.py build do not play nicely with each other

Does x.py test -iplay well with x.py build -i? I have a compiler and want to run a single testcase under compiletest, but if it's going to blow everything away I'll limit myself to gedankentesting for now ;-)

ange (Apr 11 2019 at 21:24, on Zulip):

Well, for posterity, ./x.py test -i --stage 1 src/test/ui --test-args foo does not rebuild the compiler :tada:

Last update: Nov 11 2019 at 22:00UTC