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

e2e: add ginkgo decorators to address flakes #18816

Merged

Conversation

edsantiago
Copy link
Member

  • trust_test: adding 'Ordered' seems to resolve a very common
    flake. I've tested this for dozens of CI runs, and haven't
    seen the flake recur (normally it fails every few runs).

  • exec and search tests: add FlakeAttempts(3). This is a NOP
    under our current CI setup, in which we run ginkgo with
    a global --flake-attempts=3. I am submitting this as an
    optimistic step toward a no-flake-attempts world (Epic: ginkgo: remove -flakeAttempts 3 #17967)

Fixes: #18358

Signed-off-by: Ed Santiago [email protected]

None

- trust_test: adding 'Ordered' seems to resolve a very common
  flake. I've tested this for dozens of CI runs, and haven't
  seen the flake recur (normally it fails every few runs).

- exec and search tests: add FlakeAttempts(3). This is a NOP
  under our current CI setup, in which we run ginkgo with
  a global --flake-attempts=3. I am submitting this as an
  optimistic step toward a no-flake-attempts world (containers#17967)

Fixes: containers#18358

Signed-off-by: Ed Santiago <[email protected]>
@openshift-ci openshift-ci bot added release-note-none approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 7, 2023
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

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

LGTM

@mheon
Copy link
Member

mheon commented Jun 7, 2023

Restarted a Cirrus infra issue with a machine test
/lgtm
/approve
/hold

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jun 7, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago, mheon

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

@edsantiago
Copy link
Member Author

Yeah, thanks. I've restarted it about four times already, with no luck...

@Luap99
Copy link
Member

Luap99 commented Jun 7, 2023

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 7, 2023
@openshift-merge-robot openshift-merge-robot merged commit 384e937 into containers:main Jun 7, 2023
@edsantiago edsantiago deleted the ginkgo_decorators branch June 7, 2023 16:31
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 6, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

e2e: image trust: Getting key identity: exit status 2
4 participants