Browse Source
`EmbeddedConnectCluster` has the ability to mask system exits to avoid killing the jvm. It appears that the default was intended to be `true`, but is actually `false`. The `maskExitProcedures` method on `EmbeddedConnectCluster.Builder` documents the parameter as: ``` * @param mask if false, exit and halt procedures remain unchanged; true is the default. ``` Because this is not enabled by default as intended, we are seeing some build failures which exit abruptly: ``` 17:29:11 Execution failed for task ':connect:runtime:integrationTest'. 17:29:11 > Process 'Gradle Test Executor 25' finished with non-zero exit value 1 ``` The culprit often appears to be `ExampleConnectIntegrationTest`, which indeed does not override the default value of `maskExitProcedures`. Reviewers: Ewen Cheslack-Postava <me@ewencp.org>pull/7036/head
Jason Gustafson
5 years ago
committed by
GitHub
1 changed files with 1 additions and 1 deletions
Loading…
Reference in new issue