ldd tests fail on lucid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pkgme-devportal |
Fix Released
|
High
|
Jonathan Lange |
Bug Description
Tests running...
=======
FAIL: tests.test_
-------
Traceback (most recent call last):
File "/home/
deps)
File "/home/
self.
File "/home/
raise MismatchError(
MismatchError: !=:
reference = {'/home/
actual = {'/home/
=======
FAIL: tests.test_
-------
Traceback (most recent call last):
File "/home/
deps)
File "/home/
self.
File "/home/
raise MismatchError(
MismatchError: !=:
reference = {'/home/
'/home/
actual = {'/home/
'/home/
=======
FAIL: tests.test_
-------
Traceback (most recent call last):
File "/home/
deps)
File "/home/
self.
File "/home/
raise MismatchError(
MismatchError: !=:
reference = {'/home/
actual = {'/home/
Ran 55 tests in 2.488s
FAILED (failures=3)
I think this is a multiarch change, so lucid has different paths for some libraries.
I don't know what the right fix is, but does this point to a problem we will have if our
production deployment is on lucid?
Thanks,
James
Related branches
- James Westby: Approve
-
Diff: 128 lines (+2/-95)2 files modifieddevportalbinary/binary.py (+2/-57)
devportalbinary/tests/test_binary.py (+0/-38)
Changed in pkgme-binary: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in pkgme-binary: | |
status: | Triaged → In Progress |
assignee: | nobody → Jonathan Lange (jml) |
Changed in pkgme-binary: | |
status: | In Progress → Fix Committed |
Changed in pkgme-binary: | |
status: | Fix Committed → Fix Released |
Not a problem for two reasons:
1. We discard the full path to the library anyway – it's not needed to figure out dependencies.
2. We don't actually use the ldd code at all. We use objdump instead.
All in all, the simplest solution is to just excise the ldd code from the tree.