Skip to content
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

Closed
krlmlr opened this issue Sep 8, 2015 · 4 comments
Closed

Noisy output due to dump of log files #37

krlmlr opened this issue Sep 8, 2015 · 4 comments

Comments

@krlmlr
Copy link
Owner

krlmlr commented Sep 8, 2015

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

@krlmlr
Copy link
Owner Author

krlmlr commented Sep 8, 2015

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.

@HenrikBengtsson
Copy link
Contributor

FYI, and related to http://help.appveyor.com/discussions/suggestions/828-store-some-artifacts-in-case-of-failure, I've ended up using:

on_failure:
  - 7z a failure.zip *.Rcheck\*
  - appveyor PushArtifact failure.zip

See also example log and artifacts.

@krlmlr
Copy link
Owner Author

krlmlr commented Oct 4, 2015

Thanks, Henrik, this looks like a very useful workaround!

@krlmlr
Copy link
Owner Author

krlmlr commented Feb 15, 2016

This is fixed in the devtools template now.

@krlmlr krlmlr closed this as completed Feb 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants