# Dashboard superbuild failure, Kerbin
**URL:** https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324
**Category:** Software Process
**Created:** [September 26, 2019, 6:22pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324 "2019-09-26T18:22:45Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [September 26, 2019, 6:22pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/1 "2019-09-26T18:22:46Z")
Looks like we hit a known issue with the superbuild failing on Kerbin:
[CMake: ninja command line too long](https://gitlab.kitware.com/cmake/cmake/issues/16171)
Response files are the answer, but they haven’t been implemented in CMake for compiling .rc files.
Paraview [hit it here](https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/490)
@tj.corona I see we use a very short root directory on Praxis, `C:\bbd` vs `C:/d/buildbot` on Kerbin. Can we make that change on Kerbin?
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 26, 2019, 6:24pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/2 "2019-09-26T18:24:57Z")
Also @tj.corona , do you know who to bug about why rc files do not seem to use response files while other files in the same build do?
---
### Author:  [@tj.corona](https://discourse.kitware.com/u/tj.corona)
#### Post date: [September 26, 2019, 6:25pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/3 "2019-09-26T18:25:30Z")
> [@aron.helser](#):
>
> Can we make that change on Kerbin?
@Haocheng_Liu is the maintainer for Kerbin so he gets final say, but I am fine with shortening the root directory.
---
### Author:  [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 26, 2019, 6:30pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/4 "2019-09-26T18:30:34Z")
> [@aron.helser](#):
>
> Looks like we hit a known issue with the superbuild failing on Kerbin:
> [ninja command line too long](https://gitlab.kitware.com/cmake/cmake/issues/16171)
> Response files are the answer, but they haven’t been implemented in CMake for compiling .rc files.
> Paraview [hit it here](https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/490)
>
> @tj.corona I see we use a very short root directory on Praxis, `C:\bbd` vs `C:/d/buildbot` on Kerbin. Can we make that change on Kerbin?
No objection here. Kerbin is hooked up on KVM so feel free to do so.
Btw I think the superbuild failure belongs to a release branch superbuild. The ParaView version in CMB release branch superbuild hasn’t learnt the response file yet.
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 26, 2019, 6:31pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/5 "2019-09-26T18:31:46Z")
> [@Haocheng\_Liu](#):
>
> Btw I think the superbuild failure belongs to a release branch superbuild
No, response files are definitely being used in the same ParaView build, but not for rc files.
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [September 26, 2019, 6:31pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/6 "2019-09-26T18:31:57Z")
If someone wants to tell me how, I’m happy to…
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 26, 2019, 6:32pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/7 "2019-09-26T18:32:57Z")
… or are you saying that ParaView changes were required for using response files with rc files?
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 26, 2019, 6:34pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/8 "2019-09-26T18:34:58Z")
Hmmm… I’m not sure I know all the steps involved, but at a minimum some paths need to be updated in the buildbot repo (on our internal gitlab) in the machines/kerbin directory. The buildbot’s buildslave may also need to be configured differently?
---
### Author:  [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 26, 2019, 6:36pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/9 "2019-09-26T18:36:41Z")
> [@aron.helser](#):
>
> If someone wants to tell me how, I’m happy to…
Humm, have you modified `buildbot` repo on kwgitlab? That’s the place to change the path. Meanwhile, I don’t think it’s the right way to fix the problem… The path used to be `C:\dashboard\buildbot`. I shortened it to be `C:\d\buildbot` several years ago. Even though we short it to b `C:`, we will still hit the problem in the near future.
---
### Author:  [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 26, 2019, 6:43pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/10 "2019-09-26T18:43:09Z")
> [@dcthomp](#):
>
> … or are you saying that ParaView changes were required for using response files with rc files?
BG: I digged into Kerbin a few month ago and what I found is that ninja on Kerbin is too old to use response file. I update the ninja binary to latest on Kerbin. Also I spent some to fix the release superbuild and there was nothing I can do as the ParaView SHA for release branch does not have the response file improvement. I didn’t check the master build at that time as it was working as expected.
Is [master superbuild](https://open.cdash.org/viewBuildError.php?buildid=6129414) on kerbin failing due to response file? @aron.helser
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [September 26, 2019, 6:48pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/11 "2019-09-26T18:48:42Z")
> [@Haocheng\_Liu](#):
>
> Is [master superbuild](https://open.cdash.org/viewBuildError.php?buildid=6129414) on kerbin failing due to response file?
IDK where that build comes from? I can check… This is the one that is failing due to the response file missing only on Icon.rc: [https://open.cdash.org/buildSummary.php?buildid=6128018](https://open.cdash.org/buildSummary.php?buildid=6128018)
---
### Author:  [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 26, 2019, 6:53pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/12 "2019-09-26T18:53:24Z")
> [@aron.helser](#):
>
> > Is [master superbuild](https://open.cdash.org/viewBuildError.php?buildid=6129414) on kerbin failing due to response file?
>
> IDK where that build comes from? I can check… This is the one that is failing due to the response file missing only on Icon.rc: [https://open.cdash.org/buildSummary.php?buildid=6128018](https://open.cdash.org/buildSummary.php?buildid=6128018)
Humm, clearly response file is not being used on kerbin… Now master has the problem as well
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [September 26, 2019, 9:22pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/13 "2019-09-26T21:22:44Z")
Restarted the buildslave, using c:\bbd as the build root. Until we get traction on the CMake bug for response files when compiling .rc files, this is the best we can do. I suppose shorter QT paths might be next.
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [September 27, 2019, 1:33pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/14 "2019-09-27T13:33:40Z")
> [@aron.helser](#):
>
> I suppose shorter QT paths might be next.
+1
Also, do you have any idea why praxis is dead now? Maybe a terminal left open?
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [September 27, 2019, 2:00pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/15 "2019-09-27T14:00:48Z")
Kerbin ran to completion, with 5 expected CMB test failures.
Praxis had no obvious problem terminals open. Boost root was set to something sensible on the build that complained it couldn’t find boost. Not sure what’s up. It needed a windows update, so I just restarted it.
---
### Author:  [@Haocheng\_Liu](https://discourse.kitware.com/u/Haocheng_Liu)
#### Post date: [September 27, 2019, 5:24pm UTC](https://discourse.kitware.com/t/dashboard-superbuild-failure-kerbin/324/16 "2019-09-27T17:24:14Z")
Good to know 👍.
We can bring it up on next Tuesday weekly meeting. If you need help I can help you on path shortening next week.