@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?
-
-
-
Replying to @wycats
disagree? I want the machines to be find breaks in the ecosystem!
1 reply 0 retweets 0 likes -
Replying to @Gankro
you can have a matrix line that does that, but reproducibility in CI is important too.
1 reply 0 retweets 1 like -
Replying to @wycats
Never seen anyone in the Rust lib community (including the nursery) using reproducible CI. This is how we catch regression early!
1 reply 0 retweets 0 likes -
Replying to @Gankro
"reproducible CI" means "hm my test failed but it looks like it may be intermittent." -> restart test -> you can actually tell
1 reply 0 retweets 0 likes -
Replying to @wycats
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.
1 reply 0 retweets 0 likes -
-
anyway, you don't have to agree with me. I changed my mind after years of agreeing with you and seeing costs slowly shift.
2 replies 0 retweets 0 likes -
Replying to @wycats
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
2 replies 0 retweets 0 likes
I'm saying "I see a bug on CI, lemme try to repro locally" is a thing. Having a "seed" is important.
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.