| Summary: | Rakia: Port to next | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
| Component: | rakia | Assignee: | Mikhail Zabaluev <mikhail.zabaluev> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | enhancement | ||
| Priority: | medium | CC: | xclaesse |
| Version: | unspecified | Keywords: | patch |
| Hardware: | Other | ||
| OS: | All | ||
| URL: | http://cgit.collabora.com/git/user/xclaesse/telepathy-rakia.git/log/?h=next | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 69970, 69995 | ||
| Bug Blocks: | 69431 | ||
|
Description
Guillaume Desmottes
2013-09-30 13:10:02 UTC
Guillaume's branch: http://cgit.collabora.com/git/user/cassidy/telepathy-rakia/log/?h=next Here is Guillaume's branch, rebased on master, and with extra fixes to make tests pass: http://cgit.collabora.com/git/user/xclaesse/telepathy-rakia.git/log/?h=next > fixup! test-message: Messages have been merged into Text
> I don't know why the test was expecting the first message to fail and the 2nd to succeed, but now the first succeed... It's a mystery to me...
This could be a genuine bug. The first message gets a 404 reply, analogous to HTTP 404 - we should get a failed delivery report instead of the old SendError.
Perhaps porting Rakia to Messages on master would be illuminating?
The rest is fine. (In reply to comment #3) > > fixup! test-message: Messages have been merged into Text > > I don't know why the test was expecting the first message to fail and the 2nd to succeed, but now the first succeed... It's a mystery to me... > > This could be a genuine bug. The first message gets a 404 reply, analogous > to HTTP 404 - we should get a failed delivery report instead of the old > SendError. > > Perhaps porting Rakia to Messages on master would be illuminating? You were right, fixed that and pushed my branch. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.