** 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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to