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

Make truncation threshold (ellipsis) configurable regardless the verbosity level #12111

Closed
ssbarnea opened this issue Mar 12, 2024 · 3 comments
Closed
Labels
stale status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity type: bug problem that needs to be addressed

Comments

@ssbarnea
Copy link
Member

I found multiple similar unanswered question online such stackoverflow.com/questions/38000993/how-can-i-get-my-assertions-in-pytest-to-stop-being-abbreviated-with-ellipsis

We need to make the truncation values configurable regardless of pytest verbosity level, especially as we know that changing general verbosity level has other side effects.

My opinion is that most people would want to run in minimal verbosity level (especially) on CI but have verbose errors for failed tests. If I run in verbose by default displaying the console log in the browser can be problematic, true for github actions and also most CI/CD system I know (none behaves nice with very long console logs).

Related:

@ssbarnea ssbarnea added the type: bug problem that needs to be addressed label Mar 12, 2024
@bluetech
Copy link
Member

@bluetech bluetech added the status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity label Mar 17, 2024
Copy link
Contributor

github-actions bot commented Apr 1, 2024

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Apr 1, 2024
Copy link
Contributor

github-actions bot commented Apr 9, 2024

This issue was closed because it has the status: needs information label and follow-up information has not been provided for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity type: bug problem that needs to be addressed
Projects
None yet
Development

No branches or pull requests

2 participants