Skip to content

Conversation

ggiguash
Copy link
Contributor

Manual cherry-pick of #4340 due to bootc test structure changes.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 19, 2024
@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-47463, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-47463 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Manual cherry-pick of #4340 due to bootc test structure changes.

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.

@openshift-ci openshift-ci bot requested review from agullon and jogeo December 19, 2024 16:10
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 19, 2024
@ggiguash
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-47463, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-47462 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@ggiguash
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-47463, which is invalid:

  • expected dependent Jira Issue OCPBUGS-47462 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@ggiguash
Copy link
Contributor Author

The following failure seems to be related to the #4338 fix.

+ 17:18:40.399471162 ./bin/scenario.sh:953 	timeout -v --kill-after=5m 30m /home/ec2-user/microshift/_output/robotenv/bin/robot --name cos9-src@standard-suite2 --randomize all --loglevel TRACE --outputdir /home/ec2-user/microshift/_output/test-images/scenario-info/cos9-src@standard-suite2 --debugfile /home/ec2-user/microshift/_output/test-images/scenario-info/cos9-src@standard-suite2/rf-debug.log -x junit.xml -V /home/ec2-user/microshift/_output/test-images/scenario-info/cos9-src@standard-suite2/variables.yaml suites/standard2
...
...
timeout: sending signal TERM to command ‘/home/ec2-user/microshift/_output/robotenv/bin/robot’
Second signal will force exit.
timeout: sending signal KILL to command ‘/home/ec2-user/microshift/_output/robotenv/bin/robot’
./bin/scenario.sh: line 867: 319286 Killed                  ${timeout_robot} --name "${SCENARIO}" --randomize "${TEST_RANDOMIZATION}" --loglevel TRACE --outputdir "${SCENARIO_INFO_DIR}/${SCENARIO}" --debugfile "${SCENARIO_INFO_DIR}/${SCENARIO}/rf-debug.log" -x junit.xml ${var_arg} "$@"
+ 17:53:40.403659756 ./bin/scenario.sh:962 	'[' 0 -ge 124 ']'
+ 17:53:40.404982764 ./bin/scenario.sh:965 	return 1

@ggiguash ggiguash changed the title OCPBUGS-47463: [release-4.18] Raise the default greenboot timeout to 600s [release-4.18] OCPBUGS-47463: Raise the default greenboot timeout to 600s Dec 20, 2024
@ggiguash ggiguash closed this Dec 21, 2024
@ggiguash ggiguash deleted the raise_greenboot_timeout_419 branch December 21, 2024 06:46
@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-47463. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

Manual cherry-pick of #4340 due to bootc test structure changes.

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.

@ggiguash
Copy link
Contributor Author

/retest-required

@ggiguash ggiguash restored the raise_greenboot_timeout_419 branch December 21, 2024 07:39
@ggiguash ggiguash reopened this Dec 21, 2024
@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-47463, which is invalid:

  • expected dependent Jira Issue OCPBUGS-47462 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Manual cherry-pick of #4340 due to bootc test structure changes.

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.

@pacevedom
Copy link
Contributor

/retest

@ggiguash
Copy link
Contributor Author

/test test-rpm

1 similar comment
@ggiguash
Copy link
Contributor Author

/test test-rpm

@ggiguash
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/test test-rpm

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Dec 23, 2024
Copy link
Contributor

openshift-ci bot commented Dec 23, 2024

@ggiguash: all tests passed!

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.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm
/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 23, 2024
Copy link
Contributor

openshift-ci bot commented Dec 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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

@pacevedom
Copy link
Contributor

/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Dec 23, 2024
@ggiguash
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 23, 2024
@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-47463, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
  • expected dependent Jira Issue OCPBUGS-47462 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Retaining the jira/valid-bug label as it was manually added.

In response to this:

/jira refresh

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 15d0548 into openshift:release-4.18 Dec 23, 2024
10 checks passed
@openshift-ci-robot
Copy link

@ggiguash: Jira Issue OCPBUGS-47463 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Manual cherry-pick of #4340 due to bootc test structure changes.

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.

@ggiguash ggiguash deleted the raise_greenboot_timeout_419 branch December 26, 2024 06:51
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants