-
Notifications
You must be signed in to change notification settings - Fork 178
Update Circle CI environment #822
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
Conversation
78092df
to
05d88a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The old version of mercurial on the CI machine was having trouble with the redirect from
I've updated the URLs to use |
b9b11e1
to
d4afde9
Compare
d561b54
to
db8bee3
Compare
Ug, still not working. I'll try more tomorrow. |
6b1fc3c
to
6f86790
Compare
6f86790
to
4cfb353
Compare
Lol just stayed a little longer and got it working. There were quite a few things that needed love in the Circle CI config. It's now using a more up to date OS (Debian Stretch), which fixes another issue I ran into with mercurial. It also tests Python 3.6 since we say we support it in the README. |
@bridadan Did you change the name of the checks that are required? |
@theotherjimmy looks like I did change the names of the jobs in Circle CI (to disambiguate Python 3.6 from Python 3.7). I can change the required checks on the repository if you're ok with these changes. (the existing PRs will probably need a rebase) |
This should fix the build error affecting all Python 2 builds in CI.
Edit: I should have included more details about why we have to update setuptools. When running
pip install -r mbed-os/requirements.txt
on the CI machine, I received this error:There is a requirement parsing error with one of the packages. The syntax is valid, but the support was added in a later version of setuptools. The CI machine was running an old version of setuptools (20.10.1 to be exact, the latest release is 40.6.3 as of this writing), so I've added a command to update the package.