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

remove suite hook configuration and make information flow one-way #28090

Merged
merged 3 commits into from Jul 26, 2023

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jul 24, 2023

moving hooks out of the same package as the commands that run them allows us to have a starting point for a structured command with known inputs. the test suites become an input into the commands as opposed to the bi-directional dependency that we have today.

/assign @dgoodwin

  1. pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd -- correct
  2. pull-ci-openshift-origin-master-e2e-aws-csi -- correct
  3. pull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2 -- 3674/3676
  4. pull-ci-openshift-origin-master-e2e-aws-ovn-fips - 3674/3676
  5. pull-ci-openshift-origin-master-e2e-aws-ovn-serial - 995/996
  6. pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade - 4172/4175
  7. pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade - 579/580
  8. pull-ci-openshift-origin-master-e2e-gcp-csi -- correct
  9. pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade - 577/578
  10. pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6 -- 3557/3559
  11. pull-ci-openshift-origin-master-e2e-aws-ovn-single-node -- 3674/3676
  12. pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial -- 990/991
  13. pull-ci-openshift-origin-master-e2e-gcp-ovn -- 3660/3662
  14. pull-ci-openshift-origin-master-e2e-gcp-ovn-builds -- 665/666
  15. pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade -- 523/584! -- testsuite "Cluster upgrade" is MISSING
  16. pull-ci-openshift-origin-master-e2e-metal-ipi-sdn -- 3631/3633
  17. pull-ci-openshift-origin-master-e2e-openstack-ovn -- 3688/3725! -- openshift-tests is still complete. Another invocation called openstack-test-openstack appears to be completely missing. No logs, no indication of failure. Suggest chasing after merge.

numbers are against #27980 which adds tests, so this is looking great.

@openshift-ci openshift-ci bot requested review from bparees and ibihim July 24, 2023 20:08
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2023
@deads2k
Copy link
Contributor Author

deads2k commented Jul 24, 2023

/retest

@deads2k deads2k force-pushed the invariant-08-suite-hook-madness branch from 371a1e9 to 2b5e5e0 Compare July 25, 2023 17:52
@deads2k
Copy link
Contributor Author

deads2k commented Jul 25, 2023

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Jul 25, 2023

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 25, 2023
@deads2k
Copy link
Contributor Author

deads2k commented Jul 26, 2023

  1. pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade -- 523/584! -- testsuite "Cluster upgrade" is MISSING

do not merge until resolved. Interestingly, it appears in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/28090/pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade/1683898197027590144 and doesn't appear in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/28090/pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade/1683898196247449600

@deads2k
Copy link
Contributor Author

deads2k commented Jul 26, 2023

OH, it didn't start the upgrade for RT

{ fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:209]: cluster is reporting a failing condition: Cluster operator dns is degraded

/retest

@@ -13,6 +12,10 @@ import (
"syscall"
"time"

"github.com/openshift/origin/pkg/test_suite_definition"
Copy link
Contributor

Choose a reason for hiding this comment

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

Via https://go.dev/blog/package-names

"Good package names are short and clear. They are lower case, with no under_scores or mixedCaps. They are often simple nouns"

I would suggest just "suites" here, or "testsuites".


We describe test suites sufficiently for our suite runners and e2e monitor to understand
what setup, monitoring, and invariant tests should be enforced.
We have those react to this information instead of the other way around because we can know the
Copy link
Contributor

Choose a reason for hiding this comment

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

Good README, but "those" should be clarified here.

This package contains the definition of all test suites.

We describe test suites sufficiently for our suite runners and e2e monitor to understand
what setup, monitoring, and invariant tests should be enforced.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is "run" clearer than "enforced" here?

@@ -0,0 +1,10 @@
This package contains the definition of all test suites.

We describe test suites sufficiently for our suite runners and e2e monitor to understand
Copy link
Contributor

Choose a reason for hiding this comment

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

Confused by e2e monitor here, vs "monitoring" in the subsequent part of the sentence, are they not the same thing?

@dgoodwin
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 26, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, dgoodwin

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

@deads2k
Copy link
Contributor Author

deads2k commented Jul 26, 2023

openstack didn't install. Not going to wait on that one, but

/retest

for history.

@deads2k
Copy link
Contributor Author

deads2k commented Jul 26, 2023

plan to button merge on the correct number of tests in ovn-rt-upgrade.

@deads2k
Copy link
Contributor Author

deads2k commented Jul 26, 2023

583

/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 Jul 26, 2023
@deads2k deads2k merged commit 451c57e into openshift:master Jul 26, 2023
20 of 23 checks passed
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.

None yet

3 participants