-
Notifications
You must be signed in to change notification settings - Fork 78
Closed
Labels
failed 💥Failed tickets are CI or benchmarking failures, should be investigated as soon as possibleFailed tickets are CI or benchmarking failures, should be investigated as soon as possiblet:cluster:membershipt:cluster:singleton
Milestone
Description
Still issues with the joining on CI, it's pretty slow.
withleaderchange.txt
00:04:20.354 /code/Tests/ActorSingletonPluginTests/ActorSingletonPluginClusteredTests.swift:130: error: ActorSingletonPluginClusteredTests.test_singletonByClusterLeadership_withLeaderChange : failed -
00:04:20.354 try shouldNotThrow {
00:04:20.354 ^~~~~~~~~~~~~~~
00:04:20.354 error: Unexpected throw captured
00:04:20.354 try self.ensureNodes(.up, on: second, nodes: second.cluster.node, third.cluster.node, fourth.cluster.node)
00:04:20.354 ^~~~~~~~~~~
00:04:20.354 error: No result within 20s for block at /code/Tests/ActorSingletonPluginTests/ActorSingletonPluginClusteredTests.swift:222. Queried 191 times, within 20s. Last error:
00:04:20.354 try self.ensureNodes(.up, on: second, nodes: second.cluster.node, third.cluster.node, fourth.cluster.node)
00:04:20.354 ^~~~~~
00:04:20.354 error: Expected sact://fourth:593671297@127.0.0.1:7444 on sact://second:2163397932@127.0.0.1:8222 to be seen as: [up], but was [joining]
00:04:20.355 <EXPR>:0: error: ActorSingletonPluginClusteredTests.test_singletonByClusterLeadership_withLeaderChange : threw error "unexpectedErrorWasThrown"
00:04:20.364 ------------------------------------- ActorSystem(first, sact://first@127.0.0.1:7111) ------------------------------------------------
00:04:20.364 Captured log [first][2020-06-18 4:7:07.7990] [ActorSystem.swift:306] [info] Actor System [first] initialized.
00:04:20.364 // metadata:
00:04:20.364 // "actor/node": sact://first@127.0.0.1:7111
00:04:20.364 // "actor/nodeName": first
Metadata
Metadata
Assignees
Labels
failed 💥Failed tickets are CI or benchmarking failures, should be investigated as soon as possibleFailed tickets are CI or benchmarking failures, should be investigated as soon as possiblet:cluster:membershipt:cluster:singleton