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

Update CI to use 0.31.1 #8251

Merged
merged 2 commits into from
Oct 2, 2019
Merged

Update CI to use 0.31.1 #8251

merged 2 commits into from
Oct 2, 2019

Conversation

bcardiff
Copy link
Member

No description provided.

@bcardiff bcardiff added this to the 0.32.0 milestone Sep 30, 2019
@jkthorne
Copy link
Contributor

jkthorne commented Oct 1, 2019

This is changed every release. should this be configured in the CI itself?

@bcardiff
Copy link
Member Author

bcardiff commented Oct 1, 2019

@wontruefree it's a bit of bookkeeping but it also serves as a log of the lineage. If they end up as a configuration in the CI then that information is lost in time and forks will need to be configured also.

@bcardiff bcardiff force-pushed the ci/update branch 4 times, most recently from bbcbc66 to 166d19c Compare October 2, 2019 20:07
@bcardiff
Copy link
Member Author

bcardiff commented Oct 2, 2019

The 32 bits packages are failing more frequently. It will need some further investigation in another PR. For now, the specs will be allowed to fail in order to avoid delaying the whole build. But the dist_linux32 job might also fail from time to time. So there is a bit more pressure to fix the memory issues.

@bcardiff bcardiff merged commit e63f7fd into master Oct 2, 2019
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.

2 participants