-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update Docker tests #166
base: master
Are you sure you want to change the base?
Update Docker tests #166
Conversation
Test in pion/ci-sandbox#89 |
8eebdeb
to
a2f2d93
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems that the changes in this PR is not actually tested in pion/ci-sandbox#89
(Reusable workflow in the master branch is used and arch
input is ignored)
Oh sorry. They are now tested. However, I am still not completely confident that this is a good change due to its performance implications. Emulating the ARM builds and test execution can be rather slow, and likely break/timeout test cases.. I am also looking into using Vagrant for testing other OSes like BSDs.. |
@stv0g I think it's better to test it on some large repos, which take long CI time, to check CI performance impact |
I've reworked how we run tests. With this PR I propose to use the same workflow for running all our tests (excluding WASM) via Docker.
This allows us to easily also test Pion on non-x86 platforms via QEmu Userspace Emulation.
Currently, we are emulating both the test compilation and execution. I am tempted to put in some more effort to do actual cross-compilation and use QEmu only for the test execution.
However, this is a bit tricky as we need to compile & execute a dedicated test executable for each package.
Which is a bit of an issue as we also need to gather coverage information alongside..