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

Makefile: Update the e2e target to use ginkgo #2367

Merged

Conversation

timflannagan
Copy link
Contributor

Description of the change:
Update the root Makefile and update the e2e target to use the ginkgo
executable instead of go test ... as logs produce when running the e2e
suite aren't captured until after the process has completed. This leads
to situations where failing tests aren't immediately communicated back
and loss of logs entirely in the case where the process was manually
teminated.

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive

Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
@timflannagan timflannagan force-pushed the update-make-e2e-target branch 2 times, most recently from 415ad4f to ea5af1c Compare September 21, 2021 18:56
@njhale
Copy link
Member

njhale commented Sep 22, 2021

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 22, 2021
@timflannagan timflannagan reopened this Sep 23, 2021
Update the root Makefile and update the `e2e` target to use the ginkgo
executable instead of `go test ...` as logs produce when running the e2e
suite aren't captured until after the process has completed. This leads
to situations where failing tests aren't immediately communicated back
and loss of logs entirely in the case where the process was manually
teminated.

Signed-off-by: timflannagan <timflannagan@gmail.com>
Copy link
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 30, 2021
@openshift-ci
Copy link

openshift-ci bot commented Sep 30, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dinhxuanvu, njhale, timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@timflannagan
Copy link
Contributor Author

Force (squash) merging as the e2e-test failures aren't relevant to the changes in this PR - #2383

@timflannagan timflannagan merged commit 584e12a into operator-framework:master Oct 1, 2021
@timflannagan timflannagan deleted the update-make-e2e-target branch October 1, 2021 01:32
timflannagan added a commit to ankitathomas/operator-framework-olm that referenced this pull request Oct 1, 2021
Update the root Makefile and extend the e2e/olm target to explicitly
configure the ginkgo options that gets filtered to the
staging/operator-lifecycle-manager e2e target that was introduced in [1].

[1] operator-framework/operator-lifecycle-manager#2367

Signed-off-by: timflannagan <timflannagan@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants