expose project creation failures

[deads2k]

Necessary, but not sufficient for #4473.

I suspect that project creation failed (possibly due to weird etcd problems), but the project create failure was suppressed. This exposes it so we'll be able to see what's broken next time.

@liggitt or @sosiouxme

[liggitt]

lgtm, [merge]

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/3212/) (Image: devenv-fedora_2275)

[openshift-bot]

[Test]ing while waiting on the merge queue

[openshift-bot]

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/4717/)

[openshift-bot]

Evaluated for origin test up to ba10596

[smarterclayton]

[merge]

[openshift-bot]

Evaluated for origin merge up to ba10596

[deads2k]

Note for me to look at friday: https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/4717/consoleText

You don't have any projects. You can try to create a new project, by running

    $ oc new-project <projectname>

!!! Error in hack/test-cmd.sh:223
  '[ "$(oc login --token=${temp_token} 2>&1 | grep 'using the token provided')" ]' exited with status 1
Call stack:
  1: hack/test-cmd.sh:223 main(...)
Exiting with status 1

[deads2k]

@smarterclayton How do you feel about killing the server and restarting between test-cmd scripts to see if it increases stability?

[smarterclayton]

Yuck. Why do we suddenly have test cmd stability problems? Racing against
controllers is only reason?

On Sep 2, 2015, at 7:11 PM, David Eads notifications@github.com wrote:

@smarterclayton https://github.com/smarterclayton How do you feel about
killing the server and restarting between test-cmd scripts to see if it
increases stability?

—
Reply to this email directly or view it on GitHub
#4475 (comment).