Skip to content

Conversation

jchavarri
Copy link
Contributor

@jchavarri jchavarri commented Dec 7, 2019

@jchavarri
Copy link
Contributor Author

@jaredly there seems to be some permissions issue:

tar: could not chdir to '/Users/runner/runners/2.160.1/work/1/cache'

Information, ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session f834923b-097f-4c7d-a958-c0c6379a4371
##[error]Process returned non-zero exit code: 1

I'm not sure what could be causing this, this command is part of the internal Cache saving scripts.

I thought it could be that I'm a contributor and there is some security issues, but in hello-reason I activated Azure cache in a PR like here and everything seemed to work: esy-ocaml/hello-reason#53.

@jordwalke @ulrikstrid have you run into this issue before?

@jordwalke
Copy link

I've never seen that issue before.

@jchavarri
Copy link
Contributor Author

@jordwalke this is embarrasing, it seems I forgot to add - template: utils/publish-build-cache.yml 😅 Trying again now, but the chdir error now makes more sense (the folder did not exist).

@jaredly
Copy link
Owner

jaredly commented Dec 11, 2019

Sounds good to me!

@jchavarri jchavarri deleted the upgrade-ci branch December 11, 2019 10:37
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

Successfully merging this pull request may close these issues.

3 participants