-
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
Search for part of job description across other runs #88
Comments
@kamoltat - even before that: I could not find that string (the description) at all when listing a specific run? |
@ronen-fr If you're looking for all job descriptions of a run, it's possible on pulpito-ng by toggling the "description" column. Example, for https://pulpito.netlify.app/runs/teuthology-2024-09-25_21:24:35-fs-squid-distro-default-smithi: Screen.Recording.2024-09-26.at.10.10.10.PM.movIt's also possible on current pulpito: try clicking "Show Description" button on https://pulpito.ceph.com/teuthology-2024-09-25_21:24:35-fs-squid-distro-default-smithi/ |
thanks. I missed that. |
Ah, I wasn't totally dumb. Here is how it looks in deploy-preview-87--pulpito.netlify.app No description field |
@ronen-fr So sorry, it's my bad! That URL is a temporary URL for user-filter feature (it will stop working after PR #87 is merged). It was not rebased to latest main that's why it didn't had description and task fields. I have rebased it now, you should be able to see description in above URL too. The actual pulpito-ng deployment is at https://pulpito-ng.ceph.com/. It doesn't have the global search and username filter yet, I will update you here when it does. Sorry for the confusion! |
Users see a job fail and have to look up different runs to see if the run is failing on other branches (to see if it's a common bug or local to their run). They sometimes have to
grep
last 50-something runs to see if the problem is in other runs.We can probably include a feature to search for string of job description across runs. This change requires paddles to support such a query.
The text was updated successfully, but these errors were encountered: