Build #1,659

Plan branch:
Nightly Distribution of the master branch

Build: #1659 failed Rebuilt by Florian Schmaus

Stages & jobs

  1. Default Stage

  2. Deploy

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
10 minutes
Labels
None
Revision
7e25c3ada556efc744112ac975325560656a6875
Total tests
725
Failing since
#1655 (Changes by Florian Schmaus <flo@geekplace.eu> – )
Fixed in
#1669 (Changes by Florian Schmaus <flo@geekplace.eu>)
Number of retries
1
No failed test found. A possible compilation error occurred.

Tests

Responsible

  • Florian Schmaus Florian Schmaus Automatically assigned

Code commits

Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 7e25c3ada556efc744112ac975325560656a6875 Merge branch '4.3'
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 2ceadc0de106a25012c5bcae1665a96764006d4f m Introduce verificationSuccessful boolean
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> f60e4055ec529f0b8160acedf13275592ab10a4b m Use ACE representation of XMPP domain on certificate verification
This is based on the patch provided by Georg Lukas, modified to take
XMPP domain names that can not be represented as DNS names into
account. See https://github.com/Flowdalic/Smack/pull/23/commits/c42d2eea24bc86d9de5da398d341f6085a50dd33#r269250137

Fixes SMACK-870.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 381190a45c0cafc13171611689d181f154bb68d6 m Add ConnectionConfiguration.getXmppServiceDomainAsDnsNameIfPossible()
in preperation of SMACK-870, so that the DNS name can be used for the
certificate verification.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> edcde28ecdfa56cd55ed68dd4e2a6a0566e5aaa7 m Set UncaughtExceptionHandler for CACHED_EXECUTOR_SERVICE
In order to avoid uncaught exceptions from terminating the
program (SMACK-896).

2 more changes...

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSMACK-868Could not obtain issue details from Jira
Unknown Issue TypeSMACK-870Could not obtain issue details from Jira
Unknown Issue TypeSMACK-896Could not obtain issue details from Jira