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
[release-4.8] Bug 1988478: Use kernel config to determine GCC version #55
[release-4.8] Bug 1988478: Use kernel config to determine GCC version #55
Conversation
extract-vmlinux does not work on aarch64 and s390x due to the kernel formats used thereon. This is more portable.
/bugzilla refresh |
@yselkowitz: This pull request references Bugzilla bug 1988123, which is invalid:
Comment In response to this:
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/test-infra repository. |
@openshift-cherrypick-robot: Bugzilla bug 1988123 has been cloned as Bugzilla bug 1988478. Retitling PR to link against new bug. In response to this:
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/test-infra repository. |
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1988478, which is invalid:
Comment In response to this:
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/test-infra repository. |
/bugzilla refresh |
@dagrayvid: This pull request references Bugzilla bug 1988478, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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/test-infra repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dagrayvid, openshift-cherrypick-robot 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 |
/cherry-pick release-4.7 |
@yselkowitz: once the present PR merges, I will cherry-pick it on top of release-4.7 in a new PR and assign it to you. In response to this:
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/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
/bugzilla refresh |
@dagrayvid: This pull request references Bugzilla bug 1988478, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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/test-infra repository. |
Tagging because it's urgent - shouldn't have skipped it in today's batch |
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: Bugzilla bug 1988478 has been moved to the MODIFIED state. In response to this:
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/test-infra repository. |
@yselkowitz: new pull request created: #56 In response to this:
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/test-infra repository. |
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
This is an automated cherry-pick of #52
/assign yselkowitz