You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "jrudolph (via GitHub)" <gi...@apache.org> on 2023/02/27 14:39:13 UTC

[GitHub] [incubator-pekko] jrudolph commented on issue #139: try to fix the multi-node CI build

jrudolph commented on issue #139:
URL: https://github.com/apache/incubator-pekko/issues/139#issuecomment-1446448063

   We shouldn't make this a requirement for 1.0.0.
   
   The multi-node tests mean that tests that are run as multi-jvm tests in the regular build are instead run distributed over multiple machines / VMs / containers to cover a more diverse set of working environments. The idea is that some race conditions might only turn up under more realistic environments than running on a single machine over localhost networking.
   
   Since we will not change functionality for 1.0.0, there is no reason to expect any additional failures to turn up that would only show in multi-node tests (the very same tests are still run as multi-jvm tests as part of nightly builds).
   
   They become more important when we start changing functionality and want to ensure changes that might change non-deterministic behavior are stable under a more diverse set of working conditions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org