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

[BUG]: <title>ubuntu-latest in workflow will update to ubuntu-24.04 #833

Open
dmacattack opened this issue Jan 8, 2025 · 0 comments · May be fixed by #834
Open

[BUG]: <title>ubuntu-latest in workflow will update to ubuntu-24.04 #833

dmacattack opened this issue Jan 8, 2025 · 0 comments · May be fixed by #834
Labels

Comments

@dmacattack
Copy link

dmacattack commented Jan 8, 2025

vSomeip Version

v3.4.10

Boost Version

1.74

Environment

Github workflow (Ubuntu 24.04)

Describe the bug

This is related to #688

The workflow used has the runner set as ubuntu-latest. The last run automatically used ubuntu 22.04, but will slowly upgrade to ubuntu 24.04 in this rollout: actions/runner-images#10636

We have observed similar failures while building vsome ip in eclipse-uprotocol on our workflow. We have downgraded to ubuntu 22.04 as a temporary fix.

@dmacattack dmacattack added the bug label Jan 8, 2025
Setland34 added a commit to Setland34/vsomeip that referenced this issue Jan 12, 2025
Fixes COVESA#833

Update workflow and documentation to address build issues on Ubuntu 24.04.

* **README.md**
  - Add a note to use Ubuntu 22.04 as a temporary fix for build issues on Ubuntu 24.04.
  - Mention the issue related to the GitHub Actions runner update.

* **.github/workflows/c-cpp.yml**
  - Change `runs-on` from `ubuntu-latest` to `ubuntu-22.04` for the job `build_on_ubuntu_boost_183_gcc_x86`.

* **Dockerfile**
  - Update base image from `ubuntu:jammy` to `ubuntu:22.04`.

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/COVESA/vsomeip/issues/833?shareId=XXXX-XXXX-XXXX-XXXX).
@Setland34 Setland34 linked a pull request Jan 12, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant