| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
Per [0] "There is no statement about the level of testing and upgrades
from Extended Maintenance are not supported within the Community."
In Ocata (currently in EM) and Pike (soon to be) branches, we see Zuul
check failures from time to time on unstable tests, that require a few
rechecks before the backport gets in.
For some issues it is better to fix the test/setup itself when it is
easy (see [1] and [2] for recent examples), but for some failing tests
(testing exotic cases or not directly related to networking), we should
start filtering them out.
An initial example is tempest.api.volume.test_volumes_extend.VolumesExtendTest.test_volume_extend_when_volume_has_snapshot which fails regularly on ocata and often on pike:
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22test_volume_extend_when_volume_has_snapshot%5C%22%20AND%20project:%5C%22openstack%2Fneutron%5C%22%20AND%20build_status:%5C%22FAILURE%5C%22
We can use this bug to track later similar additions
[0] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
[1] https://bugs.launchpad.net/neutron/+bug/1821815 fixes cover jobs
[2] https://review.openstack.org/#/c/648046/ fixes a functional test failure (simple backport)
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1821925
Title:
Limit test coverage for Extended Maintenance stable branches
Status in neutron:
New
Bug description:
Per [0] "There is no statement about the level of testing and upgrades
from Extended Maintenance are not supported within the Community."
In Ocata (currently in EM) and Pike (soon to be) branches, we see Zuul
check failures from time to time on unstable tests, that require a few
rechecks before the backport gets in.
For some issues it is better to fix the test/setup itself when it is
easy (see [1] and [2] for recent examples), but for some failing tests
(testing exotic cases or not directly related to networking), we
should start filtering them out.
An initial example is tempest.api.volume.test_volumes_extend.VolumesExtendTest.test_volume_extend_when_volume_has_snapshot which fails regularly on ocata and often on pike:
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22test_volume_extend_when_volume_has_snapshot%5C%22%20AND%20project:%5C%22openstack%2Fneutron%5C%22%20AND%20build_status:%5C%22FAILURE%5C%22
We can use this bug to track later similar additions
[0] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
[1] https://bugs.launchpad.net/neutron/+bug/1821815 fixes cover jobs
[2] https://review.openstack.org/#/c/648046/ fixes a functional test failure (simple backport)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1821925/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
