-
Notifications
You must be signed in to change notification settings - Fork 190
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 suite fails on Fedora #118
Comments
This adds a first basic test to be run using GitHub Actions on push and pull request for the CMake build (internally we run everything on Bazel/Blaze). The Ubuntu runners are implemented as full VMs, so we can run tests directly. In order to run Sandboxed API/Sandbox2 tests inside a container, it must be started as privileged, unconfined and retain its capabilities. Since GitHub does not support modifying the Docker invocation for container based workflows, we need to manually run the `docker` command. Until #118 is fixed, this change makes GitHub ignore the test failure on Fedora. PiperOrigin-RevId: 428485354 Change-Id: I6b55c5441c4c27b018d19498d2296c7d3da65846
I need to debug this a bit, but a recent run of the Fedora build behaves (AFAICT) the same. So maybe we should revisit the statement that we don't need to parse |
I don’t think parsing those is a good idea if it means the sandboxed process needs access to |
This fixes the main issue (#118) with stack traces on Fedora, which uses a `/lib64` and `/usr/lib64`. PiperOrigin-RevId: 437717858 Change-Id: I6986aa84c2be57ae1d9f8d0cb9b508768d27f1c1
This fixes the main issue (google#118) with stack traces on Fedora, which uses a `/lib64` and `/usr/lib64`. PiperOrigin-RevId: 437717858 Change-Id: I6986aa84c2be57ae1d9f8d0cb9b508768d27f1c1
This adds a first basic test to be run using GitHub Actions on push and pull request for the CMake build (internally we run everything on Bazel/Blaze). The Ubuntu runners are implemented as full VMs, so we can run tests directly. In order to run Sandboxed API/Sandbox2 tests inside a container, it must be started as privileged, unconfined and retain its capabilities. Since GitHub does not support modifying the Docker invocation for container based workflows, we need to manually run the `docker` command. Until #118 is fixed, this change makes GitHub ignore the test failure on Fedora. PiperOrigin-RevId: 428485354 Change-Id: I6b55c5441c4c27b018d19498d2296c7d3da65846
This fixes the main issue (#118) with stack traces on Fedora, which uses a `/lib64` and `/usr/lib64`. PiperOrigin-RevId: 437717858 Change-Id: I6986aa84c2be57ae1d9f8d0cb9b508768d27f1c1
The test suite fails on Fedora. Build script and log output attached.
log.txt
build.txt
The text was updated successfully, but these errors were encountered: