-
Notifications
You must be signed in to change notification settings - Fork 551
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
Makefile: Update the e2e target to use ginkgo #2367
Conversation
cf87cef
to
8766239
Compare
415ad4f
to
ea5af1c
Compare
/approve |
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 <[email protected]>
ea5af1c
to
729f57f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[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 |
Force (squash) merging as the e2e-test failures aren't relevant to the changes in this PR - #2383 |
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 <[email protected]>
Description of the change:
Update the root Makefile and update the
e2e
target to use the ginkgoexecutable instead of
go test ...
as logs produce when running the e2esuite 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
/doc