🌐 AI搜索 & 代理 主页
Skip to content

DRA: add new e2e tests for extended resources #135691

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.

Sign up for GitHub

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

Jump to bottom
Open
bart0sh wants to merge 1 commit into
base: master
Choose a base branch
from
Open

DRA: add new e2e tests for extended resources #135691

bart0sh wants to merge 1 commit into from
+127 −0

Conversation

@bart0sh
Copy link
Contributor

@bart0sh bart0sh commented Dec 10, 2025

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

DRA: add 5 new e2e tests to increase e2e coverage for the DRAExtendedResources code.

Which issue(s) this PR is related to:

Ref: #133675

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Dec 10, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 10, 2025

Please note that we're already in Test Freeze for the release-1.35 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.35.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Dec 10 03:39:32 UTC 2025.

@k8s-ci-robot k8s-ci-robot added do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Dec 10, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 10, 2025

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions 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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Dec 10, 2025
@k8s-ci-robot k8s-ci-robot added area/test sig/node Categorizes an issue or PR as relevant to SIG Node. labels Dec 10, 2025
@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Dec 10, 2025
@k8s-ci-robot k8s-ci-robot added wg/device-management Categorizes an issue or PR as relevant to WG Device Management. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 10, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 10, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bart0sh
Once this PR has been reviewed and has the lgtm label, please assign pohly for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@bart0sh bart0sh moved this from Triage to Needs Reviewer in SIG Node: code and documentation PRs Dec 10, 2025
@bart0sh bart0sh force-pushed the PR210-DRA-e2e-add-extended-resources-tests branch from ec491b8 to 8a573b9 Compare December 10, 2025 08:11
@pohly pohly moved this from 🆕 New to 👀 In review in Dynamic Resource Allocation Dec 10, 2025
@bart0sh
Copy link
Contributor Author

bart0sh commented Dec 10, 2025

/assign @yliaog
for review

@bart0sh
Copy link
Contributor Author

bart0sh commented Dec 11, 2025

/retest

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 11, 2025 •
edited
Loading

@bart0sh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-dra-integration 8a573b9 link false /test pull-kubernetes-dra-integration

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@klueska klueska Awaiting requested review from klueska

@pohly pohly Awaiting requested review from pohly

Assignees

@yliaog yliaog

Labels

area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. wg/device-management Categorizes an issue or PR as relevant to WG Device Management.

Projects

Dynamic Resource Allocation
Status: 👀 In review
SIG Node CI/Test Board
Status: Triage
SIG Node: code and documentation PRs
Status: Needs Reviewer

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@bart0sh @k8s-ci-robot @yliaog