These are chat archives for atomix/atomix

29th
Apr 2018
Johno Crawford
@johnou
Apr 29 2018 09:33
@kuujo looks like the timeout change is causing "regressions" in the CI tests
java.util.concurrent.CompletionException: java.util.concurrent.TimeoutException: Request timed out in 126 milliseconds
Caused by: java.util.concurrent.TimeoutException: Request timed out in 126 milliseconds
Johno Crawford
@johnou
Apr 29 2018 11:10
@kuujo I see why CI is failing now, it's mixing ipv4 and ipv6 interfaces
10:45:10.781 [atomix-cluster-heartbeat-receiver] INFO i.a.c.i.DefaultClusterMembershipService - 184 - Node activated: StatefulMember{id=3, type=PERSISTENT, address=ip6-localhost:5003}
10:45:10.782 [atomix-cluster-heartbeat-receiver] INFO i.a.c.i.DefaultClusterMembershipService - 90 - Node activated: StatefulMember{id=3, type=PERSISTENT, address=localhost:5003}
which in turn is resulting in failures like
java.util.concurrent.CompletionException: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:5088
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:5088
Caused by: io.netty.channel.unix.Errors$NativeConnectException: syscall:getsockopt(..) failed: Connection refused
Jordan Halterman
@kuujo
Apr 29 2018 20:12
interesting
good find
I couldn’t figure that out either
Trusty is defined in the travis config
So ipv6 on loop back
Jordan Halterman
@kuujo
Apr 29 2018 21:00
indeed
Johno Crawford
@johnou
Apr 29 2018 21:02
Could try Ubuntu Precise
Or does that cost money
Jordan Halterman
@kuujo
Apr 29 2018 21:03
¯_(ツ)_/¯
Johno Crawford
@johnou
Apr 29 2018 21:03
Or
Run the ci tests with just the port
So it binds on the first nic
Java ipv4 preferred might work too
Just spit balling ideas
Jordan Halterman
@kuujo
Apr 29 2018 21:07
using just the port seems like a good solution
Johno Crawford
@johnou
Apr 29 2018 21:09
Ohhh
Cluster not shut down
In the new test
Jordan Halterman
@kuujo
Apr 29 2018 21:11
sweet
Johno Crawford
@johnou
Apr 29 2018 21:16
i'll fix it
Johno Crawford
@johnou
Apr 29 2018 21:30
AtomixClusterTest isn't even starting a cluster
or
Jordan Halterman
@kuujo
Apr 29 2018 21:31
it is
it starts 3 of them
err 3 nodes
Johno Crawford
@johnou
Apr 29 2018 21:32
yeah just extremely fast
[ERROR] Tests run: 7, Failures: 1, Errors: 5, Skipped: 0, Time elapsed: 29.446 s <<< FAILURE! - in io.atomix.core.AtomixTest
[ERROR] testDiscoverData(io.atomix.core.AtomixTest) Time elapsed: 0.176 s <<< ERROR!
java.util.concurrent.CompletionException: io.atomix.utils.config.ConfigurationException: Duplicate system group detected
Caused by: io.atomix.utils.config.ConfigurationException: Duplicate system group detected
from master ci run
tests running in parallel? not shutting down atomix instances?
Jordan Halterman
@kuujo
Apr 29 2018 21:36
seems like one of those
I think that’s the first test run in that class so gotta be stuff hanging around from earlier tests
Jordan Halterman
@kuujo
Apr 29 2018 21:46
I’ve gotten less than 3 of the 14 sections of the website done :-(
Johno Crawford
@johnou
Apr 29 2018 21:52
can you copy paste anything from the old site?