3
71%
master: 71%

Ran 25 Jul 2018 03:14AM UTC

Files 4

Run time 1s

Badge

Embed ▾

Committed 25 Jul 2018 03:10AM UTC coverage: 61.654%. Remained the same

Job # 1780.3

Build Type

push

travis-ci

Committed by

k8s-ci-robot

Commit Message

Prevent multiple versions of an E2E test from clobbering each other. (#749)

* Prevent multiple versions of an E2E test from clobbering each other.

* It turns out that although we running the v1alpha2 tests, failures
  were not being properly reported in Prow because the junit xml files
  had the same names for the v2 pipeline as the v1 pipeline and the v2
  results were being clobbered by v1.

* Ensure the artifacts for each run of the E2E test have a unix name
  based on the TFJob version so that the E2E tests for the different
  TFJob versions won't clobber each other.

* Log the exception in wait for condition.

* Need to pass --tfjob_version to the tests so it uses the proper client.

* run_gpu and run_test stage need to use a v1alpha2 version of the test
  workflow.

* Update the tf_smoke program to accept chief as a valid worker type so that
  it works with v1alpha2.

* In v1alpha2 we need to terminate all workers. It looks like there was a
regression in v1alpha2
  https://github.com/kubeflow/tf-operator/issues/751
  and we require all workers to terminate as opposed to just worker 0.

* Delete a bunch of environments for the test app that shouldn't have been
  committed.

Fix #748

* * Use kubeflow/testing@HEAD rather than the hack of pinning PR
  kubeflow/testing#183 which I was using to test.

Run Details

82 of 133 relevant lines covered (61.65%)

3.1 hits per line

kubeflow / tf-operator / 1780 / 3
71%
master: 71%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1780.3

kubeflow / tf-operator / 1780 / 3 71% master: 71%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1780.3

kubeflow / tf-operator / 1780 / 3
71%
master: 71%

README BADGES
x