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

appveyor build exits with code 5 #29

Closed
nhejazi opened this issue Jul 1, 2017 · 5 comments
Closed

appveyor build exits with code 5 #29

nhejazi opened this issue Jul 1, 2017 · 5 comments
Assignees
Labels

Comments

@nhejazi
Copy link
Owner

nhejazi commented Jul 1, 2017

Using the latest version of a GitHub package that isn't owned by my account causes a failure -- in particular, it appears that I am restricted to the CRAN version of Karthik's wesanderson color palette.

See the build log on Appveyor -- specifically, v1.0.101 -- for details. Package installation fails with exit code 5. It's unclear what this means or why this is happening, given that the Travis-CI build is successful.

@nhejazi
Copy link
Owner Author

nhejazi commented Jul 1, 2017

It appears that this rather cryptic error has been encountered on Appveyor before -- see this issue.

@nhejazi nhejazi self-assigned this Jul 1, 2017
@nhejazi nhejazi added the bug label Jul 1, 2017
@nhejazi
Copy link
Owner Author

nhejazi commented Jul 1, 2017

Needed to add a GITHUB_PAT environment variable with public_repo permissions. Should have been fixed by 134d401, but a new error emerges...

@nhejazi nhejazi closed this as completed Jul 1, 2017
@nhejazi
Copy link
Owner Author

nhejazi commented Jul 1, 2017

possibly related error: Error in readRDS(dest) : error reading from connection stemming again from the attempt to install the wesanderson package via install_github on Appveyor.

@nhejazi nhejazi reopened this Jul 1, 2017
@nhejazi
Copy link
Owner Author

nhejazi commented Jul 4, 2017

The Appveyor encryption UI provides a convenient utility for protecting environment variables necessary for build processes (like the GITHUB_PAT required in this case).

@nhejazi
Copy link
Owner Author

nhejazi commented Aug 10, 2017

This is no longer a problem as of da26e25. It was caused by using palettes in the wesanderson package that had been renamed between the CRAN (v.0.3.2) release and the GitHub master (v.0.3.4) release.

@nhejazi nhejazi closed this as completed Aug 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant