Closed upodroid closed 1 year ago
It looks like the CI failed because some hardcode in k/k shell scripts. I raise a PR about env KUBE_BUILD_PLATFROMS in https://github.com/kubernetes/kubernetes/pull/120100
/retest
/retest
/retest
/retest /approve /lgtm
/assign @michelle192837
/retest
/retest
@upodroid: 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 | 00cf8d7bdec5ca725224c9f862eef8e3808f0da3 | link | true | /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.
/skip pull-kubetest2-aws-node-e2e
@michelle192837 Can you approve this, please? we can ignore the failing AWS test as it is unrelated to this change.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dims, michelle192837, upodroid
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Sorry, missed it in emails. Approved!
/cc @dims @tzneal
~In theory, all we need to do to run arm e2e tests on GCP is to compile arm binaries, create VMs with arm machine types and use the arm images~
k/k cluster scripts are too buggy right now to support arm64 building, but the feature is required for passing env variables to the kube-*.sh scripts.
I'll create a separate job to run the legacy-mode tests