[goal][python3] week R-7 update
Slawomir Kaplonski
skaplons at redhat.com
Tue Feb 19 21:21:11 UTC 2019
> Wiadomość napisana przez Doug Hellmann <doug at doughellmann.com> w dniu 19.02.2019, o godz. 22:17:
>
> Slawomir Kaplonski <skaplons at redhat.com> writes:
>
>> Hi,
>>
>> Sure. I send my email to You and to the list because I used "reply to
>> all” :)
>
> Oops, I completely missed the CC entry. Sorry about that!
No problem :)
>
>>
>>> Wiadomość napisana przez Doug Hellmann <doug at doughellmann.com> w dniu 19.02.2019, o godz. 22:06:
>>>
>>>
>>> Those are good questions. I see that you replied to me privately, would
>>> you mind if I reply back to the list with the answers?
>>>
>>> Slawomir Kaplonski <skaplons at redhat.com> writes:
>>>
>>>> Hi,
>>>>
>>>> I’m from Neutron team. Can You explain maybe what exactly means „2/17” in „tox defaults” column and what is „1” failing job?
>>>> Thx in advance for any info :)
>
> Each column shows the number of open and total patches for that
> category. So 2/17 means that the team has 2 remaining out of the 17
> total patches to deal with.
>
> At this point, those patches may need to be approved (including fixes
> before that can happen), or they might be duplicates if someone else did
> the same work using a different patch.
>
> The failing job count shows the number of patches where zuul is
> reporting a job failure, out of all of the open patches in the row. In
> neutron's case, that means 1 of the 2 patches with tox changes is
> failing some job.
>
> Looking at the list of python3-first patches for all neutron team
> repositories, I see:
>
> $ .tox/venv/bin/python3-first patches list neutron
> +-----------------------------------------------+-----------------------------+---------+----------+-------------------------------------+-------------+-----------------+
> | Subject | Repo | Tests | Workflow | URL | Branch | Owner |
> +-----------------------------------------------+-----------------------------+---------+----------+-------------------------------------+-------------+-----------------+
> | fix tox python3 overrides | openstack/networking-bgpvpn | FAILED | REVIEWED | https://review.openstack.org/606671 | master | Doug Hellmann |
> | Cleanup Zuul project definition | openstack/networking-odl | FAILED | NEW | https://review.openstack.org/598086 | master | Michel Peterson |
> | Work around test failures on pike | openstack/networking-sfc | PASS | REVIEWED | https://review.openstack.org/608170 | stable/pike | Andreas Jaeger |
> | fix tox python3 overrides | openstack/neutron-fwaas | UNKNOWN | NEW | https://review.openstack.org/586271 | master | Vieri |
> | Switch functional and tempest jobs to python3 | openstack/ovsdbapp | UNKNOWN | NEW | https://review.openstack.org/637988 | master | Nate Johnston |
> +-----------------------------------------------+-----------------------------+---------+----------+-------------------------------------+-------------+-----------------+
>
> The two tox patches are in networking-bgpvpn and neutron-fwaas.
Thx. Now I understand that :) I was thinking about neutron as „neutron only” and I forgot about stadium projects. That’s because I couldn’t figure out what it might means exactly.
I will try to look at those patches this week and will try to help when I can.
>
>>>>
>>>>> Wiadomość napisana przez Doug Hellmann <doug at doughellmann.com> w dniu 19.02.2019, o godz. 21:57:
>>>>>
>>>>>
>>>>> This is the regular update for the "Run under Python 3 by default" goal
>>>>> (https://governance.openstack.org/tc/goals/stein/python3-first.html).
>>>>>
>>>>> == Current Status ==
>>>>>
>>>>> After last week's several teams updated their status in the wiki, and at
>>>>> least one team changed the job they had running so that it is
>>>>> voting. The list of teams who have not completed this step is still
>>>>> longer than I would like, but everyone is either working on it or has
>>>>> put it on their roadmap.
>>>>>
>>>>> == Ongoing and Completed Work ==
>>>>>
>>>>> We also have a fair number of tox update patches left open. I intend to
>>>>> abandon any of those that I submitted when we hit RC1 for Stein, because
>>>>> I plan to be working on other things next cycle. If you see your project
>>>>> name below and want to get your version of the patch landed before that
>>>>> deadline, look for the patch with topic tag 'python3-first'.
>>>>>
>>>>> +-------------------+--------------+---------+----------+---------+------------+-------+---------------+
>>>>> | Team | tox defaults | Docs | 3.6 unit | Failing | Unreviewed | Total | Champion |
>>>>> +-------------------+--------------+---------+----------+---------+------------+-------+---------------+
>>>>> | adjutant | 1/ 1 | - | + | 0 | 0 | 2 | Doug Hellmann |
>>>>> | barbican | + | 1/ 3 | + | 1 | 1 | 7 | Doug Hellmann |
>>>>> | heat | 1/ 8 | + | + | 0 | 0 | 21 | Doug Hellmann |
>>>>> | InteropWG | 1/ 2 | + | + | 0 | 0 | 8 | Doug Hellmann |
>>>>> | ironic | 1/ 10 | + | + | 0 | 0 | 35 | Doug Hellmann |
>>>>> | magnum | 1/ 5 | + | + | 0 | 0 | 10 | |
>>>>> | masakari | 1/ 4 | + | - | 0 | 0 | 5 | Nguyen Hai |
>>>>> | neutron | 2/ 17 | + | + | 1 | 1 | 44 | Doug Hellmann |
>>>>> | OpenStack Charms | 7/ 73 | - | - | 7 | 2 | 73 | Doug Hellmann |
>>>>> | Quality Assurance | 1/ 9 | + | + | 0 | 1 | 30 | Doug Hellmann |
>>>>> | rally | 1/ 3 | + | - | 1 | 1 | 5 | Nguyen Hai |
>>>>> | swift | 2/ 3 | + | + | 2 | 1 | 6 | Nguyen Hai |
>>>>> | tacker | 1/ 4 | + | + | 1 | 0 | 9 | Nguyen Hai |
>>>>> | Telemetry | 1/ 7 | + | + | 0 | 1 | 19 | Doug Hellmann |
>>>>> | tripleo | 1/ 53 | + | + | 0 | 1 | 89 | Doug Hellmann |
>>>>> | trove | 1/ 5 | + | + | 0 | 0 | 11 | Doug Hellmann |
>>>>> | User Committee | 3/ 3 | + | - | 0 | 2 | 5 | Doug Hellmann |
>>>>> | | 45/ 61 | 56/ 57 | 55/ 55 | 13 | 11 | 1068 | |
>>>>> +-------------------+--------------+---------+----------+---------+------------+-------+---------------+
>>>>>
>>>>> == Next Steps ==
>>>>>
>>>>>
>>>>> == How can you help? ==
>>>>>
>>>>> 1. Choose a patch that has failing tests and help fix
>>>>> it. https://review.openstack.org/#/q/topic:python3-first+status:open+(+label:Verified-1+OR+label:Verified-2+)
>>>>>
>>>>> 2. Review the patches for the zuul changes. Keep in mind that some of
>>>>> those patches will be on the stable branches for projects.
>>>>>
>>>>> 3. Work on adding functional test jobs that run under Python 3.
>>>>>
>>>>> == How can you ask for help? ==
>>>>>
>>>>> If you have any questions, please post them here to the openstack-dev
>>>>> list with the topic tag [python3] in the subject line. Posting questions
>>>>> to the mailing list will give the widest audience the chance to see the
>>>>> answers.
>>>>>
>>>>> We are using the #openstack-dev IRC channel for discussion as well, but
>>>>> I'm not sure how good our timezone coverage is so it's probably better
>>>>> to use the mailing list.
>>>>>
>>>>> == Reference Material ==
>>>>>
>>>>> Goal description: https://governance.openstack.org/tc/goals/stein/python3-first.html
>>>>> Open patches needing reviews: https://review.openstack.org/#/q/topic:python3-first+is:open
>>>>> Storyboard: https://storyboard.openstack.org/#!/board/104
>>>>> Zuul migration notes: https://etherpad.openstack.org/p/python3-first
>>>>> Zuul migration tracking: https://storyboard.openstack.org/#!/story/2002586
>>>>> Python 3 Wiki page: https://wiki.openstack.org/wiki/Python3
>>>>>
>>>>> --
>>>>> Doug
>>>>>
>>>>
>>>> —
>>>> Slawek Kaplonski
>>>> Senior software engineer
>>>> Red Hat
>>>>
>>>
>>> --
>>> Doug
>>
>> —
>> Slawek Kaplonski
>> Senior software engineer
>> Red Hat
>>
>
> --
> Doug
—
Slawek Kaplonski
Senior software engineer
Red Hat
More information about the openstack-discuss
mailing list