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.

Sign up for GitHub

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

Jump to bottom

Use container builds #4586

Closed
wants to merge 2 commits into from
Closed

Use container builds #4586

wants to merge 2 commits into from

Conversation

pradyunsg
Copy link
Member

https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments says that repositories enabled before 2015 use the slower and bulkier full VM build, instead of the container based one.

This PR is an experiment to see if switching has any benefits; even minor one.

@pradyunsg pradyunsg added C: automation Automated checks, CI etc type: maintenance Related to Development and Maintenance Processes skip news Does not need a NEWS file entry (eg: trivial changes) labels Jun 30, 2017
@pradyunsg pradyunsg self-assigned this Jun 30, 2017
@pradyunsg pradyunsg force-pushed the ci/container-builds-2 branch from 5941762 to 3a166f7 Compare June 30, 2017 18:21
@pradyunsg
Copy link
Member Author

pradyunsg commented Jun 30, 2017 •
edited
Loading

The builds speed up a lot - upto 50% faster! 🎉 {py27}

@pradyunsg
Copy link
Member Author

pradyunsg commented Jun 30, 2017 •
edited
Loading

Ohkie... pypy doesn't seem to like something... I'll re-run the job - to confirm repeatability of the failure.

@pradyunsg
Copy link
Member Author

PyPy build is behaving weird... I'll push a useless commit.

@pradyunsg pradyunsg removed the skip news Does not need a NEWS file entry (eg: trivial changes) label Jun 30, 2017
@pradyunsg pradyunsg mentioned this pull request Jun 30, 2017
Closed
12 tasks
@pradyunsg
Copy link
Member Author

Okay... Just had an 8 minute test run on CI. This. Is. Awesome!

pypy build - please don't fail. 🤞

@pradyunsg
Copy link
Member Author

Clearly, there's something that PyPy does not like about running the tests in containers... I'll look into it soon.

@pradyunsg
Copy link
Member Author

Might be useful: pytest-test-groups

@pradyunsg
Copy link
Member Author

pradyunsg commented Jun 30, 2017 •
edited
Loading

https://pastebin.com/HAXaqBtT has the build output of the failing peppy build - pastebin for additional backup.

@pradyunsg
Copy link
Member Author

No idea why.

@pfmoore @dstufft Any idea why the PyPy build is failing with some very weird I/O issues? :/

@ghost
Copy link

ghost commented Jul 1, 2017 •
edited by ghost
Loading

No idea but I would not spend time on it as the pypy version on travis is old.

@pradyunsg
Copy link
Member Author

Closing in favour of #4587, basically.

@pradyunsg pradyunsg closed this Jul 1, 2017
@pradyunsg pradyunsg deleted the ci/container-builds-2 branch July 1, 2017 06:47
@pradyunsg pradyunsg mentioned this pull request Jul 1, 2017
Merged
@pradyunsg pradyunsg removed their assignment Oct 5, 2017
@lock
Copy link

lock bot commented Jun 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation C: automation Automated checks, CI etc type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pradyunsg