Gracias! I'll run it locally, and only then do as you suggest. Cheers,
--chet--
On Mon, Dec 18, 2017 at 3:41 PM, James E. King, III
wrote:
> There are many reasons, and it's a constant battle. Either the tests are
> flaky or the environment may have changed.
> If you do a "commit --amend --n
There are many reasons, and it's a constant battle. Either the tests are
flaky or the environment may have changed.
If you do a "commit --amend --no-edit" and then force push, it will kick a
new build.
- Jim
On Mon, Dec 18, 2017 at 4:30 PM, Chet Murthy wrote:
> I've had a couple instances wher
I've had a couple instances where a Travis CI test will fail for reasons
that clearly aren't related to the PR I've submitted. In today's case, the
"cross-test" failed while building dart-related code, and my PR was *only*
in the C++ "compiler plugin" area. Almost all the other Travis tests have
