)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"492deab95f9b84cbc612f398afb2cfe0e43f289b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bc6d8e10_d9859ad2","updated":"2024-06-19 17:33:04.000000000","message":"+30 min makes job very long and so does the overall gate. is timeout happening on tempest-full-py3 also? or it is just hitting the slow node more on tempest-integrated-compute job ?","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"d8ec41bc90875a9637d5612daffbf03fc463b34d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bf62992d_7d43af4b","updated":"2024-06-17 15:49:24.000000000","message":"I have observed a high frequency of TIMED_OUT job failures in tempest-integrated-compute and jobs that inherit from it where there were no test failures but the job timeout fired during running of the --serial scenario tests. I agree that this job either needs a bit more time to finish at the current concurrency.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"a634de267f55ab0770490aa21357ddbab8b0d94f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a047a6a6_4d50a654","updated":"2024-06-21 11:15:53.000000000","message":"an infra issue is going to cause this to fail so im oging to rebase to pull it form the queue","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d5f836fce90f36d0f7cd0aae4e9e626deee3ae56","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d59d08a4_ec621a72","updated":"2024-06-21 11:17:34.000000000","message":"i guess since i cant rebase i might as well do it via fixing the typeos in the commit message","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"507620d3d3dc4d7147b68b7b39cdffeadf9e51a3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b1529be1_72295ce0","updated":"2024-06-19 17:04:43.000000000","message":"it\u0027s just 30 more minutes for the one job, +w","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"1933b1a0dee950d4bd3f3f076ffce2bbb15159c4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fc44324e_3494f7da","updated":"2024-06-19 17:04:09.000000000","message":"lgtm, thanks for the investigation like this, it\u0027s very much needed and appreciated","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"edfdfb1e2c56a5329602e4ea4e0e9c645cd53edb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c62d35cc_1af05a5f","updated":"2024-06-21 10:38:31.000000000","message":"recheck ? it looks when gmann did this it didnt trigger or zuul did not report back?\n\ni wonder if there was a zuul restart","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"1be14f4a9dc91154d565b2f7d9296b57a89ee2f0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e90e6645_10bc22a0","updated":"2024-06-20 08:40:28.000000000","message":"recheck kernel bug","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"313dbab98f75cb0279dbee8781b1e2ae185ccc86","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3a955279_7bea9ea6","updated":"2024-06-21 00:54:19.000000000","message":"recheck other jobs are timeout which is not related to integrated-compute job change","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"db10dcf93dd77cf7afe562a4f68761b88f98b208","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"09d0ab9e_e1bb3067","updated":"2024-06-19 22:53:35.000000000","message":"recheck post fialure","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"9598c463d3b8559ae68f924e894e294a1808a579","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f0d236cc_6e2fa5fc","updated":"2024-06-20 00:26:23.000000000","message":"this is going to fail with a BUG: kernel NULL pointer dereference, address: 0000000000000000 error in a volume test. that loooks like a new kernel bug in the cirros 0.6.2 image","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"1fa039396351c2823a454b8ca65be5ad2dcb0ba7","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"536df095_96940248","in_reply_to":"29fd65ed_2940dfe6","updated":"2024-06-20 21:08:24.000000000","message":"I am also not sure if import workflow enabling will make a difference but Dan can help on this.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"3f07dff18ce53c90fb495ef1efd4274bea1fd285","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"52bf6265_f0b57721","in_reply_to":"2c8ef483_d336904a","updated":"2024-06-20 19:05:58.000000000","message":"I know it does not increase the job execution time but open the window for the same when there are any reason tests cannot finish on time. My point was why it is happening in tempest-integrated-compute only and not in tempest-full-py3 when later is superset of the former one.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"16ac3d2f7f1f514c9ee3bff2e371dc8ba9f82af1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"29fd65ed_2940dfe6","in_reply_to":"3b2674df_50f328c1","updated":"2024-06-20 20:22:45.000000000","message":"Right, I think it makes sense you\u0027re targeting tempest-integrated-compute. I agree that tempest-integrated-compute and the jobs derived from it time out far more than other jobs.\n\nI was responding to gmann\u0027s question about why tempest-integrated-compute is slower than tempest-full-py3. I noticed tempest-full-py3 configures devstack to use the Glance import workflow while tempest-integrated-compute does not. So I wondered if the Glance import workflow could impact the performance/speed of the job significantly and if so, should we consider configuring tempest-integrated-compute to use it as well. I don\u0027t know if we intentionally didn\u0027t want to use Glance import in tempest-integrated-compute.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"90a9a3dbf086169aed278ea8966c96e22cc8791a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"69797b9b_af380202","in_reply_to":"4034fc7d_3c252ae0","updated":"2024-06-20 23:55:34.000000000","message":"I tried making charts on OpenSearch, haven\u0027t figured out how to do time ranges yet but I did a couple of simpler charts.\n\ntempest-integrated-compute does run far more times (372) than tempest-full-py3 (153) in a given week (it takes awhile to load these FYI):\n\nhttps://tinyurl.com/bde4mkzx\n\nAnd the TIMED_OUT rate of tempest-integrated-compute vs tempest-full-py3 is 10.48% vs 3.25% for the last week:\n\nhttps://tinyurl.com/bdfedvwj","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"a29095ba6dfbf4938ce5a72ba094254d8a815dc3","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3b2674df_50f328c1","in_reply_to":"43634d8c_a3d3702a","updated":"2024-06-20 20:12:19.000000000","message":"we do not run tempest-full-py3 on nova, only jobs that are derived form it which is why i was targeting tempest-integrated-compute since it and its derived jobs were teh one that were failing.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"0dbcf15a0d891a5d159b1f220b76478914cb1e61","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"43634d8c_a3d3702a","in_reply_to":"52bf6265_f0b57721","updated":"2024-06-20 19:51:29.000000000","message":"Looking at the two jobs definitions, the only difference I notice is tempest-full-py3 runs with `GLANCE_USE_IMPORT_WORKFLOW: True` whereas tempest-integrated-compute does not. Could something like that make that big of a difference?\n\ntempest-full-py3:\nhttps://opendev.org/openstack/tempest/src/commit/3619d297d57c719d2f297f16e8867b5b4f7abf20/zuul.d/integrated-gate.yaml#L57\ntempest-integrated-compute:\nhttps://opendev.org/openstack/tempest/src/commit/3619d297d57c719d2f297f16e8867b5b4f7abf20/zuul.d/integrated-gate.yaml#L130","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"7eb0b2a3bf1c99b0db6e65c7ee41420d1c523e0a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"646253ad_407bd877","in_reply_to":"536df095_96940248","updated":"2024-06-20 21:55:56.000000000","message":"in theory i think the import workflow would be slower not faster.\nit really depend on what plugins are enbled.\nit should be more or less the same if no plugins are enabeld.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"6b355f2a157e1890e1a31eb512d11c1691ed61c2","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4034fc7d_3c252ae0","in_reply_to":"646253ad_407bd877","updated":"2024-06-20 22:31:43.000000000","message":"OK, so your point is the difference is whether or not a given job is running in the Nova gate. I think that could make sense ... if tempest-integrated-compute is running, that means all the other Nova jobs are running, which is a large number of jobs and tests, which creates more pressure on resources. And perhaps when tempest-full-py3 runs, it may happen to be during times when fewer jobs and tests are running at the same time. I\u0027m currently trying to figure out how to look at that on OpenSearch, so far not having success 😛","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"313dbab98f75cb0279dbee8781b1e2ae185ccc86","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d3eed487_15105343","in_reply_to":"69797b9b_af380202","updated":"2024-06-21 00:54:19.000000000","message":"Thanks melwitt for the charts, those are nice data.\n\nAnother thing I remembered and which might be making difference of higher Timeout that we do not run comoute.admin tests in tempest-full-py3 job (those are run in separate job). I split those due to timeout and oom reason. maybe that can be one thing in future to consider in tempest-integrated-compute?\n\nbut I am convinced now on the increased timeout and let\u0027s see how Sean another proposal (922168) make this job better. Thanks melwitt and Sean for explanation.\n\n- https://github.com/openstack/tempest/blob/3619d297d57c719d2f297f16e8867b5b4f7abf20/tox.ini#L135\n- https://github.com/openstack/tempest/blob/3619d297d57c719d2f297f16e8867b5b4f7abf20/tools/tempest-extra-tests-list.txt#L14","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"0bf4bb20f1f6e61633713a9f7b48a05181182daa","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2c8ef483_d336904a","in_reply_to":"bc6d8e10_d9859ad2","updated":"2024-06-20 11:10:12.000000000","message":"making the time outs longer does not increase the job execution tiem\nit just account for the 1% of slow nodes avoiding many many rechecks.\n\nnova has been mostly blocked for a few weeks now.\ni have been trying to land ci fixes for almost a month and timouts in this jobs\nhas been preventing it.\n\nif we don\u0027t address this soon (by next week) ill be proposing makign it non voting to unblock us.\n\nhttps://review.opendev.org/c/openstack/tempest/+/922168/1 the follow up is my attepmt to speed up the jobs and my analisy of the execution times\n\nthis patch is intended to stop the bleeding not as the final fix.","commit_id":"376057dedfeccbd746e499ce1449494dd01210fa"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"4a1c9755cf9b83431950a6ad51a16bcf4cfdcf9d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"82ebb072_6fae3891","updated":"2024-06-21 23:57:12.000000000","message":"Huh, weird I\u0027ve never seen openstack-tox-cover fail for insufficient coverage before:\n```\n-------------------------------------------------------------------------------------------------------------------------\nTOTAL                                                                         15845   3681   3603    416    73%\nCoverage failure: total of 73 is less than fail-under\u003d76\ncover: 81382 C exit 2 (3.73 seconds) /home/zuul/src/opendev.org/openstack/tempest\u003e coverage report -m --fail-under\u003d76 pid\u003d4775 [tox/execute/api.py:286]\n.pkg: 81384 D delete package /home/zuul/src/opendev.org/openstack/tempest/.tox/.tmp/package/2/tempest-39.0.1.dev8-0.editable-py3-none-any.whl [tox/tox_env/python/virtual_env/package/pyproject.py:224]\n  cover: FAIL code 2 (80.53\u003dsetup[4.06]+cmd[0.16,0.11,56.09,0.84,10.74,4.81,3.73] seconds)\n  evaluation failed :( (81.15 seconds)\n  ```","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6c3dd5b9face82a526a5bb04ac7fa3ce21dfe486","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b5cee9dc_cb528a49","updated":"2024-06-21 16:26:43.000000000","message":"re-approving","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"1d15aff0709686895977d7b08ad490e400d5fb54","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6fb7fe03_a6d120c0","updated":"2024-06-21 21:36:49.000000000","message":"recheck [    0.000000] ---[ end Kernel panic - not syncing: IO-APIC + timer doesn\u0027t work!  Boot with apic\u003ddebug and send a report.  Then try booting with the \u0027noapic\u0027 option. ]---","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"93f6688dfc00e07f72756846baa39ab9a183b20f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"428924e8_4626bc9f","updated":"2024-06-21 18:54:02.000000000","message":"recheck [    0.004000] ---[ end Kernel panic - not syncing: IO-APIC + timer doesn\u0027t work!  Boot with apic\u003ddebug and send a report.  Then try booting with the \u0027noapic\u0027 option. ]---","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"d29ef251a86d119e17aabc164e5885c68da60ef4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"51d761af_3374b2ef","updated":"2024-06-25 13:13:00.000000000","message":"recheck post failure in openstack-tox-py38","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"4c7dac8fd3afb47280f45783207a0bae65dd24c8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"47e6d61f_ff3be77a","updated":"2024-06-24 06:41:14.000000000","message":"recheck ssh timeout during test_resize_volume_backed_server_confirm in tempest-full-enforce-scope-new-defaults job","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"e79640e7a2d86a2fd18507dc71c717aa3c4a6c96","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"432ad46d_df597e83","updated":"2024-06-23 22:17:02.000000000","message":"recheck suspiciously low unit tests coverage (73% instead of 76% that\u0027s required) without introducing new code","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"e0a5c8073caecf8f4ab59f125420316137d8b009","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"84f6a396_43459a0d","updated":"2024-06-25 06:13:57.000000000","message":"recheck tempest-full-py3 timed out (let\u0027s try this one more time while we\u0027re waiting for the devstack patch to get through - https://review.opendev.org/c/openstack/devstack/+/922630 )","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"71e7b57d01893ff4c9557d3680b7de3857e48011","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"289b177a_d2c6b476","updated":"2024-06-24 12:59:30.000000000","message":"sigh ok we need to apply this to tempest-full too..\njust to get it to pass the tempest gate.\n\nbefore i respine this should i do this one step higher on the commn parrent \n\ndevstack-tempest","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"cb452350282b31befddb051442f72aad867e0e76","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"939ae3d8_7969db0f","in_reply_to":"6c8277fe_c6b0d31c","updated":"2024-06-24 11:06:37.000000000","message":"i meant to link to where we define that here\n\nhttps://opendev.org/openstack/tempest/src/branch/master/zuul.d/base.yaml#L17","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"29217f4ecd9cfa017af953942e3759316cc57f5b","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8aba10d9_6fd3e00e","in_reply_to":"6fb7fe03_a6d120c0","updated":"2024-06-24 10:50:21.000000000","message":"by the way this kernel bug was ment to be fixed by moving to cirros 0.6.x form 0.5.2\n\nit was caused by a kernel bug in the ubuntu kernel in 0.5.2 that was fixed but cirros was not rebuilt to pick it up 0.5.3 and 0.6.x should not hit this.\n\nif it does it means we still have an old kernel and need to look at updating the cirros images futher or to replace them with something else.","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"e79640e7a2d86a2fd18507dc71c717aa3c4a6c96","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"071313f5_6817749e","in_reply_to":"82ebb072_6fae3891","updated":"2024-06-23 22:17:02.000000000","message":"yeah, a while back, we set 76% unit test coverage as the bare minimum (it was the current coverage at that time) to influence writing unit tests for any new code (excluding tests of course) ... however, 73% is quite low, i wonder what could affect the calculation as this patch doesn\u0027t introduce any new code .. plus, locally, it gives me 76% .. let\u0027s recheck","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"1dbc8d44e7600a61e069b220a5246c7972c7d5c0","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6c8277fe_c6b0d31c","in_reply_to":"8aba10d9_6fd3e00e","updated":"2024-06-24 10:57:45.000000000","message":"we should be using 0.6.2 https://github.com/openstack/devstack/blob/b425e822f62ac2230c90551644da2368bd77b2a8/stackrc#L660C1-L660C42\nwe are usign 0.6.1 for the alt image\nhttps://c9f898dfe8b0839741c7-39f5f8dab729bdab706fbbfdb548a0f1.ssl.cf5.rackcdn.com/922108/2/gate/tempest-slow-py3/6954225/controller/logs/_.localrc_auto.txt\n\nbut both 0.6.x images are not expected to have this bug any more so it looks like we still need a newer cirros release to resolve this. it just happens alot less oftent on the 0.6.x sersise then the 0.5.2 image so it was mitigated but not fixed by the new release.","commit_id":"469bcc760eee8260f014a7c9f00aed33de7848e1"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"69c52ff12e8ccde5e80291f88bf0c7a2b88774cb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"e5a2ff6c_d1cc6b0b","updated":"2024-07-03 07:22:09.000000000","message":"lgtm, do we wanna try with concurrency 6?","commit_id":"f207d29e322676522f905bc1d8718bcaa9f5bb70"}],"zuul.d/integrated-gate.yaml":[{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"69c52ff12e8ccde5e80291f88bf0c7a2b88774cb","unresolved":true,"context_lines":[{"line_number":84,"context_line":"      # oom issue, setting the concurrency to 4 in this job."},{"line_number":85,"context_line":"      # NOTE(sean-k-mooney): now that we use zswap we should be able to"},{"line_number":86,"context_line":"      # increase the concurrency to 6."},{"line_number":87,"context_line":"      tempest_concurrency: 4"},{"line_number":88,"context_line":"      tox_envlist: integrated-full"},{"line_number":89,"context_line":"      devstack_localrc:"},{"line_number":90,"context_line":"        USE_PYTHON3: true"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"85fa6193_79ecc3fa","line":87,"range":{"start_line":87,"start_character":27,"end_line":87,"end_character":28},"updated":"2024-07-03 07:22:09.000000000","message":"per the comment above, do we wanna try with 6 now?","commit_id":"f207d29e322676522f905bc1d8718bcaa9f5bb70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ebc9d55bcc0f404d518c125ee95ec4b087801152","unresolved":true,"context_lines":[{"line_number":84,"context_line":"      # oom issue, setting the concurrency to 4 in this job."},{"line_number":85,"context_line":"      # NOTE(sean-k-mooney): now that we use zswap we should be able to"},{"line_number":86,"context_line":"      # increase the concurrency to 6."},{"line_number":87,"context_line":"      tempest_concurrency: 4"},{"line_number":88,"context_line":"      tox_envlist: integrated-full"},{"line_number":89,"context_line":"      devstack_localrc:"},{"line_number":90,"context_line":"        USE_PYTHON3: true"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"967978e0_75e91e0e","line":87,"range":{"start_line":87,"start_character":27,"end_line":87,"end_character":28},"in_reply_to":"85fa6193_79ecc3fa","updated":"2024-07-03 12:38:43.000000000","message":"the followup patch does exactly that and revert the timeout bump\n\ni wanted to keep the two seperate","commit_id":"f207d29e322676522f905bc1d8718bcaa9f5bb70"},{"author":{"_account_id":22873,"name":"Martin Kopec","email":"mkopec@redhat.com","username":"mkopec"},"change_message_id":"2331c4f7e76ddee34d7543443f789f38de804f00","unresolved":true,"context_lines":[{"line_number":84,"context_line":"      # oom issue, setting the concurrency to 4 in this job."},{"line_number":85,"context_line":"      # NOTE(sean-k-mooney): now that we use zswap we should be able to"},{"line_number":86,"context_line":"      # increase the concurrency to 6."},{"line_number":87,"context_line":"      tempest_concurrency: 4"},{"line_number":88,"context_line":"      tox_envlist: integrated-full"},{"line_number":89,"context_line":"      devstack_localrc:"},{"line_number":90,"context_line":"        USE_PYTHON3: true"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"09913f4b_cb977905","line":87,"range":{"start_line":87,"start_character":27,"end_line":87,"end_character":28},"in_reply_to":"967978e0_75e91e0e","updated":"2024-07-03 12:43:50.000000000","message":"right, i\u0027ve missed, i\u0027m sorry","commit_id":"f207d29e322676522f905bc1d8718bcaa9f5bb70"}]}