Analysis of configure and build failures due to KokkosKernels pushes on March 1-2 reported in #1099
Created by: bartlettroscoe
Description:
This story is to analyze the KokkosKernels commits pushed on March 1-2, 2017 that broke the configure and build of Trilinos that was reported in #1099 (closed) and see if usage of the checkin-test-sems.sh script could have avoided the failures (and resulting consequences) if it had been used for the test and push (which would have stopped the push).
This started when a set of commits were pushed to the Trilinos 'develop' branch on March 1 with the top commit 97ed757d being:
97ed757 [Wed Mar 1 08:24:01 2017 -0700] <crtrott@sandia.gov>
Kokkos-Kernels: Adding Kokkos-Kernels as a stand-alone package
as shown by the CI build:
That version of Trilinos failed to configure as shown on that CI build iteration.
Later that day, issue #1099 (closed) was created by an important Trilinos customer and it resulted in 35 comments that involved 9 people in that issue before it was resolved.
An attempt to fix this problem was pushed later that day with the top commit de7ac5a9 being:
de7ac5a [Wed Mar 1 13:17:16 2017 -0700] <mhoemme@sandia.gov>
KokkosKernels: Fix #1099
as shown by the CI build:
That version passed the configure but resulted in many build failures.
The build was not finally fixed until March 2 as shown at:
Could the usage of the checkin-test-sems.sh script have caught these problems and stop the pushes that broke the configure and build of Trilinos over these two days?
CC: @trilinos/framework, @bathmatt, @crtrott, @mhoemmen