-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test all ARM64 scenarios when possible #10
Labels
blocked
This issue or pull request is awaiting the outcome of another issue or pull request
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
Comments
jsf9k
added
blocked
This issue or pull request is awaiting the outcome of another issue or pull request
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
labels
Jun 18, 2024
jsf9k
added a commit
that referenced
this issue
Jun 18, 2024
TODO: Starting with systemd version 253 or 254 (I'm not sure which) it is no longer possible to start systemd-resolved.service under QEMU emulation. We support this case, but we cannot test it until we have native ARM64 runners. See issue #10 for more details.
jsf9k
added a commit
that referenced
this issue
Jun 18, 2024
TODO: Starting with systemd version 253 or 254 (I'm not sure which) it is no longer possible to start systemd-resolved.service under QEMU emulation. We support this case, but we cannot test it until we have native ARM64 runners. See issue #10 for more details.
jsf9k
added a commit
that referenced
this issue
Nov 26, 2024
Starting with systemd version 253 or 254 (I'm not sure which) it is no longer possible to start systemd-resolved.service under QEMU emulation. We support this case, but we cannot test it until we have native ARM64 runners. See issue #10 for more details.
jsf9k
added a commit
that referenced
this issue
Nov 27, 2024
Starting with systemd version 253 or 254 (I'm not sure which) it is no longer possible to start systemd-resolved.service under QEMU emulation. We support this case, but we cannot test it until we have native ARM64 runners. See issue #10 for more details.
jsf9k
added a commit
that referenced
this issue
Jan 24, 2025
In many cases we no longer need to do this because we are now using native ARM64 GitHub Actions runners. Resolves #10.
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
blocked
This issue or pull request is awaiting the outcome of another issue or pull request
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
💡 Summary
We should start testing all ARM64 scenarios once we have native ARM64 runners.
Motivation and context
Starting with
systemd
version 253 or 254 (I'm not sure which) it is no longer possible to startsystemd-resolved.service
under QEMU emulation. We support this case, but we cannot test it until we have native ARM64 runners.The text was updated successfully, but these errors were encountered: