Enable metrics in our upstream test suite#1511
Enable metrics in our upstream test suite#1511openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (3)
WalkthroughAdds Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
8be2e2b to
c7b3ed0
Compare
2427b6a to
60fcc26
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@upstream/kueue/patch/test_util_e2e.patch`:
- Around line 8-18: The CreateNamespaceFromObjectWithLog helper was changed to
forcibly add the managed label and directly call k8sClient.Create/assert, which
makes the helper non-neutral; revert it to its original neutral behavior by
removing the label mutation, removal of the direct k8sClient.Create() call and
the extra Expect(), and restore the original MustCreate(ctx, k8sClient, ns) call
and logging of ns.Name in CreateNamespaceFromObjectWithLog; if tests need an
opt-in managed namespace, add a new helper (e.g., CreateManagedNamespaceWithLog)
that sets ns.Labels["kueue.openshift.io/managed"]="true" and creates it
explicitly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7538ad79-5f69-44aa-b588-249eb717fe85
📒 Files selected for processing (4)
test/e2e/bindata/assets/08_kueue_default.yamlupstream/kueue/e2e-test-ocp.shupstream/kueue/patch/README.mdupstream/kueue/patch/test_util_e2e.patch
✅ Files skipped from review due to trivial changes (3)
- upstream/kueue/patch/README.md
- test/e2e/bindata/assets/08_kueue_default.yaml
- upstream/kueue/e2e-test-ocp.sh
60fcc26 to
19a4b14
Compare
19a4b14 to
c38e145
Compare
|
/retest |
1 similar comment
|
/retest |
| g.Expect(err).NotTo(gomega.HaveOccurred()) | ||
| g.Expect(metricsOutput).Should(utiltesting.ContainMetrics(metrics)) | ||
| - }, LongTimeout, Interval).Should(gomega.Succeed()) | ||
| + }, VeryLongTimeout, Interval).Should(gomega.Succeed()) |
There was a problem hiding this comment.
Did you have a chance to check why metrics are taking longer to be available and not available?
There was a problem hiding this comment.
Hmm. Maybe I can try removing this.
I noticed that sometimes the metrics were stuck with leader and haven't finished the leader election.
And it seems that they were running before Kueue was fully ready.
There was a problem hiding this comment.
If you think this can help with avoiding races, I'm fine with it.
There was a problem hiding this comment.
yea let's leave it for now.
| spec: | ||
| managementState: Managed | ||
| config: | ||
| preemption: |
There was a problem hiding this comment.
Just to keep track, this was needed because of this metric https://github.com/kubernetes-sigs/kueue/blob/f6cc162d758d5c2f2cf8c584dfd80b8e1e7749d7/test/e2e/singlecluster/metrics_test.go#L159C5-L159C63
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kannon92, MaysaMacedo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@kannon92: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
https://issues.redhat.com/browse/OCPKUEUE-547