-
Notifications
You must be signed in to change notification settings - Fork 123
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
Add docker compose based test environment for Linux #733
Conversation
This makes it trivial to inspect, line by line, what got covered. That is useful when evaluating coverage for a new feature. Signed-off-by: Martí Bolívar <[email protected]>
7d226d4
to
8776599
Compare
@marc-hb any objections to this PR? I found it very useful to run these extensive tests locally without the need for a lot of manuals setups. |
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.
It doesn't change the source code or packages.
Short of using a separate repository (admittedly a bit overkill but see why in #687 (comment)), please make sure Docker stuff stays contained in a separate sub directory.
9b63579
to
72b695d
Compare
@marc-hb reduced to mostly reusable files and yaml sections |
Our release process documentation recommends getting passing tox results on as many popular linux distributions as time allows. Doing this by hand is cumbersome, redundant, and error prone. Add a directory with a helper script that automates the entire process using docker compose and document its use in MAINTAINERS.rst. Signed-off-by: Martí Bolívar <[email protected]> Signed-off-by: Pieter De Gendt <[email protected]>
72b695d
to
89e9dc8
Compare
Updated #687 as it appeared to be stale, but still useful.