You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See also #481. I find myself often removing useful Transcript sends from test code because the job log in GitHub Actions gets hard-to-read and long-to-scroll otherwise. Ideally, one could show/hide the Transcript sends for each test execution individually (provided that nestled folding is possible).
The text was updated successfully, but these errors were encountered:
The problem is that you'd need to listen for output which can be tricky, adding empty groups by default simply pollutes the logs. I think in the past, we came to the conclusion that users must use Transcript sends responsibly.
Maybe not in Squeak and for your tests... smalltalkCI needs to provide compatibility across all supported images and what if some project caches the Transcript instance or relies on it somehow?
See also #481. I find myself often removing useful Transcript sends from test code because the job log in GitHub Actions gets hard-to-read and long-to-scroll otherwise. Ideally, one could show/hide the Transcript sends for each test execution individually (provided that nestled folding is possible).
The text was updated successfully, but these errors were encountered: