Skip to content

Add support for logging to a file #8686

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.

Sign up for GitHub

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

Jump to bottom
Closed
munificent opened this issue Feb 21, 2013 · 2 comments
Closed

Add support for logging to a file #8686

munificent opened this issue Feb 21, 2013 · 2 comments
Assignees
@munificent
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug

Comments

@munificent
Copy link
Member

Pub has detailed logging now, but its options for outputting the logs are limited. For the pub tests, we often want to specifically capture both stdout and stderr and it's tricky if the logs are in either of those.

It would be ideal if pub could be directed to log to a separate file (or pipe?). Then the pub tests could capture that separately and keep stdout/stderr clean.
@munificent
Copy link
Member Author

The OS already supports piping, so we've decided to just rely on that. The pub tests separate out stdout and stderr.

Added NotPlanned label.

@munificent munificent added Type-Enhancement closed-not-planned Closed as we don't intend to take action on the reported issue labels Jul 25, 2013
@munificent munificent self-assigned this Jul 25, 2013
@munificent munificent added this to the Later milestone Jul 25, 2013
@DartBot DartBot mentioned this issue Jun 3, 2015
Closed
@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#458.

@DartBot DartBot mentioned this issue Jun 5, 2015
Closed
@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed type-enhancement labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@munificent munificent

Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kevmoo @munificent @DartBot