[openstack-dev] [neutron] Call for help with in-tree tempest scenario test failures
ihrachys at redhat.com
Thu Aug 3 21:40:48 UTC 2017
Thanks for those who stepped in (Armando and Slawek).
We still have quite some failures that would benefit from initial log
triage and fixes. If you feel like in this feature freeze time you
have less things to do, helping with those scenario failures would be
a good way to contribute to the project.
On Fri, Jul 28, 2017 at 6:02 AM, Sławek Kapłoński <slawek at kaplonski.pl> wrote:
> I will try to check QoS tests in this job.
> Best regards
> Slawek Kaplonski
> slawek at kaplonski.pl
>> Wiadomość napisana przez Jakub Libosvar <jlibosva at redhat.com> w dniu 28.07.2017, o godz. 14:49:
>> Hi all,
>> as sending out a call for help with our precious jobs was very
>> successful last time and we swept all Python 3 functional from Neutron
>> pretty fast (kudos the the team!), here comes a new round of failures.
>> This time I'm asking for your help <imagine Uncle Sam "We want you"
>> poster here> with gate-tempest-dsvm-neutron-dvr-multinode-scenario
>> non-voting job. This job has been part of check queue for a while and is
>> very very unstable. Such job covers scenarios like router dvr/ha/legacy
>> migrations, qos, trunk and dvr. I went through current failures and
>> created an etherpad  with categorized failures and logstash queries
>> that give you latest failures with given particular tests.
>> If you feel like doing troubleshooting and sending fixes for gates,
>> please pick one test and write down your name to the test.
>> Thanks to all who are willing to participate.
>> Have a great weekend.
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev