kubernetes-sigs
Add s390x architecture to kubetest2 available archs
The addition of the s390x arch worked fine when I ran make ci-binaries. The resulting file had the below details when built on an x86 machine:
root@pt1:~/kubetest2/bin/linux/s390x# file kubetest2
kubetest2: ELF 64-bit MSB executable, IBM S/390, version 1 (SYSV), statically linked, with debug_info, not stripped
This change is needed for kubekins-e2e-v2 support on s390x. As at https://github.com/kubernetes/test-infra/blob/master/images/kubekins-e2e-v2/Dockerfile#L168 kubetest2 is referred.
kubekins issue : https://github.com/kubernetes/test-infra/issues/34646
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: prabhav-thali / name: Prabhav Thali (64330e419c6af60a78492e594269878e9b521fc7)
![linux-foundation-easycla[bot] avatar](https://avatars.githubusercontent.com/in/17893?v=4 "Published by a pub.dev verified publisher"){kind=small}
Welcome @prabhav-thali!
It looks like this is your first PR to kubernetes-sigs/kubetest2 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/kubetest2 has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @prabhav-thali. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: prabhav-thali, upodroid
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [upodroid]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@prabhav-thali: 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-kubetest2-aws-node-e2e | 64330e419c6af60a78492e594269878e9b521fc7 | link | false | /test pull-kubetest2-aws-node-e2e |
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.