-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Move libtest out of rust-lang/rust #57842
Conversation
@alexcrichton once we have something that "works" for this PR, it would be great if you could move the extracted Also, I extracted the libtest crate there by forking the rust repo and removing everything but the crate, because I wanted to preserve the history. But this means that the libtest crate repo is huge, which makes the initial fetch very slow. I think this won't be a problem once we release the libtest crate to crates.io and add it as a normal dependency instead of a git dependency, but I prefer to do that when the official repo for libtest is set up. |
Hey heads up, with respect to size, we can use From a fresh checkout of
I've hosted the result here: https://github.com/djrenren/libtest but it looks like it lacks |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Heh seems like a good start! Always like seeing those massive negative numbers :) Some other items to cover before merging:
|
ping from triage @gnzlbg you need to address the first point in #57842 (comment) and the conflicts |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@alexcrichton so I've managed to properly extract only the history of the libterm and libtest repositories.
So
The repo is ready (https://github.com/gnzlbg/libtest) I've transferred it to you so that it can be added to the organization. I haven't published the repo yet, since I thought it might be better for the organization to publish it. Once the transfer is complete I can publish it as libtest 0.0.1 and will update this PR to use that instead. Every time libtest is modified upstream one has to restart the migration process from zero, so once this is done it might be wise to prioritize the bors merge. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
So the failure is to be expected until we start using a crate from crates.io. I've added a commit that runs the apple and linux jobs on this branch to make sure that modulo tidy everything else is ok. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
☔ The latest upstream changes (presumably #58879) made this pull request unmergeable. Please resolve the merge conflicts. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@alexcrichton so I went ahead and released the crates on crates.io to make the tests pass, i've sent you invites as an owner. |
Oh sorry I was a bit slow on the repo transfer and it's now expired, want to send the transfer to me again? (and I'll transfer to rust-lang) I think it'd be best though if we start off from a clean/stable slate. Would it be possible to get |
So @alexcrichton I've added a README briefly describing the situation and pointing to a "roadmap" issue in |
@bors: r+ |
📌 Commit b7f0b76f01a8badb209c4195fcd1f5e727108d4a has been approved by |
@bors: r+ |
📌 Commit 144bdc6 has been approved by |
⌛ Testing commit 144bdc6 with merge 30cbf5b1f2a7260df1018f689417ba5c61ed4c9a... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-travis |
@bors: r+ |
📌 Commit 1446b24 has been approved by |
Move libtest out of rust-lang/rust This is a first step towards a number of goals explained in this internals post: https://internals.rust-lang.org/t/a-path-forward-towards-re-usable-libtest-functionality-custom-test-frameworks-and-a-stable-bench-macro This PR does not fully remove libtest from rust-lang/rust, we keep a shim that imports and re-exports the external libtest, and adds the proc_macro dependency, etc. r? @alexcrichton cc @djrenren @petrochenkov
☀️ Test successful - checks-travis, status-appveyor |
📣 Toolstate changed by #57842! Tested on commit 3eb4890. 💔 clippy-driver on windows: test-pass → test-fail (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra). |
Tested on commit rust-lang/rust@3eb4890. Direct link to PR: <rust-lang/rust#57842> 💔 clippy-driver on windows: test-pass → test-fail (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra). 💔 clippy-driver on linux: test-pass → test-fail (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra).
Revert "Auto merge of #57842 - gnzlbg:extract_libtest, r=gnzlbg" This reverts commit 3eb4890, reversing changes made to 7a4df3b. This is, as best I can tell, a clean revert of #57842. It retains some interim changes, like moving `black_box`, and otherwise brings libtest back in as it was before removal.
This is a first step towards a number of goals explained in this internals post: https://internals.rust-lang.org/t/a-path-forward-towards-re-usable-libtest-functionality-custom-test-frameworks-and-a-stable-bench-macro
This PR does not fully remove libtest from rust-lang/rust, we keep a shim that imports and re-exports the external libtest, and adds the proc_macro dependency, etc.
r? @alexcrichton
cc @djrenren @petrochenkov