Build #1,819

Plan branch:
Nightly Distribution of the master branch

Build: #1819 failed Changes by Florian Schmaus <flo@geekplace.eu>

Stages & jobs

  1. Default Stage

  2. Deploy

Build result summary

Details

Completed
Queue duration
10 minutes
Duration
10 minutes
Labels
None
Revision
56507a761f06caff15605bafdbbe73654443ce15
Total tests
823
Failing since
#1796 (Changes by Florian Schmaus <flo@geekplace.eu> – )
Fixed in
#1831 (Rebuilt by Florian Schmaus)
No failed test found. A possible compilation error occurred.

Tests

Responsible

This build has been failing since #1796
No one has taken responsibility

Code commits

Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 56507a761f06caff15605bafdbbe73654443ce15 Merge tag '4.4.3'
Smack 4.4.3
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 524e4b1d9b38a48771a7c76ed75a8d34c2234cfb m Smack 4.4.3
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> d33a5a23c32a1e5af2f8faa0c77105d0aebd8bc6 [core] Introduce Builder.failOnUnknownStates() and unit tests
The previous approach of emitting a severe log message when a
state (descriptor) was unknown was misleading. There are valid cases
where some states are not known, if, for example, a module was
explicitly disabled.

Using Builder.failOnUnknownStates() in unit tests is far cleaner, as
the existence of unknown states is tested in a controlled environment:
one where are states are supposed to be known.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> b6c87540120a3edd421049152fcc7f730d67437c Merge branch '4.4'
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 31e4e1faf20be0fc889ea62a8737518f4ecb5aac m Do not call XmlPullParser.getName() when the event is unknown
XmlPullParser.getName() only returns a result if the current parser
event is START_ELEMENT or END_ELEMENT. If this is not the case, then
the method may throw (if StAX is used).

2 more changes...