-
Notifications
You must be signed in to change notification settings - Fork 60
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
Noisy output due to dump of log files #37
Comments
I think this is better handled by AppVeyor, for now we can search the output for "dump", that's where the clutter begins -- the reason for failure should be shown just before that. |
FYI, and related to http://help.appveyor.com/discussions/suggestions/828-store-some-artifacts-in-case-of-failure, I've ended up using:
|
Thanks, Henrik, this looks like a very useful workaround! |
This is fixed in the devtools template now. |
Artifacts are not normally archived with failed builds. Perhaps artifacts can be pushed manually: http://www.appveyor.com/docs/packaging-artifacts. This would avoid the necessity to dump logs.
CC @hadley
Example: https://ci.appveyor.com/project/hadley/devtools/build/1.0.10#L360
The text was updated successfully, but these errors were encountered: