Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable direct CLI invocation, shrink e2e tests #4771

Merged
merged 3 commits into from Sep 25, 2015

Conversation

smarterclayton
Copy link
Contributor

In preparation to move to a package based test model, make two changes:

  1. No longer directly import the CLI - instead use oc like all other tests
  2. Do not directly import the entire master component into test/util

The combined result shrinks the e2e package to around ~35M compiled which is 2-3x faster - that will enable us to move to a more idiomatic Ginkgo style where we execute packages directly.

Also disable parallelism as it was causing resource exhaustion issues (may reintroduce later).

@smarterclayton
Copy link
Contributor Author

@mfojtik @deads2k @bparees changes to the extended tests

@smarterclayton
Copy link
Contributor Author

[test][extended:core]

@openshift-bot
Copy link
Contributor

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

@mfojtik
Copy link
Member

mfojtik commented Sep 23, 2015

@smarterclayton cool! this seems much better than building with CLI... it also means you need to have 'oc' binary when running the tests, but I think that is reasonable trade-off. I will review this tomorrow.

@smarterclayton
Copy link
Contributor Author

[test][extended:core]

@@ -97,4 +97,4 @@ fi
echo "[INFO] Running extended tests"

# Run the tests
TMPDIR=${BASETMPDIR} ginkgo -progress -stream -v -p "-skip=${SKIP}" "$@" ${OS_OUTPUT_BINPATH}/extended.test
TMPDIR=${BASETMPDIR} ginkgo -progress -stream -v "-skip=${SKIP}" "$@" ${OS_OUTPUT_BINPATH}/extended.test
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this mean we are no longer running parallel?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, for now. When I split the packages up I will run upstream non parallel, then us parallel

@mfojtik
Copy link
Member

mfojtik commented Sep 24, 2015

Couple small nits and questions but otherwise LGTM!

@mfojtik
Copy link
Member

mfojtik commented Sep 24, 2015

@smarterclayton I will have to rework the start-build extended test for this :-)

@mfojtik
Copy link
Member

mfojtik commented Sep 24, 2015

@mnagy tag :)

@smarterclayton
Copy link
Contributor Author

[test]

@smarterclayton
Copy link
Contributor Author

[merge]

@openshift-bot
Copy link
Contributor

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

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 9a6a204

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 9a6a204

openshift-bot pushed a commit that referenced this pull request Sep 25, 2015
@openshift-bot openshift-bot merged commit 6092653 into openshift:master Sep 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants