Global build status incorrect when builds finish out of order #483

Open
seancribbs opened this Issue Mar 28, 2012 · 9 comments

Comments

Projects
None yet
8 participants

I pushed a fix that ended up finishing its build before a previous commit's build. As a result the build status on the left-hand side was incorrect (red). Note that the build-status image shows the correct status.

Travis CI - Distributed build platform for the open source community
Travis CI - Distributed build platform for the open source community
Contributor

henrikhodne commented May 24, 2012

I can confirm that this is still an issue. Tested it with this: http://travis-ci.org/#!/dvyjones/travis-python-test-forking.

Contributor

henrikhodne commented May 26, 2012

Probably related to #567.

I was hit by this issue today as well (as originally posted). Build 35 (failed) finished after Build 36 (passed) of the project I'm working on.

@ghost ghost assigned svenfuchs Dec 19, 2012

Owner

roidrage commented Dec 19, 2012

Bumping this because it's still relevant.

We'll be looking into this.

Contributor

henrikhodne commented Dec 19, 2012

Yeah, I just noticed this on one of my own projects recently.

Contributor

henrikhodne commented Jan 25, 2014

I believe travis-ci/travis-core#318 should fix this.

👍

I ran into this today with JamesMGreene/qunit-assert-step. Build #4 passed but Build #3 (both on the master branch) finished after it with an error, so the master branch's status badge was "error".

I ended up rerunning Build #4 to fix the badge.

Run into similar problems with two repos.

Rabbit-Converter/Rabbit-PHP : Travis
Rabbit-Converter/Rabbit-Elixir : Travis

Both build passed but the badge is still showing the first build status which is fail/error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment