[nova] libvirt+virtuozzo CI is broken
I noticed this today: http://openstack-3rd-party-virtuozzo-ci-logs.virtuozzo.com/24/638324/30/chec... 2019-05-24 02:16:51.833 | + :pre_test_hook:L13: git fetch https://review.opendev.org/p/openstack/nova refs/changes/86/506686/4 2019-05-24 02:17:01.100 | From https://review.opendev.org/p/openstack/nova 2019-05-24 02:17:01.102 | * branch refs/changes/86/506686/4 -> FETCH_HEAD 2019-05-24 02:17:01.109 | + :pre_test_hook:L14: git cherry-pick FETCH_HEAD 2019-05-24 02:17:01.311 | error: could not apply 789a1f2... don't add device address if there is no any units 2019-05-24 02:17:01.313 | hint: after resolving the conflicts, mark the corrected paths 2019-05-24 02:17:01.315 | hint: with 'git add <paths>' or 'git rm <paths>' 2019-05-24 02:17:01.318 | hint: and commit the result with 'git commit' Looks like the CI is broken because this change is in merge conflict: https://review.opendev.org/#/c/506686/ Does anyone plan on working on that? It's had a -1 on it since August of 2018. Is that change really needed for the CI to work? -- Thanks, Matt
Looks like the CI is broken because this change is in merge conflict:
https://review.opendev.org/#/c/506686/
Does anyone plan on working on that? It's had a -1 on it since August of 2018. Is that change really needed for the CI to work?
This work was done in [1], so I abandoned the above change. Of course, that won't help the CI to pass, since it appears to be hardcoding that patch number somewhere. Anyone know where the setup lives for this? (Or better yet, who owns it?) efried [1] https://review.opendev.org/#/c/611974/
On 2019-05-30 16:14:55 -0500 (-0500), Eric Fried wrote: [...]
Anyone know where the setup lives for this? (Or better yet, who owns it?) [...]
Is it maybe the same as: https://wiki.openstack.org/wiki/ThirdPartySystems/Virtuozzo_CI -- Jeremy Stanley
Is it maybe the same as:
https://wiki.openstack.org/wiki/ThirdPartySystems/Virtuozzo_CI
Thanks Jeremy, seems worth a try. CC'ing... Hello Virtuozzo CI maintainers! Please read [1] and [2] regarding the broken-ness of the libvirt+virtuozzo CI. Our speculation is that the CI environment is hardcoding a particular patch as a dependency, and breaking because that patch is (was) in merge conflict. Because that same code fix was developed elsewhere, and has merged, you should be able to remove the dependency entirely from your CI setup. Thanks, efried [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006746.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006754.html
participants (3)
-
Eric Fried
-
Jeremy Stanley
-
Matt Riedemann