#920
  • Created on
    2011-06-13 12:14
  • Reported by
    viktorklang
  • Status
    Invalid
  • Priority
    Normal (3)
  • Assigned to
    viktorklang
  • Milestone
    2.0-M2
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

REMOTE: Write a ton of remote tests

Resurrect the old remoting tests from Git history.
  • Only the ones still valid. Not the client managed tests, but some of the server managed.
  • Complete with more remote tests? Evaluate if that is needed.

Cases:
  • Fire-forget message to non-existing actor on remote node followed by a sendRequestReplyFuture to an existing, working actor, the first should fail and the second succeed
User picture
  on 2011-06-16 12:58 *
By Jonas Bonér
Description changed from Cases: Fire-forget message... to Resurrect the old remoting ...
User picture
  on 2011-06-16 12:58 *
By Jonas Bonér
Assigned to set to viktorklang
User picture
  on 2011-06-25 17:41 *
By Jonas Bonér
Component changed from None to cluster
Updating tickets (#769, #774, #875, #889, #917, #920, #928, #929, #930, #931, #932, #933, #934, #935, #936, #938, #939, #940, #941, #942, #943, #944, #951, #958, #959, #960, #962, #630, #870, #891, #895)
User picture
  on 2011-07-06 13:07 *
By Jonas Bonér
Do we really need to focus on writing a lot of these low level remoting tests now that we are shoveling in massive amounts of cluster test, which implicitly tests the remoting. Not sure. Let's discuss before you start with this.
User picture
  on 2011-07-19 08:46 *
By pveentjer
What are we going to do with this issue? Mark it is a duplicate/invalid since it is solved by other means?
User picture
  on 2011-07-19 11:09 *
By viktorklang
I think we need tests for the remoting, atleast to not have to debug BOTH the clustering AND the remoting when there's a problem.
User picture
  on 2011-10-07 17:15 *
By viktorklang
Summary changed from Write a ton of remote tests to REMOTE: Write a ton of remote tests
User picture
  on 2011-12-17 22:18 *
By viktorklang
Milestone changed from 2.0 to 2.0-M2
Updating tickets (#1165, #1263, #1264, #861, #875, #920, #950, #1037, #1049, #1087, #1105, #1106, #1162, #1166, #1167, #1173, #1236, #1255, #1272, #1292, #1293, #1322, #1325, #1364, #1384, #1385, #1390, #1403, #1408, #1423, #1426, #1428, #1493, #1494, #1538, #998, #1085)
User picture
  on 2011-12-18 00:10 *
By viktorklang
Status changed from New to Invalid
This will be done as a part of doing the remote supervision, remote deathwatch, etc.