# SMTK dashboard issues

**URL:** https://discourse.kitware.com/t/smtk-dashboard-issues/608
**Category:** Software Process
**Created:** [February 20, 2021, 6:21pm UTC](https://discourse.kitware.com/t/smtk-dashboard-issues/608 "2021-02-20T18:21:32Z")
**Posts on this page:** 3
**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: [February 20, 2021, 6:21pm UTC](https://discourse.kitware.com/t/smtk-dashboard-issues/608/1 "2021-02-20T18:21:32Z")

</div>

@ben.boeckel The [failures on smtk master](https://open.cdash.org/viewTest.php?onlyfailed&buildid=7055644) look related to plugin paths (`Could not find View Type: pqSMTKResourceBrowser skipping view` ) indicate plugins are not being loaded. Could this be related to your recent superbuild changes? … and if so, will fixing paraview’s SLACTools.qch issue and updating the docker images resolve it?

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.kitware.com/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.kitware.com/u/ben.boeckel)
#### Post date: [February 21, 2021, 1:27pm UTC](https://discourse.kitware.com/t/smtk-dashboard-issues/608/2 "2021-02-21T13:27:07Z")

</div>

The superbuild updates have nothing to do with any of the repo CI results until CI bundles are updated. The superbuild bundles for SMTK were last updated at the end of Nov 2020, so I’d like to see the results of a more recent ParaView.

---

<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: [February 21, 2021, 3:57pm UTC](https://discourse.kitware.com/t/smtk-dashboard-issues/608/3 "2021-02-21T15:57:26Z")

</div>

I have an [SMTK MR](https://gitlab.kitware.com/cmb/smtk/-/merge_requests/2389) up that should bump SMTK’ runners to the latest superbuild. It had [one error](https://open.cdash.org/test/348416390) that I thought I fixed (the cdash board was clean) but the pipeline failed because the UBsan runner had [the same test fail](https://gitlab.kitware.com/cmb/smtk/-/jobs/5552235). Is there a way to see the test output from ubsan?
