that's a feature not a bug for CI.
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.
-
-
CI spews the exact numbers: https://travis-ci.org/rust-lang-nursery/regex/jobs/176188633#L228-L243 …
-
if you want a more ergonomic experience: set up the defaults so CI will literally output a lock file in the logs.
-
making CI stagnant, when machines have infinite capacity for vigilance, is a bad solution to reproducing CI results.
-
consistent developer experience is worth a lot. making community defaults "run cargo update" isn't hard.
-
yes, your new dev argument is reasonable. But it comes at the cost of bad CI policy.
-
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?
-
that ship has completely sailed? You can't change the defaults, and you're not going to change the CI configs of the world.
-
what goes into travis.yml in a new Cargo project is easy to control.
End of conversation
New conversation -
-
-
not being able to jump into a debugger from a CI failure bothers me *so much*
-
let me download core dumps that I can use in docker *at the very least*. long-term, rr would be a good fit (rm on test pass)
End of conversation
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.