Skip to content

Conversation

KeenonLee
Copy link
Member

test panicked: Asset test/extended/testdata/oap/mustgather not found

@KeenonLee
Copy link
Member Author

/assign @ming1013

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KeenonLee

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

@openshift-ci openshift-ci bot requested review from ming1013 and rioliu-rh October 13, 2025 08:42
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
@KeenonLee
Copy link
Member Author

Hi @ming1013 ,Please help to take a look, THX

@KeenonLee KeenonLee changed the title Sync the test template for MG MG-110: Sync the test template for MG Oct 13, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 13, 2025

@KeenonLee: This pull request references MG-110 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

test panicked: Asset test/extended/testdata/oap/mustgather not found

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 openshift-eng/jira-lifecycle-plugin repository.

@ming1013
Copy link
Contributor

Shall we still need to do this? Since there is a w/a to replace bindata.go via overlay mechanism. So OTP users don’t have to update template files and bindatago in origin but to maintain them separately.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 17, 2025

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

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 01d62dc link false /test okd-scos-e2e-aws-ovn
ci/prow/go-verify-deps 01d62dc link true /test go-verify-deps

Full PR test history. Your PR dashboard.

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.

@ming1013
Copy link
Contributor

@KeenonLee According what we discussed, I think we can close this PR. WDYT?

@KeenonLee
Copy link
Member Author

@ming1013 I just need to modify it in the testdata of OTP, right?

@KeenonLee KeenonLee closed this Oct 20, 2025
@ming1013
Copy link
Contributor

@ming1013 I just need to modify it in the testdata of OTP, right?

In OTP or after the test code is migrated then in your component repo.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants