Files
kubernetes/hack
Phillip Wittrock c3e1c12985 Kubemark e2e tests should exit 0 for test failures.
Jenkins relies on junit.xml to identify test failures
and non-0 exit codes to indentify infrastructure failures.
Test failures in kubemark tests should not cause the test
script to exit non-0.  Infrastructure failures should.

- Add function to dump cluster logs without exiting (refactor)
- Change `test/kubemark/stop-kubemark.sh` to be run regardless of whether tests fail or not
- Exit code for failed tests overwritten to be the exit code of dumping the cluster logs
2016-05-27 15:45:18 -07:00
..
2016-05-14 23:19:18 -07:00
2016-05-12 22:04:19 -04:00
2016-03-02 20:46:32 -05:00
2016-05-13 12:41:40 -07:00
2016-05-08 20:30:39 -07:00
2016-05-08 20:30:37 -07:00
2016-04-20 12:12:29 -04:00
2016-05-08 20:30:39 -07:00
2016-05-26 10:27:45 -07:00