Skip to content

split stdtest into stdtest/coretest #1386

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Dec 26, 2011 · 3 comments
Closed

split stdtest into stdtest/coretest #1386

brson opened this issue Dec 26, 2011 · 3 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Dec 26, 2011

Stuff in core should not be tested in stdtest
@kud1ing
Copy link

kud1ing commented Dec 26, 2011

See also #1254

@kud1ing
Copy link

kud1ing commented Jan 18, 2012

This probably can be closed too, since the respective tests are in libcore and libstd now?

@brson
Copy link
Contributor Author

brson commented Jan 18, 2012

Yes

@brson brson closed this as completed Jan 18, 2012
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
@JohnTitor
Git-ignore pulls.json (rust-lang#1386)
1a4811e 
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 2, 2025
@JohnTitor
Git-ignore pulls.json (rust-lang#1386)
4627aa9 
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brson @kud1ing