# Build stuck in running state and the next stage started despite the previous stage failure

**URL:** <https://travis-ci.community/t/build-stuck-in-running-state-and-the-next-stage-started-despite-the-previous-stage-failure/5572>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** bug\
**Created:** [October 21, 2019, 7:10am UTC](https://travis-ci.community/t/build-stuck-in-running-state-and-the-next-stage-started-despite-the-previous-stage-failure/5572 "2019-10-21T07:10:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![akimd](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/akimd/32/2949_2.png) [@akimd](https://travis-ci.community/u/akimd)\
**Post date:** [October 21, 2019, 7:10am UTC](https://travis-ci.community/t/build-stuck-in-running-state-and-the-next-stage-started-despite-the-previous-stage-failure/5572/1 "2019-10-21T07:10:45Z")

</div>

[https://travis-ci.org/akimd/bison/builds/600582734](https://travis-ci.org/akimd/bison/builds/600582734)

I have pushed -f quickly, and travis seems to have not noticed that it faced a failure. The log reveals:

$ git checkout -qf adb073139a8a3af2c1f26848377b1b55fc8dc752

167fatal: reference is not a tree: adb073139a8a3af2c1f26848377b1b55fc8dc752

168The command “git checkout -qf adb073139a8a3af2c1f26848377b1b55fc8dc752” failed and exited with 128 during .

169

170Your build has been stopped.

yet the remainder of the pipeline seems not to have noticed the failure of the first step.