-
Notifications
You must be signed in to change notification settings - Fork 541
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
CI: Revert recent "show build commands on terminal" change #2000
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for posting this PR!
I have pushed a commit to finish reversal of e5a66fc: When reverting a commit, we should be reverting that commit as a whole, not undoing some of that commit changes while keeping others (even if we like some of the changes in the being-reverted commit). Some of the leftovers (removed in my commit 620f4bf) were plain wrong. Some may be a good idea but should be submitted in a dedicated PR (where they may be expanded or polished as needed, in that new context).
I adjusted PR title to become more meaningful in isolation (e.g., in a list of commit titles and/or in another branch). I adjusted PR description to state the facts without an unnecessary (and incomplete) list of those who observed those facts. I also left a bit more breadcrumbs in case we decide to revisit this topic in future PRs.
If you are OK with these adjustments, please clear this PR for merging.
Time spent so far: 7 hours and 8 minutes
What's worse, we're back to square one, fundamental disagreement about |
GitHub Actions UI does not handle large amounts of console output with collapsable `::group::` sections well. For example, UI may truncate console output if a collapsable `::group::` section gets too many log lines. In some cases, GitHub does not report truncation at all, resulting in misleading console output. In other, UI warns: "This step has been truncated due to its large size. Download the full logs from the menu once the workflow run has completed." This change reverts recent commit e5a66fc.
GitHub Actions UI does not handle large amounts of console output with collapsable `::group::` sections well. For example, UI may truncate console output if a collapsable `::group::` section gets too many log lines. In some cases, GitHub does not report truncation at all, resulting in misleading console output. In other, UI warns: "This step has been truncated due to its large size. Download the full logs from the menu once the workflow run has completed." This change reverts recent commit e5a66fc.
…he#2000) GitHub Actions UI does not handle large amounts of console output with collapsable `::group::` sections well. For example, UI may truncate console output if a collapsable `::group::` section gets too many log lines. In some cases, GitHub does not report truncation at all, resulting in misleading console output. In other, UI warns: "This step has been truncated due to its large size. Download the full logs from the menu once the workflow run has completed." This change reverts recent commit e5a66fc.
GitHub Actions UI does not handle large amounts of console output with
collapsable
::group::
sections well.For example, UI may truncate console output if a collapsable
::group::
section gets too many log lines. In some cases, GitHub does not report
truncation at all, resulting in misleading console output. In other, UI
warns: "This step has been truncated due to its large size. Download the
full logs from the menu once the workflow run has completed."
This change reverts recent commit e5a66fc.