-
Notifications
You must be signed in to change notification settings - Fork 141
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
Extract doctest from main CI workflow #915
Extract doctest from main CI workflow #915
Conversation
Signed-off-by: Yury-Fridlyand <yuryf@bitquilltech.com>
Signed-off-by: Yury-Fridlyand <yuryf@bitquilltech.com>
Codecov Report
@@ Coverage Diff @@
## 2.x #915 +/- ##
============================================
- Coverage 97.90% 95.10% -2.81%
Complexity 3072 3072
============================================
Files 293 303 +10
Lines 7588 8246 +658
Branches 490 609 +119
============================================
+ Hits 7429 7842 +413
- Misses 158 350 +192
- Partials 1 54 +53
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
build.dependsOn doctest | ||
// Deactivate doctest in the main gradle workflow (./gradlew build), because doctest depends | ||
// on ML plugin and it ruins SQL plugin build if ML plugin is not available (not released) | ||
// build.dependsOn doctest |
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.
if it's for CI only, maybe disable in workflow instead of removing doctest from build task?
But could you explain more on why? If ml-commons is missing and doctest cannot run, we should not merge in PR anyways since we don't know if the PR breaks other doctests
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.
we should not merge in PR anyways
I agree. Unfortunately, gradle
runs doctests before integration tests and before most of the unit tests. This results in a PR with failed SQL Java CI
workflow, which crashed on doctests.
The proposed change unblocks UT and IT from doctest. The PR will remain blocked by a failing CI workflow - SQL Doctest CI
. We will be able to identify that all tests really pass and we are waiting for ML
release to complete the PR.
I do not think we should disable docTest in IT flow and github flow. The purpose of docTest is make sure the code is align with docs. |
+1 for removing ML dependency from doctest. Otherwise, version bump like #898 will always fail and blocked. |
Confirmed. Will do in another PR. |
Description
Doctest depends on ML plugin. If it is unavailable for download for the current version, doctest fails and this ruins all SQL plugin CI.
Issues Resolved
Make SQL plugin CI independent on ML plugin.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.