@wycats isn't commiting the lib lockfiles a CI hazard? Like if I tell travis to build+test my repo, it will use the lock by default?
-
-
disagree? I want the machines to be find breaks in the ecosystem!
-
you can have a matrix line that does that, but reproducibility in CI is important too.
-
Never seen anyone in the Rust lib community (including the nursery) using reproducible CI. This is how we catch regression early!
-
"reproducible CI" means "hm my test failed but it looks like it may be intermittent." -> restart test -> you can actually tell
-
I have zero concern about this for 99.9% of use cases (which is what defaults matter for). Most CI takes like, a minute to run.
-
you haven't had intermittent test failures on CI?
-
anyway, you don't have to agree with me. I changed my mind after years of agreeing with you and seeing costs slowly shift.
-
I'm saying there's basically zero impact of intermittent failures for small projects. I can run it like 5 times in a mins to be sure
- 10 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.