| *** rlandy|bbl is now known as rlandy | 00:59 | |
| *** rlandy is now known as rlandy|out | 01:00 | |
| *** ysandeep|out is now known as ysandeep | 01:23 | |
| *** ysandeep is now known as ysandeep|breakfast | 03:16 | |
| *** ysandeep|breakfast is now known as ysandeep | 04:19 | |
| *** ysandeep is now known as ysandeep|afk | 06:06 | |
| opendevreview | Ian Wienand proposed openstack/openstack-zuul-jobs master: Build CentOS 9 RPM packages https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/839689 | 06:45 |
|---|---|---|
| *** ysandeep|afk is now known as ysandeep | 06:48 | |
| opendevreview | Ian Wienand proposed openstack/openstack-zuul-jobs master: Build CentOS 9 RPM packages https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/839689 | 06:52 |
| *** jpena|off is now known as jpena | 06:58 | |
| opendevreview | Ian Wienand proposed openstack/openstack-zuul-jobs master: Build CentOS 9 RPM packages https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/839689 | 07:14 |
| *** ysandeep is now known as ysandeep|lunch | 08:13 | |
| *** ysandeep|lunch is now known as ysandeep | 09:40 | |
| *** rlandy|out is now known as rlandy | 10:25 | |
| *** ysandeep is now known as ysandeep|afk | 10:56 | |
| *** dviroel|rover|out is now known as dviroel|rover | 11:23 | |
| opendevreview | Merged openstack/project-config master: Add the cinder-three-par to Openstack charms https://review.opendev.org/c/openstack/project-config/+/837782 | 11:38 |
| *** ysandeep|afk is now known as ysandeep | 11:45 | |
| *** dasm|off is now known as dasm | 13:10 | |
| *** ysandeep is now known as ysandeep|out | 14:10 | |
| *** jpena is now known as jpena|off | 14:14 | |
| fungi | gmann: you're clearly confused. we can continue discussing after the tc meeting ends, but neutron-fwaas was not going to be renamed into the x/ namespace. there was an option to fork it but we would not have moved it because that's against the current tc policy | 15:02 |
| fungi | "The solution to this problem is to follow the repository retirement process in openstack any time a deliverable repository is removed from current governance, regardless of whether its authors intend to continue development on it outside governance. OpenDev allows multiple repositories to have the same base names across different namespaces, so this does not mean a project has to | 15:06 |
| fungi | change its new name. It does however mean that the repository must be forked into the new namespace, leaving behind its Gerrit reviews and no redirection (the README file can certainly mention where to find continued development however). This forces existing consumers of the source code to take note of the change in governance, clarifying that no official OpenStack project team is | 15:06 |
| fungi | responsible for it any longer." | 15:06 |
| fungi | https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html | 15:06 |
| *** dviroel|rover is now known as dviroel|rover|lunch | 16:02 | |
| *** dviroel|rover|lunch is now known as dviroel|rover | 16:41 | |
| opendevreview | Gage Hugo proposed openstack/project-config master: End project gating for openstack-helm-docs https://review.opendev.org/c/openstack/project-config/+/839103 | 17:15 |
| opendevreview | Gage Hugo proposed openstack/project-config master: Retire openstack-helm-docs repo, step 3.3 https://review.opendev.org/c/openstack/project-config/+/839427 | 17:17 |
| opendevreview | Gage Hugo proposed openstack/project-config master: Retire openstack-helm-docs repo, step 3.3 https://review.opendev.org/c/openstack/project-config/+/839427 | 17:20 |
| gmann | fungi: ok, my main goal to order that way is we get the governance patch merged first before we mark the project retire in project-config and stop infra for that. | 17:21 |
| fungi | gmann: that was already the case with the gating removal depending on the governance patch | 17:22 |
| gmann | well it was not clearly documented, we used to do reverse of it always. governance patch depends on gating removal | 17:23 |
| fungi | the effective change is that now we can turn off gating and merge a change to clear out the repository before the tc agrees to retire the project, rather than only after the tc agrees | 17:23 |
| fungi | gmann: https://review.opendev.org/837787 is actually very confusing, because step #1 is to remove the deliverable from governance before proceeding with retiring its repository, but now the project-team-guide says step #1 needs to happen after steps 3-5, yet it's still "step #1" | 17:27 |
| gmann | fungi: yes because we know in governance that retirement is happening and if any strong objection then we can review on repo content removal or so. I added a note there the intension of that. | 17:28 |
| fungi | okay, but from a config-core review perspective, since there's no depends-on from the initial retirement changes to the governance removal, we can just merge those changes now, even if the tc hasn't reached agreement that they're a good idea? | 17:29 |
| gmann | confusing things there is step3-5 is mixed with single ref to opendev link which I can separate out and make it more clear about each step order | 17:30 |
| fungi | step #1 is to remove the deliverable from governance. if the change to remove the deliverable from governance hasn't merged, then that step isn't complete since the deliverable hasn't been removed from governance | 17:31 |
| fungi | has step #1 become to simply propose removal to the governance repository? | 17:31 |
| gmann | fungi: well that is needed because we have a check in governance about proper retirement of repo content. that is why governance patch needs to wait for repo content removal. let me check if we can remove that dependency without loosing the proper-retirement-check | 17:31 |
| fungi | and then other steps can proceed even though the deliverable hasn't been removed yet | 17:31 |
| fungi | gmann: oh, so 837787 was driven by the addition of consistency checks in the governance repo? that would have been very useful information to include in the commit message, or at least in a review comment. commit messages are supposed to be about why changes are being made, rather than just listing the changes being made | 17:33 |
| fungi | (hence the request for clarification i left in a comment on it after it merged, as i hadn't seen it before then) | 17:33 |
| opendevreview | Merged openstack/project-config master: End project gating for openstack-helm-docs https://review.opendev.org/c/openstack/project-config/+/839103 | 17:39 |
| *** rlandy is now known as rlandy|mtg | 19:05 | |
| *** rlandy|mtg is now known as rlandy | 19:23 | |
| *** dviroel|rover is now known as dviroel|rover|brb | 20:31 | |
| *** dasm is now known as dasm|off | 20:32 | |
| *** rlandy is now known as rlandy|out | 22:45 | |
| timburke_ | did something change with our node pool recently? i've got a test job that used to pass fairly reliably and take about an hour (and only rarely over 1.25hr), but in the last couple days has reliably timed out after two: https://zuul.opendev.org/t/openstack/builds?job_name=swift-probetests-centos-8-stream&project=openstack%2Fswift&result=SUCCESS&result=FAILURE&result=TIMED_OUT | 23:01 |
| clarkb | we've not added any new clouds. One cloud went away a ocuple months ago but thats it | 23:04 |
| clarkb | the images do get updated daily though so it is possible you're seeing a regression in the distro. Or just unlucky with noisy neighbors | 23:04 |
| timburke_ | might be something with the distro image... the centos7 equivalent has been fine: https://zuul.opendev.org/t/openstack/builds?job_name=swift-probetests-centos-7&project=openstack%2Fswift&result=SUCCESS&result=FAILURE&result=TIMED_OUT&skip=0&limit=100 | 23:15 |
| timburke_ | idk *how* a distro could regress like that, though :-/ | 23:16 |
| clarkb | timburke_: anytime there is weird slowness like that I immediately think about swapping | 23:17 |
| clarkb | maybe double check you aren't swapping? | 23:17 |
| timburke_ | host info lists the same ansible_memtotal_mb for an arbitrary (pass, fail) pair, and ansible_swaptotal_mb: 0 | 23:23 |
| clarkb | timburke_: that is collected at the beginning of the test job not the end | 23:25 |
| clarkb | devstack has some profiling data it collects | 23:25 |
| clarkb | if you use devstack there should be a file for that | 23:25 |
| timburke_ | not for this one :-/ | 23:29 |
| *** dviroel|rover|brb is now known as dviroel|rover | 23:52 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!