Wednesday, 2023-02-08

gmannelodilles: +1 on your patch. I have proposed the generic template change which can be merged once we have stable/2023.1 https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873051 01:53
*** yadnesh|away is now known as yadnesh04:02
opendevreviewGhanshyam proposed openstack/tempest master: Separate the extra tests to run in a separate job  https://review.opendev.org/c/openstack/tempest/+/87305505:29
opendevreviewGhanshyam proposed openstack/tempest master: Separate the extra tests to run in a separate job  https://review.opendev.org/c/openstack/tempest/+/87305505:41
*** jpena|off is now known as jpena08:29
elodillesgmann: thanks \o/ looks good! Note that we need to wait until *every* project has branched with stable/2023.108:50
opendevreviewyatin proposed openstack/devstack stable/train: [Train Only] Run ensure-rust role  https://review.opendev.org/c/openstack/devstack/+/87290210:28
opendevreviewyatin proposed openstack/grenade stable/train: [train-only] Add ensure-rust to grenade jobs  https://review.opendev.org/c/openstack/grenade/+/87299910:28
*** yadnesh is now known as yadnesh|away13:24
*** Roamer`_ is now known as Roamer`14:00
*** tosky_ is now known as tosky14:19
gmannelodilles: yeah15:55
gmannkopecmartin: can you check this too (ensure-rust in grenade jobs) https://review.opendev.org/c/openstack/grenade/+/87296915:55
opendevreviewGhanshyam proposed openstack/tempest master: Separate the extra tests to run in a separate job  https://review.opendev.org/c/openstack/tempest/+/87305516:53
gmanndansmith: kopecmartin: ^^ on splitting the  tests in job. let me know what you think. and in tempest-extra-tests-list.txt we can add other tests also in future if we think is kind of redundant and not needed to run as part of common full job16:55
dansmithgmann: yeah, it is unfortunate that we have to make things more parallel to avoid the timeout, just because of how much resource is consumed by a single tempest patch (which expands to the other projects, but less so) although it seems like that's probably a good initial step17:17
dansmithdoesn't tempest have its own timeout timer?17:17
dansmithif so, maybe we could up the regular job timeout to 3h and run multiple batches of tempest in a single job, with their own shorter timers?17:17
gmanndansmith: yes we can up the job timeout for regular one. I was thinking the same in our earlier discussion too. let me push that on top of it17:22
gmanni feel full-parallel is also passing at good rate https://zuul.openstack.org/builds?job_name=tempest-full-parallel&skip=017:22
gmannthat can be another option to try - run scenario tests in parallel17:23
dansmithgmann: to be clear, I'm not saying we should just up the job timeout in isolation,17:26
dansmithI'm saying _if_ we could run two sets of tempest tests, each with their own short timer, then we could let the job timer for the whole thing be longer17:27
dansmithi.e. "you have 1h to complete the non-admin tempest tests".. "pass, okay now you have 1h to complete the admin tests".. total job timeout=3h17:27
gmanndansmith: ohk. I misunderstood then. so breaking tests timeout in single job is not possible in tempest side. its 'single test timeout' and 'complete job timeout' 17:29
dansmithokay17:30
dansmithpresumably we could do that by just running `timeout 1h tox -e ...` in the job or `timeout 1h stestr ...` in tox.ini17:32
*** jpena is now known as jpena|off17:32
gmannbut what additional it will help if we need to up the overall job time17:38
gmannto know which set of tests  is running long and timeout ?17:38
dansmithno, it means we will still fail quickly if a test gets stuck, but will allow longer runtime if we're truly making progress17:41
dansmithI guess if tempest already has a per-test timeout, then it's the same as just upping the job timer17:41
dansmithI hadn't thought of that until you mentioned it17:42
dansmithsplitting tests into separate jobs uses a lot more resource total (setup of two devstacks and two nodes while running)17:42
dansmithso just thinking if it's really better to do that vs. increasing the job timeout17:42
dansmithwhat is the per-test timer set to? 10m or something?17:43
gmann20 min by default17:44
dansmithwow, okay17:45
opendevreviewGhanshyam proposed openstack/tempest master: Move tempest-full-py3-ipv6 job to periodic  https://review.opendev.org/c/openstack/tempest/+/87316317:47
dansmithgmann: finally got a clean run of this glance retry thing: https://review.opendev.org/c/openstack/tempest/+/87298219:37
gmanndansmith: ack19:42
dansmithtrying to make an opensearch query to quantify how often we hit that19:43
dansmithat least 5 yesterday, but it manifests a few different ways19:43
opendevreviewCyril Roelandt proposed openstack/devstack master: Glance: Properly copy rootwrap.d/* when USE_VENV is True  https://review.opendev.org/c/openstack/devstack/+/86695120:34
opendevreviewGhanshyam proposed openstack/tempest master: Move a few jobs to periodic  https://review.opendev.org/c/openstack/tempest/+/87316320:59
gmanndansmith: kopecmartin ^^ this is moving some jobs to periodic pipeline, i think they do not need to run on every change. this can help to save some resource21:01
dansmithgmann: ++21:06
opendevreviewGhanshyam proposed openstack/tempest master: Fix creation of requested creds within the same project  https://review.opendev.org/c/openstack/tempest/+/87101823:02
opendevreviewGhanshyam proposed openstack/tempest master: DNM: for test  https://review.opendev.org/c/openstack/tempest/+/87101923:03
opendevreviewGhanshyam proposed openstack/tempest master: Use project_reader in server test  https://review.opendev.org/c/openstack/tempest/+/87121023:04

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!