Skip to content

Preparing for running lexer tests on bots #15988

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jul 26, 2014
Merged

Conversation

brson
Copy link
Contributor

@brson brson commented Jul 25, 2014

Add check-secondary, which runs the pretty and lexer tests so we can run them on a dedicated bot. Leaves the pretty tests running under check until the bots are switched over. Also fixes some issues.

r? @cmr

brson added 5 commits July 24, 2014 21:34
We'll use this to run a subset of the test suite onto a dedicated
bot.

This puts the grammar tests and the pretty-printer tests under
check-secondary. It leanves the pretty tests under plain `check`
for now, until the new bot is added to take over.

Because check-secondary is not run as part of `make check` there
will be a set of tests that most users never run and are only
checked by bors. I think this will be ok because grammar tests
should rarely regress, and the people regressing such tests
should have the fortitude to deal with it.
Invoke rustc in a way that sets LD_LIBRARY_PATH,
and disable the deps on RustLexer.class when antlr isn't available.
This appears to be redundantly named with a shortcut target for
testing the syntax crate.
bors added a commit that referenced this pull request Jul 26, 2014
Add `check-secondary`, which runs the pretty and lexer tests so we can run them on a dedicated bot. Leaves the pretty tests running under `check` until the bots are switched over. Also fixes some issues.

r? @cmr
@bors bors closed this Jul 26, 2014
@bors bors merged commit 3382ffe into rust-lang:master Jul 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants