# Dashboard status after !6110

**URL:** https://discourse.vtk.org/t/dashboard-status-after-6110/1971
**Category:** Dashboards
**Created:** [October 24, 2019, 7:52pm UTC](https://discourse.vtk.org/t/dashboard-status-after-6110/1971 "2019-10-24T19:52:07Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [October 24, 2019, 7:52pm UTC](https://discourse.vtk.org/t/dashboard-status-after-6110/1971/1 "2019-10-24T19:52:07Z")

</div>

So after merging !6110 (which had green dashboards), `master` looked a bit rocky on some dashboards. I went and investigated on `taanab` and `bigmac`. On the latter, I reproduced the error and then started to bisect over the branch finding…nothing wrong. Rerunning on the merge (since it could have somehow been the combination of master and the branch that was the problem, I couldn’t reproduce it again. Similar effects on `taanab` when I tried there. So, since it’s a ghost-y issue that I can’t debug right now, I’m going to see if another `master` build papers over the issue. But if not, I’ll dig back in again tomorrow and debug more. Leaving this here as a heads up before leaving today.

In the meantime, I fixed the `eeloo` `+extdeps` builder to at least have a chance at testing again. A `git` command had died and left around an `index.lock` file causing everything to fail updating `git`, so it didn’t even show up on CDash since it never got that far. Hopefully it is happy now, but it’s possible some other changes crept in for that builder.

Cc: @ken-martin @utkarshayachit @brad.king

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [October 24, 2019, 8:03pm UTC](https://discourse.vtk.org/t/dashboard-status-after-6110/1971/2 "2019-10-24T20:03:07Z")

</div>

And I may have found out why `eeloo` was submitting to the `master` track. I’ve updated from 3.12.0 to 3.12.4 in case it was fixed in a patch release. Another thing to keep an eye on.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [October 25, 2019, 12:37pm UTC](https://discourse.vtk.org/t/dashboard-status-after-6110/1971/3 "2019-10-25T12:37:55Z")

</div>

Hrm. Seems it is real. Trying to get a failing build I can debug on `bigmac`.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [October 25, 2019, 5:41pm UTC](https://discourse.vtk.org/t/dashboard-status-after-6110/1971/4 "2019-10-25T17:41:31Z")

</div>

[!6119](https://gitlab.kitware.com/vtk/vtk/merge_requests/6119) reverting the offending change has been merged. I still don’t understand exactly _why_ this change broke things, but I’ll investigate that at a later date. We’ve been rolling just fine with the typo for a while anyways.
