Thursday, 2021-08-12

*** ykarel|away is now known as ykarel04:57
*** akekane_ is now known as abhishekk06:03
*** rpittau|afk is now known as rpittau06:22
*** dpawlik6 is now known as dpawlik07:07
*** jpena|off is now known as jpena07:33
*** elodilles_pto is now known as elodilles08:12
*** ykarel is now known as ykarel|lunch08:27
*** sshnaidm|afk is now known as sshnaidm08:55
*** akekane_ is now known as abhishekk09:08
*** ykarel|lunch is now known as ykarel09:46
*** jcapitao is now known as jcapitao_lunch11:10
*** jpena is now known as jpena|lunch11:33
*** rlandy is now known as rlandy|rover11:41
*** jcapitao_lunch is now known as jcapitao11:56
*** jpena|lunch is now known as jpena12:24
*** jpena is now known as jpena|off12:33
zulfungi: one more question after the parent has been merged and the child has a +2/+1 recheck should just kick if off correct?12:34
fungizul: normally, children would be automatically enqueued into the gate pipeline when their git parents are, so if that didn't happen on its own there may also be some other problem with the change12:36
zulok12:36
fungiwhich change isn't getting enqueued?12:37
fungii can play spot-the-issue12:37
zulhold on12:49
zuli just rechecked it it https://review.opendev.org/c/starlingx/ha/+/80236212:49
fungizul: the problem there is that it has a git parent which can never appear in the branch history. its parent is change 788325 revision #2 (a1ce600), but what merged was change 788325 revision #4 (1f48745)12:53
zulso how do i fix it?12:53
fungizuul tries to test it for you in check anyway by rebasing it on the branch tip, but can't enqueue it into the gate pipeline because gerrit will refuse to let it merge12:53
fungirebasing it on the branch tip at this point is the simplest solution12:54
zulok12:54
fungithe way you avoid it in the future is to always rebase child changes on updates you push for their parents12:54
fungigenerally if i'm working on a series of git commits, i'll use git rebase -i and edit a particular commit in the series that way, so that when i git rebase --continue all the children are rebased on it automatically12:55
fungigerrit also has a "rebase" button, though it will only work for trivial rebases (those where you don't need to resolve any merge conflicts)12:55
zulgotcha12:56
*** ysandeep|PTO is now known as ysandeep13:26
*** dmellado_ is now known as dmellado14:24
*** jpena|off is now known as jpena14:43
clarkbI do something similar but will typically do my edits at the end of my stack then commit them with annotations like squash into foo and squash into bar. Then I git rebase -i HEAD~X and reorder things. I find this trade off for slightly more complex rebase is worthwhile as it makes the actual writing of the changes simpler15:19
fungii mainly avoid reordering unless necessary, as i often run into painful merge conflicts to resolve when i switch around commits touching the same or nearby blocks of code15:23
*** rpittau is now known as rpittau|afk15:31
*** jpena is now known as jpena|off15:34
*** ykarel is now known as ykarel|away16:31
opendevreviewClark Boylan proposed openstack/project-config master: Revert "Disable airship citylcoud nodepool provider"  https://review.opendev.org/c/openstack/project-config/+/80441716:40
opendevreviewMerged openstack/project-config master: Revert "Disable airship citylcoud nodepool provider"  https://review.opendev.org/c/openstack/project-config/+/80441717:01
*** sshnaidm is now known as sshnaidm|afk17:55

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