-
Notifications
You must be signed in to change notification settings - Fork 4
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
Post analysis URL in logs #28
Comments
Sorry, this is an RFE, wrong type /o\ |
We have an EPIC going on including this issue to make thamos output more readable: thoth-station/thamos#1118 However, we could work on a temporary solution to make the output less verbose in the meantime |
/sig user-experience |
Note that the link to the analysis should already be shown... only that it is buried inside that "wall of text" (search for the text "Results can be browsed in Thoth search"). Unfortunately the link provided there is (still) broken. thoth-station/support#219 is fixed but apparently not release in prod, will take a look at that. Besides that, as Maya mentioned, I hope thoth-station/thamos#1118 can help here. |
This is now solved and the fix is part of the current release of adviser, 0.56.1. It should make it into production as part of thoth-station/thoth-application#2598
This is also available now in thamos 1.27.9:
With that, I believe this can be consider this request as done and it. If you feel something is missing please do not hesitate to reopen or open a new one as appropriate. |
@codificat: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Bug description
Once the analysis is done, it would be nice to review it on your web frontend. Could the pre-commit hook put a link in logs?
Actual behavior
Expected behavior
Well, my expected behaviour would be only a few lines of output with errors and a link to the analysis:
I am getting a wall of text right now which is hard to inspect. I believe that's where the frontend would be really helpful.
The text was updated successfully, but these errors were encountered: