From 80ffd07dfd71d5bef7a5bda97830aae50d23f305 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Wed, 19 Feb 2025 08:47:50 -0800 Subject: [PATCH] ci: restrict multinode job to multinode tests We'll likely want to revert this one, but overall the multinode job has been failing quite a bit because it is trying to run *all* of the secenario jobs. While, that is not a big deal under normal conditions, at end of development cycle, CI loads are much higher and the failure rate can also be much higher as a result. So for now, dial back the test to the most beneficial/needful test which could be executed on the node. Change-Id: Id4d050e1abd67f431026a2d813f97ffacf24407e --- zuul.d/ironic-jobs.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zuul.d/ironic-jobs.yaml b/zuul.d/ironic-jobs.yaml index f98b72ab40..43a6dfaa5b 100644 --- a/zuul.d/ironic-jobs.yaml +++ b/zuul.d/ironic-jobs.yaml @@ -687,7 +687,7 @@ vars: tox_envlist: all tempest_concurrency: 3 - tempest_test_regex: "ironic_tempest_plugin.tests.scenario" + tempest_test_regex: "BaremetalMultitenancy" tempest_test_timeout: 2400 devstack_localrc: BUILD_TIMEOUT: 2400