-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Task does not fail if report generation fails #909
Comments
It seems that there is no way to detect the failure in this gradle-plugin side; HTML bug reporter ignores thrown exception. I'll try to monitor its stderr output and make the task fail if |
Signed-off-by: Kengo TODA <skypencil@gmail.com>
Hm, but the exception is preserved in some field. |
The fix for this issue #929 is not published yet. Did you confirm it with a built Gradle plugin from that branch? |
This is true. I recently little bit tired to maintain the SpotBugs core, hope that someone will send a PR to fix these kinds of problems... |
No |
* test: reproduce the reported issue as #909 Signed-off-by: Kengo TODA <skypencil@gmail.com> * test: fix test case Signed-off-by: Kengo TODA <skypencil@gmail.com> * fix: Task does not fail if report generation fails Signed-off-by: Kengo TODA <skypencil@gmail.com> * chore: format code by spotless Signed-off-by: Kengo TODA <skypencil@gmail.com> * chore: resolve problems reported by SonarQube Signed-off-by: Kengo TODA <skypencil@gmail.com> --------- Signed-off-by: Kengo TODA <skypencil@gmail.com>
🎉 This issue has been resolved in version 5.1.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
If there is an error during report generation, for example if you configure the HTML report and give it a syntactically incorrect XSL, you get the error from the XSLT engine printed, but the task finishes successfully. The task should fail instead if anything goes wrong during report generation. Especially as on next execution the task will simply be up-to-date or taken from task output cache, where the task output cache will contain a stale report from last time the generation was successful.
The text was updated successfully, but these errors were encountered: