Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #958 was successful Rebuilt by Florian Schmaus

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
11 minutes
Labels
None
Agent
ip-172-31-27-151.eu-central-1.compute.internal
Revision
63e25bc8cd2ebe513d7ab02c681c5c3ec6f8b6d5
Total tests
826
First to pass since
#956 (Changes by Florian Schmaus)
Number of retries
1

Tests

Code commits

Author Commit Message Commit date
Florian Schmaus Florian Schmaus 63e25bc8cd2ebe513d7ab02c681c5c3ec6f8b6d5 Merge pull request #624 from guusdk/SMACK-949_MUC-join-state-after-destroy
[muc] State of MUC should reflect room destruction
Guus der Kinderen Guus der Kinderen 93efdf3eda73c1c43f72d9a299e6bc1435b5565c m [muc] State of MUC should reflect room destruction
After a room is destroyed, the MultiUserChat-stored representation of the 'join' state of any occupant should be updated to reflect that the user is no longer in the room.

This fixes a problem where an occupant (that not itself triggered the destruction) appears to continue be part of a room after its destruction.

Additional integration test assertions are added to check for the invalid state fixed by this commit.

fixes SMACK-949

Configuration changes

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

Jira issues

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