-
Notifications
You must be signed in to change notification settings - Fork 3k
Enabl-able Python 3 tools testing in Travis CI #6433
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
ca594b3
to
c48ff37
Compare
@cmonr Don't delete the dashes. it kills the check boxes. |
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.
Looks fine to me.
@theotherjimmy Not sure I follow. Which dashes do you mean? Doing a visual diff in Travis of this PR's branch and mbed-os master, they still look the same. |
# | ||
# - <<: *tools-pytest | ||
# env: NAME=tools-py3.6 | ||
# python: 3.6 |
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.
nice!
why not turn it on?
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.
Ignore me, I didn't read your message close enough 👍
Let's keep this pr open until python 3 support works again. Maybe we should create a branch for python3 work?
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.
@geky Hmm, a feature branch might not be that bad of an idea, although I'm not confident it's needed. We actually already have some tools in master that are python3 ready, courtesy of @theotherjimmy.
I'd prefer to not keep PRs open as a progress indicator, mainly because I don't like to see PRs linger :)
@0xc0170 thoughts?
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.
A branch will quickly become out of date with master and then be rebase hell, I think.
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.
Fair enough
It just seems strange to merge something that is entirely commented out
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.
That's fair. The flip side is that devs can enable the functionality to test porting efforts :)
/morph build |
Build : SUCCESSBuild number : 1537 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1178 |
Test : SUCCESSBuild number : 1318 |
@cmonr I was referring to the |
Parking for now. Will update and uncomment py3 sections when support is complete. |
Will be enabled when tool support has been completely ported
c48ff37
to
8b66182
Compare
@theotherjimmy @geky @0xc0170 It's baaack! This is the final piece to the puzzle. mbed-cli currently has two PRs open and should be merged and released within the week (ARMmbed/mbed-cli#668 and ARMmbed/mbed-cli#667). What I suggest: Thoughts? |
@cmonr, @theotherjimmy said add dashes in front of the following 5 lines of Pull request type and then produce
No code changes or testing are required. |
Build : SUCCESSBuild number : 2119 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1743 |
Halting the auto-started export and test builds, and will hold until review had been completed. Build needs to be restarted anyways since the status wasn't captured correctly. |
@li-ho I'm glad you noticed, but the description style has been updated a couple of times since I last had this PR open. The style that is present now is correct and in line with other PRs. |
/morph build |
Build : SUCCESSBuild number : 2140 Triggering tests/morph test |
Test : SUCCESSBuild number : 1933 |
Exporter Build : SUCCESSBuild number : 1765 |
Description
Updates Travis CI such that once mbed-cli 1.7.0 is released, automatic tools testing against Python 3 can be switched on with a single, small PR.
Tested in personal instance of Travis CI. When enabled, Python 3 fails appropriately. An aborted example can be found here: https://travis-ci.org/cmonr/mbed-os/builds/357062171.
Pull request type