Monday, 2023-07-24

opendevreviewGhanshyam Mann proposed openstack/tempest master: Optimize the resource creation and status waiting in scenario tests  https://review.opendev.org/c/openstack/tempest/+/88920701:22
opendevreviewMaxim Sava proposed openstack/tempest master: Add image task client and image tests task APIs.  https://review.opendev.org/c/openstack/tempest/+/88875507:26
opendevreviewMerged openstack/tempest master: Split up ServerActionsTestJSON for better mixing  https://review.opendev.org/c/openstack/tempest/+/88910910:56
dansmithkopecmartin: if you're willing, there are several more patches in that series which reduce our wall clock time by making resource allocation more overlap-friendly: https://review.opendev.org/q/topic:split-sat13:51
dansmithkopecmartin: analysis here: https://review.opendev.org/c/openstack/tempest/+/88920016:18
*** jgwentworth is now known as melwitt16:18
dansmithkopecmartin: I really want to get the next patch in the series landed, so please let me know ASAP if I should reorder these so we can get that underway16:19
kopecmartindansmith: thanks, i'm ok with the changes, it makes total sense to wait for multiple states at the same time, i just noticed that the time of the test wasn't shorter and i wasn't sure if the shorter exec time was the primary goal ... i see it wasn't, we can merge it as is because it is a good idea16:22
dansmithkopecmartin: exec time *is* the primary goal, it just varies a *ton* by the speed of the worker16:22
dansmithif you compare other volume-based tests in the two jobs you see they're all way slower in the one run16:23
dansmithwaiting for two things at once will be more efficient in all cases, you just can't compare absolute numbers to each other since workers vary so much in perofrmance16:23
dansmithin the latest recheck, that modified test is 4% of overall execution time, vs. 8% in the unmodified case you quoted16:24
dansmitheven though the unmodified one was on a very fast worker and it took less overall time to run the test as a result, it was still slower in adjusted time16:25
kopecmartinyou're right16:26
kopecmartini oversimplified it .. all makes sense now16:26
dansmithkopecmartin: so this is the juicy one: https://review.opendev.org/c/openstack/tempest/+/889202/116:29
dansmiththe test was creating an extra server.. one to not use and then another with volume-backed16:29
dansmiththat's *obviously* better to avoid :)16:29
dansmithgmann: I noticed you rechecked a docs timeout recently17:29
dansmithI saw this just now: python tools/generate-tempest-plugins-list.py taking like 30 minutes17:29
dansmithperhaps that's fetching things from remote and getting stuck?17:29
gmanndansmith: oh is it, 30 min is too long for that script. I need to check if it search in non OpenStack namespace too ?17:33
dansmithidk, I haven't looked at what it's doing, just saw that it's the offender for my most recent docs timeout17:33
gmannok, I will check17:34
gmannall those timeout things in various places and fixes stopping me to think on doc job timeout. sorry about not checking it17:35
gmannyeah, it is more than just openstack/ namespace search I will suggest 4 years of that release can be good amount (1.5 years in Maintained phase + 2.5 years in Unmaintained phase).17:36
gmannThis way we will keep (counting from the time of latest 2023.1 release):17:36
gmannMaintained:17:36
gmannmaster17:36
gmannstable/2023.1 (< 6 months of release)17:36
gmannstable/zed (6 months of release)17:36
gmannstable/yoga (12 months of release)17:36
gmannUnmaintained:17:36
gmannunmaintained/xena (1.5 years of release)17:36
gmannunmaintained/wallaby (2 years of release)17:36
gmannunmaintained/victoria (2.5 years of release)17:36
gmannunmaintained/ussuri (3 years of release)17:36
gmannunmaintained/train (3.5 years of release)17:36
gmannunmaintained/stein (4 years of release)17:36
gmannunmaintained/rocky -> EOL ( > 4 years of release)17:36
gmannor we can make it 5 if that timeline seems good.17:36
gmannohh, my bad17:36
gmannthis is what I wanted to paste https://github.com/openstack/tempest/blob/master/tools/generate-tempest-plugins-list.py#L129-L14517:36
dansmithgmann: maybe we just need to log something from there to see if we're getting stuck on one or they're just so slow that we're taking too long?17:40
dansmithseems like some of our workers are hiiiightly io constrained these days, like some take double the time of others to run the same job17:40
dansmithso maybe this is just a very slow worker?17:41
gmannmaybe, as i have not see it much but let me do logs and check locally also17:42
gmanndansmith: total 1348 projects are searched in <2 min locally17:49
gmannmay be some other issue on worker/node17:49
dansmithyeah17:50
dansmithkopecmartin pointed out one of these test optimization runs where it was 100% slower on one worker than another he found17:51
dansmithand I looked at several tests in each and the difference was staggering17:51
opendevreviewGhanshyam Mann proposed openstack/tempest master: Add logs in generate-tempest-plugins-list.py  https://review.opendev.org/c/openstack/tempest/+/88933318:07
dansmith++18:07
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Enable LM back and forth flag for SRIOV  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/88933818:39
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Enable LM back and forth flag for SRIOV  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/88933818:42
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Enable LM back and forth flag for SRIOV  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/88933818:43
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Enable LM back and forth flag for SRIOV  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/88933818:44
JayFI'm trying to get a devstack setup based on an Ironic CI job, and it's repeatedly failing starting etcd: https://gist.github.com/jayofdoom/b7020b52d8c69d719627d3d27d4231cc20:04
JayFThis is a freshly installed jammy VM with 16GB of ram and a couple of vcpus20:04
JayFConfiguration is https://zuul.opendev.org/t/openstack/build/cde0eec7274b46f69788d62f08856f1e/logs controller/logs/_.localrc_auto.txt tossed into localrc with ERROR_ON_CLONE=true removed20:05
JayFaha, I think I need to nuke SERVICE_HOST too20:15
opendevreviewAshley Rodriguez proposed openstack/devstack-plugin-ceph master: Remote Ceph with cephadm  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/87674720:37
dansmithgmann: sorry meant to mention https://54345f3748db63fac266-f6d343514834eb14212ec1823288b4de.ssl.cf5.rackcdn.com/889196/2/check/tempest-slow-py3/298c784/testr_results.html in here21:12
* dansmith is juggling too many places at the moment21:12
gmanndansmith: let's wait for ykarel response once he is online as it is failing in serial run also and if he does not have any quick finding then we can skip it21:13
gmannykarel: you remember we talked in neutron channel about test_port_security_macspoofing_port test failing failing in parallel run but it is failing in same frequency in serial run also21:14
opendevreviewGoutham Pacha Ravi proposed openstack/devstack-plugin-ceph master: Remote Ceph with cephadm  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/87674721:51

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