omnidb-dropped-test : lp:~paelzer/britney/+git/hints-ubuntu : Git : Code : britney

Get this branch:: git clone -b omnidb-dropped-test https://git.launchpad.net/~paelzer/britney/+git/hints-ubuntu

Only Christian Ehrhardt  can upload to this branch. If you are Christian Ehrhardt  please log in for upload directions.

Branch merges

Merged into ~ubuntu-release/britney/+git/hints-ubuntu:devel at revision 7b3a921abe1e9652b5096fb5e459a3ecf1861d47

Łukasz Zemczak: Approve on 2020-11-26

Branch information

Name:: omnidb-dropped-test

Repository:: lp:~paelzer/britney/+git/hints-ubuntu

Recent commits

7b3a921... by Christian Ehrhardt  on 2020-11-26

omnidb 2.17.0+ds-2build1 can't work with postgresql-13

Of those 2.17.0+ds-2build1 can't work with the new combo of
postgresql-13/postgresql-common that I need to migrate.

But we can't "fix" omnidb either, since >=3.0 has dropped the test
entriely due o the fact that the plugin functionality was moved to a
different source.

Now we have a growing list of tests that is automatically retried vs the
version in -release [1].
But at the same time we can't make it "test against 3.x to realize
things are ok" as that will fail with "SKIP no tests in this package"
which is considered a "Neutral" state [2].

Given the current size of the ppc64 queue I'm proposing to ignore the
old test results - which will be more effective than triggering it to
report a "neutral" fail and then hoping this will make it pass.

[1]: https://autopkgtest.ubuntu.com/packages/o/omnidb/hirsute/ppc64el
[2]: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/o/omnidb/20201124_070404_c8486@/log.gz