-
Notifications
You must be signed in to change notification settings - Fork 61
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
Use stable libtest #165
base: master
Are you sure you want to change the base?
Use stable libtest #165
Conversation
|
Our session-types library also broke due to the recent changes in compiletest. Your changes seem to fix some of the issue, but I'm still getting the following errors when trying to compile with this branch:
That's on a stable build by the way. |
@Munksgaard on which stable version? |
@mati865, you're right, I was using an old stable version. After updating to 1.33.0 everything is dandy with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This removes the tester
crate entirely, if I understand correctly?
@@ -1,6 +1,6 @@ | |||
[package] | |||
name = "compiletest_rs" | |||
version = "0.3.20" | |||
version = "0.4.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't do version bumps in this commit, I do that separately.
@@ -2,13 +2,10 @@ language: rust | |||
matrix: | |||
include: | |||
- rust: nightly | |||
env: FEATURES="" | |||
env: FEATURES="--features unstable" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about nightly
for the feature name?
extern crate rustc; | ||
|
||
#[cfg(unix)] | ||
extern crate libc; | ||
extern crate libtest as test; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the rename to libtest
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't want it to try and link with the local test
crate that is unstable and broken now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But an as
import will never change what gets linked. So why not keep extern crate libtest as test
?
Is this ready to land? The PR description still says WIP. |
Oh, the other PR needs to merge |
Ping, any update on this? |
We're currently reverting the libtest changes in Rust, but the path forward will likely involve landing this eventually, keeping it open for now. |
What is the status of this? We just ran into another compiletest feature that hasn't been synced here yet (and it's been in rustc for more than 2 years). |
Someone needs to replace compiletest in rust-lang/rust with this crate to avoid the duplication. I don't think anybody is working on that. |
Interesting, thanks! Some time ago I was told that someone is working on it and it would happen right after the next Rust release. Oh well. |
WIP: this uses my branch of stable libtest, that will be merged as part of rust-lang/libtest#11 . Once that is merged I'll update this PR to use libtest 0.0.2, but I wanted to make sure that CI here works fine first.