Build: #1220 was successful Manual run by daryl herzmann

Build result summary

Details

Completed
Queue duration
13 seconds
Duration
1 minute
Labels
None
Agent
Default Agent
Revision
148cf29b3e7e21b7119a6eb0e8dd2d9b5634e72f
Total tests
466
Successful since
#749 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 148cf29b3e7e21b7119a6eb0e8dd2d9b5634e72f Merge pull request #1883 from guusdk/OF-2289_cache-key
OF-2290 / OF-2278: Per-cache locks
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 437e1a3ca3505cff91f316b6247b32239ebe6e48 Merge pull request #1885 from guusdk/OF-2292_MUC-clustering-CME
OF-2292: Prevent ConcurrentModificationException when syncing cluster…
Guus der Kinderen Guus der Kinderen dd787e50333ba992a884d711e58cfc8d875b77d2 OF-2292: Prevent ConcurrentModificationException when syncing clustered MUC occupants
This creates a copy of a collection over which is being operated, to prevent the collection to be modified while being iterated over.
Guus der Kinderen Guus der Kinderen 5b40c0623e2e897a18cb4de6194bb05b3322b4e7 m OF-2290 / OF-2278: Per-cache locks
Locks that are obtained from a cache are though to refer to the key value of an entry. A lock should:
- be unique to a cache (eg: when acquiring a lock for cache A, it should not interfere with operations on cache B)
- based on equals and hashcode, not equality by reference (==). For example: caches that use JIDs are they key typically use different but equal instances of the same JID value.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2278Could not obtain issue details from Jira
Unknown Issue TypeOF-2289Could not obtain issue details from Jira
Unknown Issue TypeOF-2290Could not obtain issue details from Jira
Unknown Issue TypeOF-2292Could not obtain issue details from Jira