Skip to content
This repository has been archived by the owner on May 21, 2019. It is now read-only.

build.cmd should create a log file #86

Closed
mikeharder opened this issue Jun 9, 2016 · 4 comments
Closed

build.cmd should create a log file #86

mikeharder opened this issue Jun 9, 2016 · 4 comments

Comments

@mikeharder
Copy link
Contributor

I think build.cmd should create a log file, including things like detailed test results (including the time to execute each test). Would be nice to keep the 10 most recent logs (build.log, build.1.log ... build.9.log), but even a single log of the most recent build would be nice.

This came up when I ran build.cmd, and Kestrel unit tests took 120 seconds rather than the usual 6 seconds, but I cannot repro and I don't know what caused it (e.g. was it a single slow test or all tests). A build log showing unit test timing would have been helpful.

@muratg
Copy link

muratg commented Jul 26, 2016

cc @pranavkm @anurse

@muratg
Copy link

muratg commented Jul 27, 2016

@anurse Were you planning to add something like this in korebuild2?

@natemcmaster
Copy link
Contributor

#159 started producing a file log to artifacts/msbuild/msbuild.log. Good enough?

@mikeharder
Copy link
Contributor Author

LGTM

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants