KokkosKernels CI build failure on 4/12/2017
Created by: bartlettroscoe
A KokkosKernels build failure was caught by the standard CI build:
in the first CI iteration this morning:
(which suggests the checkin-test-sems.sh script should have caught this build failure before the push). But this was only a test/example failure which does not disable KokkosKernels in downstream packages. (Note that we will lose this behavior once we do the single configure, build, and tests https://github.com/TriBITSPub/TriBITS/issues/183 ).
But it looks like @crtrott reacted to this quickly fixed the KokkosKernels in the latest CI build iteration:
Note that since this was only a test/example failure for KokkosKernels, this would not have stopped anyone else's pushes using the checkin-test-sems.sh script where were only changing a package downstream from KokkosKernels.
Just added this issue to document this failure since it was interesting for a few reasons:
- The build failure should have likely have been caused by the checkin-test-sems.sh script
- The failure was seen and fixed in the very next CI iteration
- This was only a build failure for examples/tests so this would not have blocked anyone else's push to changes in packages downstream from KokkosKernels
Since Trilinos CDash info is forgotten pretty quickly (just a month or so).