ubuntu-push FTBFS on xenial
Bug #1517189 reported by
dobey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-push (Ubuntu) |
Fix Released
|
Critical
|
Jonas G. Drange |
Bug Description
Several test failures are occurring on xenial, even on amd64 and i386 now.
See for example:
Related branches
lp:~jonas-drange/ubuntu-push/lp1517189
- Samuele Pedroni: Approve
-
Diff: 492 lines (+88/-50)17 files modifiedaccounts/caccounts.go (+2/-0)
click/click_test.go (+28/-13)
client/service/postal_test.go (+16/-11)
client/service/service_test.go (+3/-1)
client/session/session_test.go (+20/-8)
config/config_test.go (+1/-1)
debian/rules (+0/-6)
dependencies.tsv (+2/-2)
http13client/z_last_test.go (+2/-1)
identifier/testing/testing_test.go (+3/-2)
launch_helper/cual/cual_c.go (+2/-0)
launch_helper/kindpool.go (+1/-1)
launch_helper/kindpool_test.go (+1/-1)
messaging/cmessaging/cmessaging_c.go (+2/-0)
scripts/connect-many.py (+1/-1)
signing-helper/CMakeLists.txt (+2/-2)
urldispatcher/curldispatcher/curldispatcher_c.go (+2/-0)
lp:ubuntu-push/automatic
- Ubuntu Push Hackers: Pending requested
-
Diff: 65 lines (+3/-7)6 files modifiedbus/connectivity/connectivity_test.go (+1/-1)
bus/networkmanager/networkmanager.go (+1/-1)
client/service/postal_test.go (+1/-0)
debian/source/format (+0/-1)
docs/example-server/.bzrignore (+0/-1)
docs/example-server/.gitignore (+0/-3)
- Ubuntu Push Hackers: Pending requested
-
Diff: 84 lines (+34/-15)2 files modifiedclient/service/postal.go (+17/-14)
client/service/postal_test.go (+17/-1)
Changed in ubuntu-push (Ubuntu): | |
assignee: | nobody → Jonas G. Drange (jonas-drange) |
Changed in ubuntu-push (Ubuntu): | |
status: | New → Fix Committed |
To post a comment you must log in.
there's a branch sitting that just needs some cleanups that fixes most of those errors:
https:/ /code.launchpad .net/~mwhudson/ ubuntu- push/1. 5-test- fixery
it doesn't fix the errors in client/service though, which I haven't dug into, and also are random, not always the same test/tests fail, probably scheduler changes related