You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
445: Try temporary fix for CI r=jswrenn a=phimuemue
Unfortunately, I was not able to implement the idea @jswrenn suggested in #444 (comment) (having an optional `dev-dependency` seems to be a problem).
Thus, I adapted @jswrenn's attempt from 3f9e669 so that our MSRV only `build`s while stable/beta/nightly also test and bench.
To be honest, this feels pretty unsastisfactorily, but it may for now be a viable option that avoids blocking all PRs just because of a compilation error in a `dev-dependency`. Another possibility might be to downgrade `criterion`'s version (or abandon `criterion` altogether), both not particularly appealing imho.
When releasing a new version, we could still try to have one test/bench run on our MSVC (possibly with a manually adjusted `criterion` version).
(Sorry for all the noise from my side, but I'd really like to settle these kinds of problems so that we enable people to contribute without much inconvenience.)
Co-authored-by: philipp <[email protected]>
Copy file name to clipboardExpand all lines: Cargo.toml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ either = { version = "1.0", default-features = false }
27
27
28
28
[dev-dependencies]
29
29
rand = "0.7"
30
-
criterion = "=0.3.0"# TODO update criterion version once it becomes compatible with our minimum required Rust verision or bump minimum required rust version
30
+
criterion = "=0"# TODO how could this work with our minimum supported rust version?
0 commit comments