Skip to content
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

Verbose information no longer shared on failed or timeout tasks #3512

Open
sbertramrh opened this issue Feb 6, 2025 · 6 comments
Open

Verbose information no longer shared on failed or timeout tasks #3512

sbertramrh opened this issue Feb 6, 2025 · 6 comments

Comments

@sbertramrh
Copy link

Since TF 0.0.22 was deployed I noticed that when tests fail or timeout, extra information is missing from the test bar.

e.g. when dmesg checks fail but the test passes it would print (check 'dmesg' failed, original test result: pass). now nothing is shared about the test and why it failed in the bar.

similarly when the bar is warning, in this case for a timeout, it used to show (timeout). but now it does not.

@psss
Copy link
Collaborator

psss commented Feb 6, 2025

@janhavlin, I guess that could be related to the way how the note list is converted to oculus? Could you please have a look?

@psss psss added bug Something isn't working priority | must high priority, must be included in the next release labels Feb 6, 2025
@psss psss added this to the 1.43 milestone Feb 6, 2025
@janhavlin
Copy link
Collaborator

Can you share an affected Testing Farm request so I can take a look?

@happz
Copy link
Collaborator

happz commented Feb 11, 2025

@janhavlin
Copy link
Collaborator

Ok, that actually looks like two separate bugs:

  1. Showing skipped/failed checks as passed (TFT-3103).
  2. Missing fix for str -> list[str] change of the note field.

I'll try to fix it.

@janhavlin
Copy link
Collaborator

@happz
Copy link
Collaborator

happz commented Feb 13, 2025

I am removing this issue from the release, as no fix is needed in tmt.

@happz happz removed this from the 1.43 milestone Feb 13, 2025
@happz happz removed bug Something isn't working priority | must high priority, must be included in the next release labels Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants