Skip to content
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

The debian ISO build machine is crashing when running buildroot #9650

Closed
afbjorklund opened this issue Nov 9, 2020 · 4 comments
Closed

The debian ISO build machine is crashing when running buildroot #9650

afbjorklund opened this issue Nov 9, 2020 · 4 comments
Labels
area/build-release area/testing kind/bug Categorizes issue or PR as related to a bug. kind/flake Categorizes issue or PR as related to a flaky test. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Nov 9, 2020

The node is running debian oldstable (stretch), which is still running gcc-multilib 4:6.3.0-4

It seems to have some issues, when trying to bootstrap and cross-compile our buildroot ?

g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
Makefile:152: recipe for target 'cmGeneratorTarget.o' failed

See PR #9628 and PR #9645, both crashed

@afbjorklund afbjorklund added kind/bug Categorizes issue or PR as related to a bug. area/build-release area/testing kind/flake Categorizes issue or PR as related to a flaky test. labels Nov 9, 2020
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Nov 9, 2020

Can we upgrade from Debian 9 to Debian 10, perhaps ?

https://www.debian.org/releases/

Or maybe the machine has other issues like running out of memory ?

Runner name: 'gcp-agent2-debian9'

@afbjorklund afbjorklund added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Nov 9, 2020
@priyawadhwa priyawadhwa added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 25, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 25, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 26, 2021
@sharifelgamal
Copy link
Collaborator

ISO builds now happen on Debian 10. This is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-release area/testing kind/bug Categorizes issue or PR as related to a bug. kind/flake Categorizes issue or PR as related to a flaky test. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

5 participants