Tests fail on armel/panda
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
postgresql-8.4 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
postgresql-9.1 (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
All postgresql versions used to build fine on the older babbage buildds, and on Debian's armel builders. However, on Ubuntu's Panda buillds a lot of the tests fail:
parallel group (19 tests): comments polygon lseg timetz macaddr inet date reltime abstime tinterval interval circle point timestamptz box tstypes path time timestamp
point ... FAILED (test process exited with exit code 2)
lseg ... ok
box ... FAILED (test process exited with exit code 2)
path ... FAILED (test process exited with exit code 2)
polygon ... ok
circle ... FAILED (test process exited with exit code 2)
date ... FAILED (test process exited with exit code 2)
time ... FAILED (test process exited with exit code 2)
timetz ... FAILED (test process exited with exit code 2)
timestamp ... FAILED (test process exited with exit code 2)
timestamptz ... FAILED (test process exited with exit code 2)
interval ... FAILED (test process exited with exit code 2)
abstime ... FAILED (test process exited with exit code 2)
reltime ... FAILED (test process exited with exit code 2)
tinterval ... FAILED (test process exited with exit code 2)
inet ... FAILED (test process exited with exit code 2)
macaddr ... FAILED (test process exited with exit code 2)
tstypes ... FAILED (test process exited with exit code 2)
comments ... ok
[...]
and eventually hang forever.
This sounds like our debian/
Changed in postgresql-9.1 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Martin Pitt (pitti) |
tags: | added: armel ftbfs panda |
Changed in postgresql-8.4 (Ubuntu): | |
status: | New → Invalid |
no longer affects: | postgresql-9.1 (Ubuntu Natty) |
no longer affects: | postgresql-9.1 (Ubuntu Maverick) |
no longer affects: | postgresql-8.4 (Ubuntu Oneiric) |
no longer affects: | postgresql-9.1 (Ubuntu Lucid) |
Changed in postgresql-8.4 (Ubuntu Maverick): | |
status: | New → Fix Committed |
Changed in postgresql-8.4 (Ubuntu Natty): | |
status: | New → Fix Committed |
Changed in postgresql-8.4 (Ubuntu Lucid): | |
status: | New → Fix Committed |
think would be cool if devplatform team could look into this as part of their porting effort. Seems it's a problem t have the tests fail with the new precise policy. pitti said that __sync_ lock_test_ and_set( ) seems to not work