FTBFS due to broken unit tests
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | python-pysaml2 (Ubuntu) |
Undecided
|
Łukasz Zemczak | ||
Bug Description
In the wily test-rebuild [1] python-pysaml2 seems to fail to build due to multiple errors and failures in the unit tests. The log:
=======
platform linux2 -- Python 2.7.10 -- py-1.4.30 -- pytest-2.7.2
rootdir: /«PKGBUILDDIR», inifile:
collected 493 items / 1 errors
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_05_md.py .......
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_60_sp.py ss
tests/test_62_vo.py ........
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
tests/test_
(...)
[1] http://
Related branches
| Łukasz Zemczak (sil2100) wrote : | #1 |
| Łukasz Zemczak (sil2100) wrote : | #2 |
Looks like we can get this fixed without pulling in the new upstream version with this:
https:/
| Łukasz Zemczak (sil2100) wrote : | #3 |
After applying the patch there are still test failures. The first two (in tests/test_
https:/
The final failure needs to be fixed manually. The test_eptid_mongo_db test from tests/test_
| Łukasz Zemczak (sil2100) wrote : | #4 |
Ok, prepared a debdiff fixing all FTBFS issues. Almost all the fixes that are part of distro patches in this version are cherry-picked from upstream (will contact them about certain aspects of the testing suite). Debian seems to prepare for switching to a newer python-pysaml2 (3.0.0 in experimental), not sure if it make sense to forward there.
Could someone sponsor this for me? Thanks!
| Barry Warsaw (barry) wrote : | #5 |
There's a typo in the changelog. It's "d/control" not "d/rules". I'll fix that when I sponsor. Other than that, the debdiff looks great and a local build succeeds. Thanks!
| Launchpad Janitor (janitor) wrote : | #6 |
This bug was fixed in the package python-pysaml2 - 2.4.0-0ubuntu2
---------------
python-pysaml2 (2.4.0-0ubuntu2) wily; urgency=medium
* debian/control:
- Depend on python-pymongo versions 3.0 and higher
* debian/
- Cherry-pick fix pysaml2 with python-pymongo 3.0
* debian/
- Fix the newly failing test failures (LP: #1503698)
-- Łukasz 'sil2100' Zemczak <email address hidden> Thu, 08 Oct 2015 20:16:42 +0200
| Changed in python-pysaml2 (Ubuntu): | |
| status: | In Progress → Fix Released |
| Łukasz Zemczak (sil2100) wrote : | #7 |
Oh, right! Yeah, I think I was not thinking when typing that. pysaml2 really needs a better test suite. I generally think that relying on actual time when having some pre-generated timestamps is a bad idea in overall. They should mock their time methods and stop relying on real time during tests, otherwise the test suite will have to be updated again soon.
Thanks for sponsoring!


At least parts of the failures are due to the new pymongo, which for instance deprecated the 'Connection' object. Looking if we can easily distro-patch it to work. Debian also doesn't have it changed for the new pymongo. Maybe we could sync python-pysaml2 3.0.0-1 from experimental? Looking into that still.