-
Notifications
You must be signed in to change notification settings - Fork 314
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 Makefile target to run all CI checks #1299
Conversation
And reorganize the docs to mention integration tests and this new target.
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.
Many thanks for the quick turnaround in raising this PR!
Generally this looks good, I left a few comments mostly about requiring that a PR, prior to submission, passes all tests locally.
.github/PULL_REQUEST_TEMPLATE.md
Outdated
@@ -8,6 +8,6 @@ attention. | |||
|
|||
* Have you signed the [contributor license agreement](https://www.elastic.co/contributor-agreement)? | |||
* Have you followed the [contributor guidelines](https://github.com/elastic/rally/blob/master/CONTRIBUTING.md)? | |||
* Have you run `make test` and `make it` and both finish without errors? | |||
* Have you run `make lint`, `make test` and `make it` and they finish without errors? |
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.
Regarding your PR comment we want to ensure all tests pass before raising a community PR is raised so I suggest we replace this with Have you run `make check-all` successfully?
This reduces time spent in the PR review process.
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.
Thanks, done.
CONTRIBUTING.md
Outdated
|
||
Consider using editor integrations to do it automatically: you'll need to configure [black](https://black.readthedocs.io/en/stable/integrations/editors.html) and [isort](https://github.com/PyCQA/isort/wiki/isort-Plugins). | ||
Run the test suite to make sure that nothing is broken: `make test`. You can also run integration tests with `make it` (they're much slower, though). To run everything including lint, use `make check-all`. |
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.
I suggest we change the order here and require that make check-all
passes first -- since these are the guidelines before raising a PR -- and then explain that to iterate faster make test
and make it
can also be used. In other words something like:
Ensure that all tests pass by running
make check-all
. This runs sequentially lint checks, unit tests and integration tests. These can be executed in isolation usingmake lint
,make test
andmake it
respectively, in case you need to iterate over a subset of tests.Note: Integration tests are much slower than unit tests.
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.
Thanks, done.
@elasticmachine test this please |
@elasticmachine test this please |
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.
Thanks for iterating. LGTM, will merge after CI is green.
CI is green :) |
@pquentin Ah sorry, yes this fell through the cracks. Merging. |
And reorganize the docs to mention integration tests and this new target.
I also noticed an opportunity to update the pull request template. I think I prefer not mentioning
make check-all
there because I still haven't managed to run the integration tests locally!Closes #1297