Merge lp:~paelzer/britney/hints-ubuntu-trusty-postgresqlMREs into lp:~ubuntu-sru/britney/hints-ubuntu-trusty

Proposed by Christian Ehrhardt 
Status: Rejected
Rejected by: Brian Murray
Proposed branch: lp:~paelzer/britney/hints-ubuntu-trusty-postgresqlMREs
Merge into: lp:~ubuntu-sru/britney/hints-ubuntu-trusty
Diff against target: 11 lines (+2/-2)
1 file modified
brian-murray (+2/-2)
To merge this branch: bzr merge lp:~paelzer/britney/hints-ubuntu-trusty-postgresqlMREs
Reviewer Review Type Date Requested Status
Robie Basak Needs Fixing
Ubuntu Package Archive Administrators Pending
Review via email: mp+337350@code.launchpad.net

Description of the change

There are some autopkgtest issues which won't be resolved.
So lets update the hints accordingly.

Documentation in bug 1748161 (and the last few MREs were it was discussed every time, links to old MREs can be found in the description of bug 1730661)

To post a comment you must log in.
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Resubmitted to the correct target branch

Revision history for this message
Robie Basak (racb) wrote :

Looks like pitti fixed this trivially in https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/commit/?id=fc40fc34ce in the development release. Instead of ignoring all armhf test results, could this be cherry-picked into the next postgres MRE SRU instead? I think it would fix the failures, and then we'd still be able to catch armhf-related regressions in postgres instead, rather than the test effectively being turned off. Right now at least the test success (apart from the stderr) is being checked manually.

review: Needs Fixing
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

We discussed on IRC with Pitti and agreed that we will:
1. drop this MP
2. bundle the test fix on postgresql-common with the next postgresql MRE

Killing this MP

Revision history for this message
Brian Murray (brian-murray) wrote :

> We discussed on IRC with Pitti and agreed that we will:
> 1. drop this MP
> 2. bundle the test fix on postgresql-common with the next postgresql MRE
>
> Killing this MP

I did the killing.

Revision history for this message
Brian Murray (brian-murray) wrote :

> We discussed on IRC with Pitti and agreed that we will:
> 1. drop this MP
> 2. bundle the test fix on postgresql-common with the next postgresql MRE
>
> Killing this MP

I did the killing.

Revision history for this message
Brian Murray (brian-murray) wrote :

> We discussed on IRC with Pitti and agreed that we will:
> 1. drop this MP
> 2. bundle the test fix on postgresql-common with the next postgresql MRE
>
> Killing this MP

I did the killing.

Unmerged revisions

17. By Christian Ehrhardt 

postgres issues due to LXC to LXD should cover all versions (LP: #1748161)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'brian-murray'
2--- brian-murray 2017-09-28 17:17:10 +0000
3+++ brian-murray 2018-02-08 11:26:17 +0000
4@@ -1,5 +1,5 @@
5 # buggy test doesn't work with proxy configuration on autopkgtest.u.c
6 force-badtest apt/1.0.1ubuntu2.15
7
8-# per pitti - "fallout from moving from LXC to LXD" fixed in devel
9-force-badtest postgresql-9.3/9.3.19-0ubuntu0.14.04/armhf
10+# per pitti - "fallout from moving from LXC to LXD"
11+force-badtest postgresql-9.3/armhf/all

Subscribers

People subscribed via source and target branches