-
Notifications
You must be signed in to change notification settings - Fork 8
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
Details of test failures are sometimes too short #144
Comments
It has always been this way, we keep the first 3 lines as there is a hard limit in the size of the comments on GitHub, which can become very restrictive when you have a lot of failures. I could try to keep more lines and see how it goes. FYI, you have the full stacktrace in the annotations at the bottom of https://github.com/quarkusio/quarkus/runs/19900097523#user-content-test-failure-io.quarkus.reactive.oracle.client.noconfigtest-1 (here I'm not hit by the limit). |
If you know what the limit is in GitHub, we could come up with some smart-ish way of determining how many lines we keep. I.e. we first build some template:
Then we compute the number of chars/line in that template, and depending on that and the limit we determine how many chars/lines we can keep in each details section, and we replace the placeholders with the truncated details. |
Yeah I have some logic with various options and some degraded options if the comment is too long. I went with 8 lines, we will see if we end up having no stacktraces in too many cases. |
There's something wrong with the "details" of test failures generated by the build reporter: sometimes it's (much) shorter than it ought to, skipping all meaningful information
See for example quarkusio/quarkus#37906 (comment) . We get this:
Even though the error message is much more detailed in the logs:
Originally posted by @yrodiere in quarkusio/quarkus#37906 (comment)
The text was updated successfully, but these errors were encountered: