ubuntu_k8s_unit_tests sub tests failed to build with gcc: cannot allocate memory on X-4.15-GCP

Bug #1959430 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

This is not a regression, we have changed how we run this test for different releases in this commit:
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/commit/?id=e4b72827b7bf6dd402443b59e2d11a83ab3a749a

Test failed on:
  * g1-small
  * n1-highcpu-4

Some tests will failed to build on them, e.g.:
  FAIL k8s.io/kubernetes/cmd/hyperkube [build failed]
  FAIL k8s.io/kubernetes/cmd/kube-apiserver/app [build failed]
  FAIL k8s.io/kubernetes/cmd/kubelet/app [build failed]
  FAIL k8s.io/kubernetes/cmd/kube-proxy/app [build failed]
  FAIL k8s.io/kubernetes/cmd/libs/go2idl/client-gen/testoutput/clientset_generated/test_internalclientset [build failed]
  FAIL k8s.io/kubernetes/contrib/mesos/cmd/km [build failed]

Different tests will fail on different instances.

Looks like they all failed with:
  /usr/lib/go-1.6/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

Po-Hsu Lin (cypressyew)
summary: ubuntu_k8s_unit_tests sub tests failed to build with gcc: cannot
- allocate memory
+ allocate memory on X-4.15-GCP
tags: added: 4.15 gcp sru-20220103 ubuntu-k8s-unit-tests xenial
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.