-
Notifications
You must be signed in to change notification settings - Fork 414
Refactor Makefile and run s3/adls/gcs integration tests in CI
#2125
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
Refactor Makefile and run s3/adls/gcs integration tests in CI
#2125
Conversation
|
Resolved for now by adding these errors to |
| docker compose -f dev/docker-compose-integration.yml kill | ||
| docker compose -f dev/docker-compose-integration.yml rm -f | ||
| docker compose -f dev/docker-compose-integration.yml up -d |
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.
refactor: remove these lines and reuse test-integration-setup
| test-s3: # Run tests marked with s3, can add arguments with PYTEST_ARGS="-vv" | ||
| sh ./dev/run-minio.sh | ||
| poetry run pytest tests/ -m s3 ${PYTEST_ARGS} |
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.
refactor: move lower and closer to test-adls and test-gcs
Fokko
left a comment
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 giving the Makefile some much-needed love and attention @kevinjqliu 🙌 I left some extra-nitpicky comments to clean it up a bit more, let me know what you think!
In apache#2125 we got a warning from the google-auth package, and we're on `1.6.3` while `2.40.3` is out there.
In #2125 we got a warning from the google-auth package, and we're on `1.6.3` while `2.40.3` is out there. So maybe good to bump everything 👍 <!-- Thanks for opening a pull request! --> <!-- In the case this PR will resolve an issue, please replace ${GITHUB_ISSUE_ID} below with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> # Rationale for this change # Are these changes tested? # Are there any user-facing changes? <!-- In the case of user-facing changes, please add the changelog label. -->
4ccc9e3 to
cf061a2
Compare
Makefile and run s3/adls/gcs integration tests in CI
:( |
|
|
||
| help: ## Display this help | ||
| @awk 'BEGIN {FS = ":.*##"; printf "\nUsage:\n make \033[36m\033[0m\n"} /^[a-zA-Z_-]+:.*?##/ { printf " \033[36m%-20s\033[0m %s\n", $$1, $$2 } /^##@/ { printf "\n\033[1m%s\033[0m\n", substr($$0, 5) } ' $(MAKEFILE_LIST) | ||
| ifeq ($(COVERAGE),1) |
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.
Love it
|
@kevinjqliu This is the tricky part of the coverage. Looks like we have sufficient coverage for the unit tests, but not for the integration tests :( So maybe only report coverage for the unit-tests? Or we have to do some GitHub Actions wizardry to combine the reports of both the unit-tests and the integration tests. |
|
Made coverage fail percentage customizable.
Also added this comment :) |
Fokko
left a comment
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.
Looks good, love the cleanup 🚀
|
Thanks @kevinjqliu 🙌 |
In apache#2125 we got a warning from the google-auth package, and we're on `1.6.3` while `2.40.3` is out there. So maybe good to bump everything 👍 <!-- Thanks for opening a pull request! --> <!-- In the case this PR will resolve an issue, please replace ${GITHUB_ISSUE_ID} below with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> # Rationale for this change # Are these changes tested? # Are there any user-facing changes? <!-- In the case of user-facing changes, please add the changelog label. -->
<!--
Thanks for opening a pull request!
-->
<!-- In the case this PR will resolve an issue, please replace
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
<!-- Closes #${GITHUB_ISSUE_ID} -->
Closes apache#2124
# Rationale for this change
Refactor `Makefile`
* Grouped commands and added comments
* Added `COVERAGE` param to run test with coverage
* Added `COVERAGE_FAIL_UNDER` param to specify coverage threshold to
pass
* Change test coverage threshold to `85` for unit tests, we are
currently at `87`
* Change test coverage threshold to `75` for integration tests, we are
currently at `77`
CI
* Add s3/adls/gcs integration tests to run in CI
* Run tests with coverage report
Note the `gcsfs` issue was resolved by apache#2127
# Are these changes tested?
Yes
# Are there any user-facing changes?
No
<!-- In the case of user-facing changes, please add the changelog label.
-->
In apache#2125 we got a warning from the google-auth package, and we're on `1.6.3` while `2.40.3` is out there. So maybe good to bump everything 👍 <!-- Thanks for opening a pull request! --> <!-- In the case this PR will resolve an issue, please replace ${GITHUB_ISSUE_ID} below with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> # Rationale for this change # Are these changes tested? # Are there any user-facing changes? <!-- In the case of user-facing changes, please add the changelog label. -->
<!--
Thanks for opening a pull request!
-->
<!-- In the case this PR will resolve an issue, please replace
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
<!-- Closes #${GITHUB_ISSUE_ID} -->
Closes apache#2124
# Rationale for this change
Refactor `Makefile`
* Grouped commands and added comments
* Added `COVERAGE` param to run test with coverage
* Added `COVERAGE_FAIL_UNDER` param to specify coverage threshold to
pass
* Change test coverage threshold to `85` for unit tests, we are
currently at `87`
* Change test coverage threshold to `75` for integration tests, we are
currently at `77`
CI
* Add s3/adls/gcs integration tests to run in CI
* Run tests with coverage report
Note the `gcsfs` issue was resolved by apache#2127
# Are these changes tested?
Yes
# Are there any user-facing changes?
No
<!-- In the case of user-facing changes, please add the changelog label.
-->
Closes #2124
Rationale for this change
Refactor
MakefileCOVERAGEparam to run test with coverageCOVERAGE_FAIL_UNDERparam to specify coverage threshold to pass85for unit tests, we are currently at8775for integration tests, we are currently at77CI
Note the
gcsfsissue was resolved by #2127Are these changes tested?
Yes
Are there any user-facing changes?
No