Skip to content
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

Automatic JIT testing #3328

Closed
brson opened this issue Aug 31, 2012 · 6 comments
Closed

Automatic JIT testing #3328

brson opened this issue Aug 31, 2012 · 6 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows A-testsuite Area: The testsuite used to check the correctness of rustc C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@brson
Copy link
Contributor

brson commented Aug 31, 2012

We have JIT code now. It passes lots of tests, but we don't actually run them. Needs a bot.

@pnkfelix
Copy link
Member

pnkfelix commented May 6, 2013

rusti uses the JIT, right? So regression+bot testing of rusti could help with this; see Issue #5469.

I'm assuming brson ideally wants unit tests for the JIT as well, but rusti testing alone might suffice for much of what we need.

@pnkfelix
Copy link
Member

pnkfelix commented May 6, 2013

Nominating for maturity milestone 4: "well covered", since this is a measurement mechanism for evaluating the correctness of a library.

@brson
Copy link
Contributor Author

brson commented May 16, 2013

compiletest does have a mode for testing the JIT now, but we never run it

@graydon
Copy link
Contributor

graydon commented Jun 20, 2013

accepted for well-covered milestone

@pnkfelix
Copy link
Member

visiting for triage, email from 2013-08-05.

I considered adding E-needstest tag. But this isn't about adding more tests (that's how I read "it passes lots of test"), its instead about adding either a dedicated bot, or incorporating the tests into some existing test suite?

@alexcrichton
Copy link
Member

Closing, the JIT has been removed.

bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
RalfJung pushed a commit to RalfJung/rust that referenced this issue Mar 3, 2024
./miri many-seeds: support MIRI_SEED_END to control the end of the seed range
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows A-testsuite Area: The testsuite used to check the correctness of rustc C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Development

No branches or pull requests

4 participants