[Desktop-packages] [Bug 1748161] Re: improve britney hints for postgres MREs
Related MPs just all got merged. Thanks! ** Also affects: postgresql-common (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: postgresql-common (Ubuntu Artful) Status: New => Fix Released ** Changed in: postgresql-common (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: postgresql-common (Ubuntu Trusty) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1748161 Title: improve britney hints for postgres MREs Status in britney: New Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Trusty: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in postgresql-common source package in Artful: Fix Released Bug description: On every postgres MRE we mention some regular failing tests. Those were mostly caused by changes in the environment and fixes were done for later Ubuntu releases but not SRUable. We should not ask the release team to force them on every SRU but cover those where it is correct with badtest entries. So this is about collecting this information and adapting hints for britney accordingly. Due to changes from lxc -> lxd (documented by pitti and carried on since then) - trusty - postgresql-9.3/armhf - Xenial - postgresql-9.5/armhf - mimeo/armhf FYI - there are also some long term always fail cases. Often had just 1-2 good runs on old pgsql versions and hen never again - resolved in latter releases. Those packages are in universe only and are already covered by hints. - Xenial - pgfincore, see [1] - orafce, see [2] - postgresql-plproxy, see [3] - pgpool2, since pgpool2/3.4.3-1 see [4] as an example Some others are known flaky tests are there as well, but I don't want to overrid all those to keep their coverage. E.g. dbconfig-common failed on artful due to mysql (but one can see in the log postgres is good which for this update is the important part). But for those above that are due to the LXC/LXD change there is no reason to bump it on every MRE. It won't change - so lets propose them unversioned to not need this over and over again. [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64 [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64 [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64 [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1748161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748161] Re: improve britney hints for postgres MREs
This is a tradeoff of effort vs gain - and in the past discussions were back and forth on trying to fix pgsql-common to make the lxd based tests work OR to hint them on britney. While in a perfect world we'd prefer the former for now I proposed the latter. Armhf is not a major target for postgresql and there never was an issue on armhf exclusive so far and on newer release this is fixed. Also this isn't backportable that well to Trusty, and to do this only for Xenial feels wrong. Really lets mask the known issues and be good. Only if denied I'd (unwillingly) reconsider this, but really only then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1748161 Title: improve britney hints for postgres MREs Status in britney: New Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Trusty: Triaged Status in postgresql-common source package in Xenial: Triaged Bug description: On every postgres MRE we mention some regular failing tests. Those were mostly caused by changes in the environment and fixes were done for later Ubuntu releases but not SRUable. We should not ask the release team to force them on every SRU but cover those where it is correct with badtest entries. So this is about collecting this information and adapting hints for britney accordingly. Due to changes from lxc -> lxd (documented by pitti and carried on since then) - trusty - postgresql-9.3/armhf - Xenial - postgresql-9.5/armhf - mimeo/armhf FYI - there are also some long term always fail cases. Often had just 1-2 good runs on old pgsql versions and hen never again - resolved in latter releases. Those packages are in universe only and are already covered by hints. - Xenial - pgfincore, see [1] - orafce, see [2] - postgresql-plproxy, see [3] - pgpool2, since pgpool2/3.4.3-1 see [4] as an example Some others are known flaky tests are there as well, but I don't want to overrid all those to keep their coverage. E.g. dbconfig-common failed on artful due to mysql (but one can see in the log postgres is good which for this update is the important part). But for those above that are due to the LXC/LXD change there is no reason to bump it on every MRE. It won't change - so lets propose them unversioned to not need this over and over again. [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64 [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64 [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64 [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1748161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748161] Re: improve britney hints for postgres MREs
mimeo was already done, the two regular armhf fails are part of an MP now that we have a "normal" SRU update again. Linking MRE to this bug ... ** Branch linked: lp:~paelzer/britney/hints-ubuntu-xenial-postgresMREII ** Branch linked: lp:~paelzer/britney/hints-ubuntu-trusty-postgresMREII -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1748161 Title: improve britney hints for postgres MREs Status in britney: New Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Trusty: Triaged Status in postgresql-common source package in Xenial: Triaged Bug description: On every postgres MRE we mention some regular failing tests. Those were mostly caused by changes in the environment and fixes were done for later Ubuntu releases but not SRUable. We should not ask the release team to force them on every SRU but cover those where it is correct with badtest entries. So this is about collecting this information and adapting hints for britney accordingly. Due to changes from lxc -> lxd (documented by pitti and carried on since then) - trusty - postgresql-9.3/armhf - Xenial - postgresql-9.5/armhf - mimeo/armhf FYI - there are also some long term always fail cases. Often had just 1-2 good runs on old pgsql versions and hen never again - resolved in latter releases. Those packages are in universe only and are already covered by hints. - Xenial - pgfincore, see [1] - orafce, see [2] - postgresql-plproxy, see [3] - pgpool2, since pgpool2/3.4.3-1 see [4] as an example Some others are known flaky tests are there as well, but I don't want to overrid all those to keep their coverage. E.g. dbconfig-common failed on artful due to mysql (but one can see in the log postgres is good which for this update is the important part). But for those above that are due to the LXC/LXD change there is no reason to bump it on every MRE. It won't change - so lets propose them unversioned to not need this over and over again. [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64 [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64 [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64 [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1748161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748161] Re: improve britney hints for postgres MREs
s/MRE/MPs/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1748161 Title: improve britney hints for postgres MREs Status in britney: New Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Trusty: Triaged Status in postgresql-common source package in Xenial: Triaged Bug description: On every postgres MRE we mention some regular failing tests. Those were mostly caused by changes in the environment and fixes were done for later Ubuntu releases but not SRUable. We should not ask the release team to force them on every SRU but cover those where it is correct with badtest entries. So this is about collecting this information and adapting hints for britney accordingly. Due to changes from lxc -> lxd (documented by pitti and carried on since then) - trusty - postgresql-9.3/armhf - Xenial - postgresql-9.5/armhf - mimeo/armhf FYI - there are also some long term always fail cases. Often had just 1-2 good runs on old pgsql versions and hen never again - resolved in latter releases. Those packages are in universe only and are already covered by hints. - Xenial - pgfincore, see [1] - orafce, see [2] - postgresql-plproxy, see [3] - pgpool2, since pgpool2/3.4.3-1 see [4] as an example Some others are known flaky tests are there as well, but I don't want to overrid all those to keep their coverage. E.g. dbconfig-common failed on artful due to mysql (but one can see in the log postgres is good which for this update is the important part). But for those above that are due to the LXC/LXD change there is no reason to bump it on every MRE. It won't change - so lets propose them unversioned to not need this over and over again. [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64 [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64 [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64 [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1748161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748161] Re: improve britney hints for postgres MREs
** Package changed: postgresql-9.5 (Ubuntu) => postgresql-common (Ubuntu) ** Also affects: postgresql-common (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: postgresql-common (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: postgresql-common (Ubuntu) Status: New => Fix Released ** Changed in: postgresql-common (Ubuntu Trusty) Status: New => Triaged ** Changed in: postgresql-common (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1748161 Title: improve britney hints for postgres MREs Status in britney: New Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Trusty: Triaged Status in postgresql-common source package in Xenial: Triaged Bug description: On every postgres MRE we mention some regular failing tests. Those were mostly caused by changes in the environment and fixes were done for later Ubuntu releases but not SRUable. We should not ask the release team to force them on every SRU but cover those where it is correct with badtest entries. So this is about collecting this information and adapting hints for britney accordingly. Due to changes from lxc -> lxd (documented by pitti and carried on since then) - trusty - postgresql-9.3/armhf - Xenial - postgresql-9.5/armhf - mimeo/armhf FYI - there are also some long term always fail cases. Often had just 1-2 good runs on old pgsql versions and hen never again - resolved in latter releases. Those packages are in universe only and are already covered by hints. - Xenial - pgfincore, see [1] - orafce, see [2] - postgresql-plproxy, see [3] - pgpool2, since pgpool2/3.4.3-1 see [4] as an example Some others are known flaky tests are there as well, but I don't want to overrid all those to keep their coverage. E.g. dbconfig-common failed on artful due to mysql (but one can see in the log postgres is good which for this update is the important part). But for those above that are due to the LXC/LXD change there is no reason to bump it on every MRE. It won't change - so lets propose them unversioned to not need this over and over again. [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64 [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64 [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64 [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1748161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748161] Re: improve britney hints for postgres MREs
Notes: [12:29] cpaelzer: one note: when you do the next postgresql MRE, get the SRU reviewer to accept postgresql-common and want for binaries to be published before accepting the others [12:29] Then the dep8 test will definitely run against the new one. [12:30] (I don't think a versioned dependency relationship is needed here) [12:30] s/want/wait/ [12:31] that's not true [12:31] dependencies are satisfied from relelase/-updates as far as possible [12:31] --> milardovich (~milardovi@190.193.40.124) has joined this channel. [12:32] you either need a versioned test dependency, or explicitly trigger the test to run against p-common in -proposed [12:32] Oh. [12:32] (the latter appears better to me) [12:32] OK we'll do an explicit trigger [12:32] Thanks [12:32] i. e. see it fail, re-trigger armhf tests against p-common in -proposed, that should succeed and also validate the p-common SRU [12:33] although bumping the test dep in postgresql's d/tests/comtrol isn't wrong [12:33] just as I did last week with some other migrations [12:33] I generally shy away from bumping versioned deps to reflect bug fixes on the other side [12:33] (except the typoed file name, of course - tpying is hrad!) [12:34] Seems like a recipe to madness [12:34] yeah, and breaks the clean backports, too [12:34] so I think manual trigger for that one round is just fine [12:34] Yep -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1748161 Title: improve britney hints for postgres MREs Status in britney: New Status in postgresql-common package in Ubuntu: Fix Released Status in postgresql-common source package in Trusty: Triaged Status in postgresql-common source package in Xenial: Triaged Bug description: On every postgres MRE we mention some regular failing tests. Those were mostly caused by changes in the environment and fixes were done for later Ubuntu releases but not SRUable. We should not ask the release team to force them on every SRU but cover those where it is correct with badtest entries. So this is about collecting this information and adapting hints for britney accordingly. Due to changes from lxc -> lxd (documented by pitti and carried on since then) - trusty - postgresql-9.3/armhf - Xenial - postgresql-9.5/armhf - mimeo/armhf FYI - there are also some long term always fail cases. Often had just 1-2 good runs on old pgsql versions and hen never again - resolved in latter releases. Those packages are in universe only and are already covered by hints. - Xenial - pgfincore, see [1] - orafce, see [2] - postgresql-plproxy, see [3] - pgpool2, since pgpool2/3.4.3-1 see [4] as an example Some others are known flaky tests are there as well, but I don't want to overrid all those to keep their coverage. E.g. dbconfig-common failed on artful due to mysql (but one can see in the log postgres is good which for this update is the important part). But for those above that are due to the LXC/LXD change there is no reason to bump it on every MRE. It won't change - so lets propose them unversioned to not need this over and over again. [1]: http://autopkgtest.ubuntu.com/packages/pgfincore/xenial/amd64 [2]: http://autopkgtest.ubuntu.com/packages/orafce/xenial/amd64 [3]: http://autopkgtest.ubuntu.com/packages/postgresql-plproxy/xenial/amd64 [4]: http://autopkgtest.ubuntu.com/packages/pgpool2/xenial/amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1748161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
