| opendevreview | Takashi Kajinami proposed openstack/tempest master: Use service_available option to detect Neutron https://review.opendev.org/c/openstack/tempest/+/918191 | 01:39 |
|---|---|---|
| opendevreview | Merged openstack/whitebox-tempest-plugin master: Evalute adding serial decorator to tests https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/916639 | 02:48 |
| opendevreview | Merged openstack/whitebox-tempest-plugin master: Update shared set depending on microversion https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/918009 | 02:48 |
| opendevreview | Maxim Sava proposed openstack/tempest master: Add image dependencies test for image <-> instance snapshot https://review.opendev.org/c/openstack/tempest/+/914198 | 05:31 |
| opendevreview | Amit Uniyal proposed openstack/whitebox-tempest-plugin master: evacuation tests https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/915393 | 06:02 |
| opendevreview | Rajesh Tailor proposed openstack/tempest master: Check nova fix for bug 2033541 works https://review.opendev.org/c/openstack/tempest/+/918383 | 06:08 |
| opendevreview | Maxim Sava proposed openstack/tempest master: Add image dependencies test for image <-> instance snapshot https://review.opendev.org/c/openstack/tempest/+/914198 | 10:13 |
| kopecmartin | gmann: frickler do you know if there are any exact rules on project core members and their affiliation to a company? I had a theoretical discussion and we were wondering if we have specific rules or we just act logically and the most transparent way possible, e.g. if i consider a new core to a project, do i need to take into account their affiliation to a company? hmm, let me rephrase, is there a percentage recommending company affiliation | 10:18 |
| kopecmartin | of all core members for example something like "max 75% of contributors should belong to a single company"? | 10:18 |
| frickler | kopecmartin: iiuc this is up to the project, there are no hard rules. given the current state of the community, my personal opinion is that any contributor is better than no contributor | 10:36 |
| frickler | kolla has some rule that a change submitted by one company should not get approved only by reviewers from that company, but that still doesn't tell anything about who is allowed to be core reviewer at all | 10:38 |
| kopecmartin | thanks, that's my understanding too | 10:42 |
| opendevreview | Denis Silakov proposed openstack/bashate master: Fix detection of func declaration without keyword https://review.opendev.org/c/openstack/bashate/+/918317 | 10:53 |
| opendevreview | Amit Uniyal proposed openstack/whitebox-tempest-plugin master: evacuation tests https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/915393 | 12:02 |
| opendevreview | Amit Uniyal proposed openstack/tempest master: Log request-id in test_delete_server_while_in_verify_resize_state test https://review.opendev.org/c/openstack/tempest/+/918439 | 12:27 |
| *** haleyb is now known as haleyb|out | 12:40 | |
| opendevreview | Elod Illes proposed openstack/grenade stable/2023.2: Fix grenade-skip-level job to use unmaintained/zed https://review.opendev.org/c/openstack/grenade/+/918452 | 13:29 |
| opendevreview | Dan Smith proposed openstack/tempest master: Add servers test with LUN direct volume https://review.opendev.org/c/openstack/tempest/+/918457 | 15:18 |
| gmann | kopecmartin: yes, there is no rule on those, it is up to project. previously in tempest, nova and a few more projects, we used to have rule that both core on any approved patch should not be from same company. But as number of contributors reduced, that was not so applicable in many project. | 16:51 |
| kopecmartin | gmann: makes sense, thanks | 17:18 |
| gmann | kopecmartin: diversity is great thing to have but at same time it is most difficult thing too especially in OSS ecosystem | 17:20 |
| opendevreview | Dan Smith proposed openstack/tempest master: Add servers tests with LUN direct volume https://review.opendev.org/c/openstack/tempest/+/918457 | 18:18 |
| opendevreview | James Parker proposed openstack/whitebox-tempest-plugin master: Add AMD Sev instance creation test https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/809441 | 18:53 |
| opendevreview | Dan Smith proposed openstack/devstack master: Use OSCaaS to speed up devstack runs https://review.opendev.org/c/openstack/devstack/+/676016 | 18:57 |
| gmann | kopecmartin: commented on this, I would like this to see running in at least one of the job https://review.opendev.org/c/openstack/tempest/+/897847 | 19:49 |
| gmann | kopecmartin: I am ok to include this in the release but that release is for end of zed support so it hardly matter we add this change in this release or not bcz we will be having this on master whihc all supported branches use | 19:50 |
| opendevreview | James Parker proposed openstack/whitebox-tempest-plugin master: Add a waiter when checking pci allocation https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/918480 | 19:51 |
| opendevreview | James Parker proposed openstack/whitebox-tempest-plugin master: Add a waiter when checking pci allocation https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/918480 | 19:53 |
| kopecmartin | gmann: thanks, yeah, it makes no difference in upstream, it just makes it a bit easier downstream .. any preference for the job? i see that run classic cleanup in the tempest-full-parallel and prefix cleanup in tempest-full-py3-ipv6 | 22:01 |
| kopecmartin | https://opendev.org/openstack/tempest/src/branch/master/zuul.d/tempest-specific.yaml#L37-L62 | 22:02 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!