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: #2135 failed Changes by Guus der Kinderen

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
1 minute
Labels
None
Agent
Default Agent
Revision
5f530f2f976fecf049c6c2225c00a47b2f4cc56e
Total tests
452
Fixed in
#2137 (Changes by Dan Caseley <dan@caseley.me.uk>)

Tests

Responsible

No one has taken responsibility for this failure

Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen 5f530f2f976fecf049c6c2225c00a47b2f4cc56e OF-2243: Version check task should not be busy doing nothing
Instead of scheduling an immediate task that does nothing for X seconds, schedule a task that will start in X seconds, that immediately does something.

This prevents using up a thread from the TaskEngine that's not doing anything for a significant amount of time.

Tests

New test failures 1
Status Test View job Duration
Collapse Failed LoginLimitManagerTest lockoutsWillBeAudited
Build < 1 sec
org.mockito.exceptions.verification.TooManyActualInvocations: 
securityAuditManager.logEvent(
    "test-user",
    "Failed admin console login attempt",
    "A failed login attempt to the admin console was made from address a.b.c.d. "
);
Wanted 10 times:
-> at org.jivesoftware.admin.LoginLimitManagerTest.lockoutsWillBeAudited(LoginLimitManagerTest.java:51)
(38 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2243Could not obtain issue details from Jira