# Dashboard Status

**URL:** https://discourse.kitware.com/t/dashboard-status/308
**Category:** Software Process
**Created:** [September 7, 2019, 1:56am UTC](https://discourse.kitware.com/t/dashboard-status/308 "2019-09-07T01:56:16Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.kitware.com/user_avatar/discourse.kitware.com/dcthomp/32/10_2.png) [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 7, 2019, 1:56am UTC](https://discourse.kitware.com/t/dashboard-status/308/1 "2019-09-07T01:56:17Z")

</div>

Some (not all) dashboards are back up after a change to smtk that required a matching change to ParaView.

## Issues

- kerbin is having [issues with command lines that are too long](https://open.cdash.org/viewBuildError.php?buildid=6097996). For some reason, the superbuild is not using response files for ParaView.
- ~~praxis has a [truncated log](https://open.cdash.org/viewBuildError.php?buildid=6097924) so it impossible to determine the cause of the crash without console access.~~
- ~~talosiv is [failing to build the documentation](https://open.cdash.org/viewBuildError.php?buildid=6097895) because a directory “does not exist and cannot be created.” As above, this will likely require console access.~~

---

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.kitware.com/user_avatar/discourse.kitware.com/dcthomp/32/10_2.png) [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 7, 2019, 8:58pm UTC](https://discourse.kitware.com/t/dashboard-status/308/2 "2019-09-07T20:58:02Z")

</div>

I’ve checked and praxis had what appeared to be a stale `.git/index.lock` file in its smtk source directory (it was dated August 19th; today is September 7th). I’ve removed it.

---

<div class="post-metadata">

### Author: ![Haocheng\_Liu](https://discourse.kitware.com/user_avatar/discourse.kitware.com/haocheng_liu/32/36_2.png) [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 9, 2019, 12:25pm UTC](https://discourse.kitware.com/t/dashboard-status/308/3 "2019-09-09T12:25:44Z")

</div>

I can take a look on Kerbin this week.

---

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.kitware.com/user_avatar/discourse.kitware.com/dcthomp/32/10_2.png) [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 9, 2019, 2:19pm UTC](https://discourse.kitware.com/t/dashboard-status/308/4 "2019-09-09T14:19:06Z")

</div>

I think the issue is that the superbuild is not configured to use response files when building paraview. This prevents the superbuild from completing and thus an old paraview (without the required changes) is used when trying to build smtk’s master branch. I don’t know how Ben sets things up to use response files.

---

<div class="post-metadata">

### Author: ![tj.corona](https://discourse.kitware.com/user_avatar/discourse.kitware.com/tj.corona/32/35_2.png) [@tj.corona](https://discourse.kitware.com/u/tj.corona)
#### Post date: [September 9, 2019, 2:22pm UTC](https://discourse.kitware.com/t/dashboard-status/308/5 "2019-09-09T14:22:00Z")

</div>

`-DCMAKE_NINJA_FORCE_RESPONSE_FILE:BOOL=ON`

---

<div class="post-metadata">

### Author: ![Haocheng\_Liu](https://discourse.kitware.com/user_avatar/discourse.kitware.com/haocheng_liu/32/36_2.png) [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 9, 2019, 5:09pm UTC](https://discourse.kitware.com/t/dashboard-status/308/6 "2019-09-09T17:09:50Z")

</div>

> [@tj.corona](#):
>
> CMAKE\_NINJA\_FORCE\_RESPONSE\_FILE

Trying it right now.

PS: The ninja on Kerbin is too old to support it. I just bumped its version to be 1.9.0.
