Build: #66 was successful Manual run by Florian Schmaus

Stages & jobs

  1. Default Stage

  2. Deploy

Build result summary

Details

Completed
Queue duration
2 seconds
Duration
7 minutes
Labels
None
Revisions
Smack (master)
92825020ab6f51a7689a2764077f8dde14c7f8ff
Smack (4.2)
fe61922fb75a11999d50c202800089fee8ba044a
Total tests
476
Successful since
#64 ()

Tests

Code commits

Smack (4.2)
Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> fe61922fb75a11999d50c202800089fee8ba044a Merge pull request #179 from damencho/4.2
Makes xmpperror descriptive text optional as said in the rfc.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> a66c42834fe93c6a0fb221be3aee43f5278aa50a Add findServicesDiscoveryInfo() variant
which does not log some exceptions, but instead comes with an optional
output paramater which returns the encountered exceptions.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 5ef6853db6873115d53d9bb65780b6f5a8d549f9 Improve MultiUserChat's leave() and destroy() login
Remove the "if (!joined) return" guard in leave() this allows to
resync the instances state with the real world state in case they ever
get out of sync.

Also call userHasLeft() in even if leave() throws and in certain
situations if destroy() throws.

Thanks to Дамян Минков and Ingo Bauersachs for pointing this out.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 0a4cd79d4ea0111dbe7e25e8ca191a2c40b53bed Call MultiUserChat.userHasLeft() before invoking listeners
in case a listener throws, userHasLeft() will eventually have set the
MutliUserChat instance to the right state.
damencho <damencho@jitsi.org> damencho <damencho@jitsi.org> 44e4607259fddf0c3d6b75ea78cb01ef4583e3ed Fix memory leak in MutliUserChat.removeConnectionCallback().
Fix memory leak by removing subject listener
in MutliUserChat.removeConnectionCallback().
Fixes SMACK-782.

Configuration changes

Some of the jobs or stages referenced by this result no longer exist.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSMACK-779Could not obtain issue details from Jira
Unknown Issue TypeSMACK-782Could not obtain issue details from Jira