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.

Sign up for GitHub

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

Jump to bottom

multiarch build of che-machine-exec is not stable #19062

Open
sleshchenko opened this issue Feb 12, 2021 · 3 comments
Open

multiarch build of che-machine-exec is not stable #19062

sleshchenko opened this issue Feb 12, 2021 · 3 comments
Labels
area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 area/machine-exec kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.

Comments

@sleshchenko
Copy link
Member

Describe the bug

multiarch build of che-machine-exec is not stable https://github.com/eclipse/che-machine-exec/actions
as result PR checks fails without a clear reason for that + the latest changes may be not propagated to the container registry.
@sleshchenko sleshchenko added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. area/machine-exec labels Feb 12, 2021
@sleshchenko
Copy link
Member Author

Dashboard has similar issues with multiarch build #19049

@sleshchenko
Copy link
Member Author

multiarch PR checks are fixed in eclipse-che/che-machine-exec#133

@tolusha tolusha mentioned this issue Apr 6, 2021
Closed
@nickboldt nickboldt added the area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 label Apr 28, 2021
@che-bot
Copy link
Contributor

che-bot commented Nov 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2021
@tolusha tolusha added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 area/machine-exec kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nickboldt @tolusha @sleshchenko @che-bot