# RogueResearch buildbots errors
**URL:** https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307
**Category:** Support
**Created:** [August 5, 2021, 4:50pm UTC](https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307 "2021-08-05T16:50:59Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@seanm](https://discourse.vtk.org/u/seanm)
#### Post date: [August 5, 2021, 4:50pm UTC](https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307/1 "2021-08-05T16:50:59Z")
So I’ve just done a bit of triage on my vtk cdash submissions and there are lots of new errors & warnings there that should be fixed. It would take me most of a day to `git blame` every one of them and contact the person that introduced the issue. Nonetheless, I did this for errors (but not warnings).
I have 2 more concrete suggestions for improving this situation:
1. Increase the warning settings that the gitlab buildbots use. For macOS, I have very fine grained warning settings that I can share. I guess with @ben.boeckel ? If you tell me the Xcode versions of your bots, I can give you corresponding warning flags.
2. Figure out why 3rd party lib warnings appear on cdash. I thought there was already a mechanism to remove such warnings, yet I see hdf5 warnings here for example:
[https://open.cdash.org/viewBuildError.php?type=1&buildid=7383149](https://open.cdash.org/viewBuildError.php?type=1&buildid=7383149)
Sean
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [August 5, 2021, 5:10pm UTC](https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307/2 "2021-08-05T17:10:30Z")
> [@seanm](#):
>
> For macOS, I have very fine grained warning settings that I can share. I guess with @ben.boeckel ? If you tell me the Xcode versions of your bots, I can give you corresponding warning flags.
I’d like to see additional warning flags gated behind a CMake option so that developers can easily enable them as well. CI can then just flip that flag in `.gitlab/ci/configure_common.cmake`. See `CMake/vtkSanitize.cmake` and `CMake/vtkSanitizeFlags.cmake` (separated so that some of the setup logic is not affected).
> [@seanm](#):
>
> Figure out why 3rd party lib warnings appear on cdash. I thought there was already a mechanism to remove such warnings, yet I see hdf5 warnings here for example:
Are you doing `ctest_read_custom_files("${CTEST_BINARY_DIRECTORY}")` in your CTest script? These suppressions come from `CMake/CTestCustom.cmake.in` which is configured into the build tree.
---
### Author:  [@seanm](https://discourse.vtk.org/u/seanm)
#### Post date: [August 5, 2021, 6:09pm UTC](https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307/3 "2021-08-05T18:09:36Z")
> Are you doing `ctest_read_custom_files("${CTEST_BINARY_DIRECTORY}")` in
> your CTest script? These suppressions come from `CMake/ CTestCustom.cmake.in` which is configured into the build tree.
I see `ctest_read_custom_files(${CTEST_BINARY_DIRECTORY})` in `vtk_common.cmake`, which I include. Maybe you could take a look here:
[https://open.cdash.org/build/7383072/notes#note0](https://open.cdash.org/build/7383072/notes#note0)
to see if I’ve done anything weird…
Sean
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [August 5, 2021, 8:36pm UTC](https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307/4 "2021-08-05T20:36:29Z")
I don’t see anything odd there. Maybe try using `--trace-expand` to trace the execution and make sure it’s actually happening?
---
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [August 6, 2021, 6:32am UTC](https://discourse.vtk.org/t/rogueresearch-buildbots-errors/6307/5 "2021-08-06T06:32:09Z")
I’ve split the thread.