Skip to content

MAINT, CI: disable Shippable cache #16620

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

Merged
merged 1 commit into from
Jun 16, 2020

Conversation

tylerjereddy
Copy link
Contributor

Fixes #16611

  • a quick look at the NumPy CI failures on Shippable
    service clearly shows the full test suite passing
    and a negative exit code only because of the failed
    cache restore

  • since the jobs are running in about 20 minutes
    even without the use of a cache, just try turning
    if off

* a quick look at the NumPy CI failures on Shippable
service clearly shows the full test suite passing
and a negative exit code only because of the failed
cache restore

* since the jobs are running in about 20 minutes
even without the use of a cache, just try turning
if off
@seberg
Copy link
Member

seberg commented Jun 16, 2020

Ok, too bad about the cache, but I suspect the run itself is quite a bit slower than the setup to begin with. So lets try it. Thanks @tylerjereddy and @anirudh2290.

@seberg seberg merged commit 1fb7047 into numpy:master Jun 16, 2020
@tylerjereddy
Copy link
Contributor Author

Looks like our Shippable queue is pretty substantial--I don't see a currently active job. I can try to purge out the queue later, but not sure that would help much. Perhaps it was getting hammered and the load balance reduced NumPy priority for a while or something, not sure.

@sturlamolden
Copy link
Contributor

sturlamolden commented Jun 17, 2020

Shippable had two successful Ci runs, and is now failling on cache restore again

@sturlamolden
Copy link
Contributor

Looks like the problem has returned.

@tylerjereddy
Copy link
Contributor Author

I don't think it has returned--the only failures I see have restore_cache stages, which means they aren't using the updated shippable.yml, which causes that stage to disappear completely.

@tylerjereddy tylerjereddy deleted the shippable_disable_cache branch June 17, 2020 01:34
@charris charris added the 09 - Backport-Candidate PRs tagged should be backported label Jun 20, 2020
@charris charris added this to the 1.19.1 release milestone Jun 20, 2020
@charris charris removed the 09 - Backport-Candidate PRs tagged should be backported label Jun 20, 2020
@charris charris removed this from the 1.19.1 release milestone Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Shippable always fails
5 participants