kubernetes-mesos icon indicating copy to clipboard operation
kubernetes-mesos copied to clipboard

AS a Quality Engineer I WANT to have clarity regarding which test script harness is running the unit/integration/smoke/conformance/end-to-end tests for a particular test run.

Open jdef opened this issue 10 years ago • 4 comments

  • initial ask: https://github.com/kubernetes/kubernetes/pull/17180#issuecomment-159393049
  • upstream response:
    • https://github.com/kubernetes/kubernetes/pull/17735
    • https://github.com/kubernetes/kubernetes/pull/17736
    • https://github.com/kubernetes/kubernetes/issues/17734
    • https://github.com/kubernetes/kubernetes/pull/17749
    • https://github.com/kubernetes/kubernetes/pull/17750
  • … upstream response was complicated

looks to be resolving here: https://github.com/kubernetes/kubernetes/issues/18162

jdef avatar Dec 09 '15 19:12 jdef

In fact kubernetes/kubernetes#18162 proposes what we already did with our conformance claim.

sttts avatar Dec 09 '15 20:12 sttts

Is this fixed?

sttts avatar Jan 06 '16 07:01 sttts

There's probably some more work to do to start running the release-1.1 conformance tests against master, but it's just a matter of putting it in TeamCity.

karlkfi avatar Jan 06 '16 19:01 karlkfi

TODO:

  • [ ] run release-1.1 conformance tests against master code
  • [x] re-enable master against master conformance (once kubectl/job timeouts problems are fixed)

jdef avatar Jan 07 '16 17:01 jdef