# Sad state of the dashboard
**URL:** https://discourse.itk.org/t/sad-state-of-the-dashboard/793
**Category:** Engineering
**Created:** [March 23, 2018, 2:35pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793 "2018-03-23T14:35:15Z")
**Posts on this page:** 17
**Page:** 1
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 23, 2018, 2:35pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/1 "2018-03-23T14:35:15Z")
Hi all,
Almost all the Mac builds on the dashboard are red, and have been for weeks now.
Mine have been red since 2018-03-08. They used to build. Isn’t the idea that if one commits something one must watch the dashboards and fix any fallout?
Cheers,
Sean
---
### Author:  [@dzenanz](https://discourse.itk.org/u/dzenanz)
#### Post date: [March 23, 2018, 2:53pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/2 "2018-03-23T14:53:10Z")
2 out of 3 builds in the nightly expected section are fully successful. [1](https://open.cdash.org/buildSummary.php?buildid=5308976) [2](https://open.cdash.org/buildSummary.php?buildid=5308930)
What are the errors you are getting? Can you submit an experimental build? `ctest -D Experimental`
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 23, 2018, 3:02pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/3 "2018-03-23T15:02:29Z")
> 2 out of 3 builds in the nightly expected section are fully successful.
> [1](https://open.cdash.org/buildSummary.php?buildid=5308976) [2](https://
> [open.cdash.org/buildSummary.php?buildid=5308930](http://open.cdash.org/buildSummary.php?buildid=5308930))
Those 2 are practically the only non-red Mac builds, scroll further down…
> What are the errors you are getting? Can you submit an experimental
> build? `ctest -D Experimental`
I submit several nightly builds already, don’t see the point in your request to submit yet another, it’ll be red too.
Cheers,
---
### Author:  [@blowekamp](https://discourse.itk.org/u/blowekamp)
#### Post date: [March 23, 2018, 3:07pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/4 "2018-03-23T15:07:09Z")
I think this patch should help with some of the compilation errors on your build:
[http://review.source.kitware.com/#/c/23277/](http://review.source.kitware.com/#/c/23277/)
---
### Author:  [@dzenanz](https://discourse.itk.org/u/dzenanz)
#### Post date: [March 23, 2018, 3:12pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/5 "2018-03-23T15:12:30Z")
> [@seanm](#):
>
> I submit several nightly builds already
I didn’t realize that RogueResearch\* are your machines, sorry.
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 23, 2018, 3:24pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/6 "2018-03-23T15:24:20Z")
Ah. I also keep forgetting that this ‘discourse’ thing strips both signatures and ‘from’ address, so yeah, the association was maybe difficult to discern.
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 23, 2018, 6:47pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/7 "2018-03-23T18:47:12Z")
Yes, we should do better with our dashboard builds and get back to a green state.
@seanm , I just merged a patch that should address your build errors.
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 26, 2018, 3:10pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/8 "2018-03-26T15:10:36Z")
That seemed to do it, thanks.
Could we move all the RogueResearch dashboards into Nightly Expected? It seems those are the ones people pay attention to.
Sean
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 26, 2018, 3:37pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/9 "2018-03-26T15:37:12Z")
> [@seanm](#):
>
> Could we move all the RogueResearch dashboards into Nightly Expected? It seems those are the ones people pay attention to.
Yes, let’s do that. First, let’s get them green, though, in the spirit of ‘get it green, keep it green’ ;-).
Could you please add `ITK_USE_KWSTYLE` to OFF in the ctest configuration since we are having trouble suppressing the boost warnings?
Thanks,
Matt
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 27, 2018, 9:03pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/10 "2018-03-27T21:03:19Z")
That seemed to work. A few are now fully green, can they be moved now at least?
Sean
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 27, 2018, 9:33pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/11 "2018-03-27T21:33:58Z")
> [@seanm](#):
>
> That seemed to work. A few are now fully green, can they be moved now at least?
Fantastic!
The builds have been moved to the `Expected Nightly` section. Thank you for contributing them!
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 27, 2018, 11:01pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/12 "2018-03-27T23:01:13Z")
“Mac10.9-clang-dbg-x86\_64-static” is also green.
“Mac10.10-clang-dbg-x86\_64-static” you can remove entirely, it was renamed.
“Mac10.11-AppleClang-rel-x86\_64-static” has just 2 test failures, OpenCL related. It seems only my bots even run these test at all:
[https://open.cdash.org/testSummary.php?project=2&name=itkGPUBinaryThresholdImageFilterTest2D&date=2018-03-27](https://open.cdash.org/testSummary.php?project=2&name=itkGPUBinaryThresholdImageFilterTest2D&date=2018-03-27)
Sean
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 27, 2018, 11:44pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/13 "2018-03-27T23:44:03Z")
> [@seanm](#):
>
> “Mac10.9-clang-dbg-x86\_64-static” is also green.
Moved.
> [@seanm](#):
>
> “Mac10.10-clang-dbg-x86\_64-static” you can remove entirely, it was renamed.
Removed.
> [@seanm](#):
>
> “Mac10.11-AppleClang-rel-x86\_64-static” has just 2 test failures, OpenCL related.
Fixes would be welcome.
Unfortunately, the GPU support never developed traction. A brighter future could be possible with a better abstraction like ArrayFire or VTK-M instead of OpenCL.
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 28, 2018, 4:33pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/14 "2018-03-28T16:33:59Z")
I’m afraid I don’t have time to work on the OpenCL tests. But I really want my dashboards in ‘nightly expected’. Do you want to move that one there anyway? Or shall I disable/suppress the OpenCL test first?
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 28, 2018, 4:40pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/15 "2018-03-28T16:40:01Z")
Please disable the OpenCL test for now.
---
### Author:  [@seanm](https://discourse.itk.org/u/seanm)
#### Post date: [March 29, 2018, 4:46pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/16 "2018-03-29T16:46:50Z")
Done. And now “Mac10.11-AppleClang-rel-x86\_64-static” is green.
“Mac10.13-AppleClang-dbg-x86\_64-ASanUBSan” had ~200 test failures, but I have it down to 3 today by removing some UBSan flags. The 3 remaining failures are all from ASan, and are not likely to be false positives. I looked at each, but none struck me as trivial. Anyone familiar with the code exercised by these tests:
itkHDF5ImageIOTest
itkMeshTest
netlib\_test\_integral
For each, ASan catches an overread of a stack-based buffer.
Sean
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 29, 2018, 9:06pm UTC](https://discourse.itk.org/t/sad-state-of-the-dashboard/793/17 "2018-03-29T21:06:46Z")
Excellent!
`Mac10.11-AppleClang-rel-x86_64-static` has been moved.