You have been subscribed to a public bug:

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.


** Affects: britney
     Importance: Undecided
         Status: New

** Affects: postgresql-common (Ubuntu)
     Importance: Undecided
         Status: New

improve britney hints for postgres MREs
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to postgresql-common in Ubuntu.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to