From 53ef08276cd64675f872a91bdbd167f6b11c729e Mon Sep 17 00:00:00 2001 From: Eric Fried Date: Thu, 5 Dec 2019 17:03:16 -0600 Subject: [PATCH] Restore test_minbw_allocation_placement in nova-next job This test was accidentally removed via [1] so we restored it via [2], but that fell afoul of the related bug so we re-disabled it via [3]. Once the dependency merges, we should be able to re-restore it. [1] https://review.opendev.org/#/c/683988/ [2] https://review.opendev.org/#/c/697180/ [3] https://review.opendev.org/#/c/697491/ Depends-On: https://review.opendev.org/682964 Change-Id: I9c11f25307b6b3859522775bb8172b901b468d79 Related-Bug: #1854993 --- .zuul.yaml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/.zuul.yaml b/.zuul.yaml index ae5116eb5c..30893abd47 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -176,9 +176,7 @@ # (1) take a long time and (2) are already covered in the # tempest-slow* job. If this regex gets more complicated use # tempest_test_blacklist. - # TODO(mriedem): Unskip test_minbw_allocation_placement once bug 1844568 - # is fixed. - tempest_black_regex: ^tempest.scenario\.(test_network|test_minbw_allocation_placement) + tempest_black_regex: ^tempest.scenario.test_network devstack_local_conf: post-config: $NOVA_CPU_CONF: