linkerd2/test
Alejandro Pedraza 368d16f23c
Fix auto-injecting pods and integration tests reporting (#3335)
* Fix auto-injecting pods and integration tests reporting

When creating an Event when auto-injection occurs (#3316) we try to
fetch the parent object to associate the event to it. If the parent
doesn't exist (like in the case of stand-alone pods) the event isn't
created. I had missed dealing with one part where that parent was
expected.

This also adds a new integration test that I verified fails before this
fix.

Finally, I removed from `_test-run.sh` some `|| exit_code=$?` that was
preventing the whole suite to report failure whenever one of the tests
in `/tests` failed.

Signed-off-by: Alejandro Pedraza <alejandro@buoyant.io>
2019-08-28 15:04:20 -05:00
..
egress Improve object cleanup when integration tests fail (#3080) 2019-07-12 15:01:10 -05:00
get Introduce Cluster Heartbeat cronjob (#3056) 2019-07-23 17:12:30 -07:00
inject Fix auto-injecting pods and integration tests reporting (#3335) 2019-08-28 15:04:20 -05:00
routes Move tap service into its own pod. (#2773) 2019-05-15 16:28:44 -05:00
serviceprofiles Update ServiceProfile CRD to version v1alpha2 and remove validation (#3078) 2019-07-23 11:46:31 -07:00
stat Return invalid argument for external name services (#3120) 2019-07-29 16:31:22 -07:00
tap Improve object cleanup when integration tests fail (#3080) 2019-07-12 15:01:10 -05:00
testdata Add "can create cronjobs" to linkerd check (#3133) 2019-07-26 13:09:41 -07:00
install_test.go Update warning event regex for integration test (#3336) 2019-08-28 10:19:40 -07:00