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
-
-
they suck EGGS for large projects because it's like "well crap there goes another hour"
1 reply 0 retweets 1 like -
Replying to @Gankro
it has nothing to do with running it 5 times. It has to do with reproducing the failure in an env that has a debugger.
2 replies 0 retweets 0 likes -
Replying to @wycats
CI spews the exact numbers: https://travis-ci.org/rust-lang-nursery/regex/jobs/176188633#L228-L243 …
1 reply 0 retweets 0 likes -
if you want a more ergonomic experience: set up the defaults so CI will literally output a lock file in the logs.
1 reply 0 retweets 0 likes -
making CI stagnant, when machines have infinite capacity for vigilance, is a bad solution to reproducing CI results.
1 reply 0 retweets 0 likes -
Replying to @Gankro
consistent developer experience is worth a lot. making community defaults "run cargo update" isn't hard.
1 reply 0 retweets 0 likes -
Replying to @wycats
yes, your new dev argument is reasonable. But it comes at the cost of bad CI policy.
1 reply 0 retweets 0 likes -
Replying to @Gankro
as I said, it's very easy to make the "default experience" for Travis to include a `cargo update` on one row. Let's do it?
1 reply 0 retweets 0 likes -
Replying to @wycats
that ship has completely sailed? You can't change the defaults, and you're not going to change the CI configs of the world.
1 reply 0 retweets 0 likes
what goes into travis.yml in a new Cargo project is easy to control.
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.