Skip to content

Mark output in LogProgress#11753

Open
sheaf wants to merge 1 commit intohaskell:masterfrom
sheaf:mark-logProgress
Open

Mark output in LogProgress#11753
sheaf wants to merge 1 commit intohaskell:masterfrom
sheaf:mark-logProgress

Conversation

@sheaf
Copy link
Copy Markdown
Collaborator

@sheaf sheaf commented Apr 16, 2026

Cabal's Distribution.Utils.LogProgress module failed to take into account whether we were marking output or not, and simply never included output markers. This PR rectifies that.

We also make sure that warnings go to stderr not stdout, to be consistent with Distribution.Simple.Utils.warnMessage.

In summary, the impact is that:

  • warning messages now consistently go to stderr
  • when running the testsuite, we are more consistent in tagging messages emitted by Cabal, with the BEGIN CABAL OUTPUT/END CABAL OUTPUT markers.

TODO:

  • Updated expected testsuite output to account for this change.

Template B: This PR does not modify behaviour or interface. It only modifies output marking, which is an internal mechanism for the testsuite.

@sheaf sheaf force-pushed the mark-logProgress branch from 649a899 to 1af3dfb Compare April 16, 2026 19:26
Cabal's Distribution.Utils.LogProgress module failed to take into
account whether we are marking output or not, and simply never included
output markers.

We also make sure that warnings go to stderr not stdout, to be
consistent with `Distribution.Simple.Utils.warnMessage`.

In summary, the impact is that:

  - warning messages now consistently go to stderr
  - when running the testsuite, we are more consistent in tagging
    messages emitted by Cabal, with the 'BEGIN CABAL OUTPUT'/'END CABAL OUTPUT'
    markers.
@sheaf sheaf force-pushed the mark-logProgress branch from 1af3dfb to d54a5eb Compare April 16, 2026 20:07
@sheaf sheaf marked this pull request as ready for review April 17, 2026 17:23
@sheaf
Copy link
Copy Markdown
Collaborator Author

sheaf commented Apr 17, 2026

CI is passing, just a spurious network blip in one of the jobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants