Build: #564 was successful Scheduled with changes by daryl herzmann <akrherz@iastate.edu> and Dele Olajide <dele@4ng.net>

Build result summary

Details

Completed
Queue duration
1 minute
Duration
2 minutes
Labels
None
Revision
5017d0a10e1b91812bed74cdb426f730a108155f
Total tests
427
Successful since
#240 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 5017d0a10e1b91812bed74cdb426f730a108155f Merge pull request #1629 from igniterealtime/fix-issue-OF-2017
Update Jetty to 9.4.28.v20200408
Dele Olajide <dele@4ng.net> Dele Olajide <dele@4ng.net> 2200700b1d08a7b83a2ad91edc32241a0f80d480 Update Jetty to 9.4.28.v20200408
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> e46bca20b638a3c164365e0040662b3568bbc430 Merge pull request #1626 from guusdk/sm-invalid-connection-fixes
Various fixes for Stream Management
Guus der Kinderen Guus der Kinderen 481f555554ab258ebcfc19ed6a6ad5053cd56026 m Adding debug logging
Guus der Kinderen Guus der Kinderen cff87d5620cf27266df7821e36dd14b5984a6284 m OF-2015: Clean up the donor immediately after session resumption.
When Stream Management is used to resume an old session, the session that was used to resume the old session should be cleaned up immediately. Before this fix, the session lingers in a state of being 'detached'. Not only is there no reason for it to linger (it can't be resumed), marking it as 'detached' is semantically wrong: this session never reached a state where it makes sense to resume it later. The changes in this commit clean up the donor session immediately after resuption.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2013Could not obtain issue details from Jira
Unknown Issue TypeOF-2014Could not obtain issue details from Jira
Unknown Issue TypeOF-2015Could not obtain issue details from Jira