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

add ripgrep to travis ci cache directories list #5373

Merged
merged 1 commit into from
Jun 6, 2019

Conversation

tom-shan
Copy link
Contributor

@tom-shan tom-shan commented Jun 6, 2019

CI often fails for github api rate limit when downloading
ripgrep package. This workaroud is trying to enable
Travis CI cache of ripgrep package.

@kittaakos
Copy link
Contributor

Hopefully, this PR fixes #3787.

Copy link
Member

@akosyakov akosyakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine with me, let's try

probably PRs from forks cannot contribute to a cache, but if they can use cached data then it should help

.travis.yml Outdated
@@ -66,6 +66,7 @@ cache:
# end_cache_directories
- packages/java-debug/download
- packages/debug-nodejs/download
- /tmp/vscode-ripgrep-cache-1.2.4
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only concern that we should keep it sync with rigrep version, maybe we can improve scripts/prepare-travis

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will have a try

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@tom-shan tom-shan force-pushed the ripgrep-cache branch 2 times, most recently from ddf2744 to 323aabb Compare June 6, 2019 12:43
CI often fails for the github api rate limit when downloading ripgrep
package. This workaroud is trying to enable Travis CI cache of the
ripgrep package and lower the failure rate.

Signed-off-by: tom-shan <swt0008411@163.com>
@marcdumais-work
Copy link
Contributor

Assuming this works as intended, would there be a way to re-use this strategy when building the docker images in theia-apps?

@akosyakov
Copy link
Member

@marcdumais-work yes, merging, if it helps then we can try with theia-apps

@akosyakov akosyakov merged commit 393aa6a into eclipse-theia:master Jun 6, 2019
@tom-shan
Copy link
Contributor Author

I notice that a couple of recent CI results are still failed. During these builds, there are some weird logs about Travis cache, for example https://travis-ci.org/theia-ide/theia/jobs/547289068#L248 and https://travis-ci.org/theia-ide/theia/jobs/547291207#L248.

@marcdumais-work
Copy link
Contributor

@tom-shan thanks for pointing this out.

Do we know if caching ripgrep, as done in this PR, has been observed to work for PRs originating from a non-committer's fork?

I'll clear the current Travis cache for our project, in case it might help.

@tom-shan
Copy link
Contributor Author

tom-shan commented Jun 20, 2019

Yes, you can refer to https://docs.travis-ci.com/user/caching/#pull-request-builds-and-caches

I'm not sure whether clearing cache really help. But it should be pointed out that after the master cache is cleared, you'd better recreate it as soon as possible, or the new PR is going to download the ripgrep from github and may fail the CI.

@marcdumais-work
Copy link
Contributor

it should be pointed out that after the master cache is cleared, you'd better recreate it as soon as possible

+1. Not practically a problem however; the cache was recreated minutes after I cleared it - @akosyakov had a PR being tested that repopulated the cache.

Yes, you can refer to https://docs.travis-ci.com/user/caching/#pull-request-builds-and-caches

Thanks - that does not prove that the mechanism works as we intended - so far I have not seen a Travis run that succeeds for a non-committer.

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.

4 participants