Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failure in wasm_identity_test.WasmBasicIdentityTest.verify_materialized_topics_test #4038

Closed
ajfabbri opened this issue Mar 18, 2022 · 2 comments
Assignees
Labels
area/wasm WASM Data Transforms ci-failure kind/bug Something isn't working

Comments

@ajfabbri
Copy link
Contributor

CI failure here.


--------------------------------------------------------------------------------
--
  | test_id:    rptest.tests.wasm_identity_test.WasmBasicIdentityTest.verify_materialized_topics_test
  | status:     FAIL
  | run time:   1 minute 28.725 seconds
  |  
  |  
  | Exception('Consumed 7108 expected 10240 output records')
  | Traceback (most recent call last):
  | File "/usr/local/lib/python3.9/dist-packages/ducktape/tests/runner_client.py", line 135, in run
  | data = self.run_test()
  | File "/usr/local/lib/python3.9/dist-packages/ducktape/tests/runner_client.py", line 215, in run_test
  | return self.test_context.function(self.test)
  | File "/root/tests/rptest/services/cluster.py", line 35, in wrapped
  | r = f(self, *args, **kwargs)
  | File "/root/tests/rptest/tests/wasm_identity_test.py", line 54, in verify_materialized_topics_test
  | self.verify_results(materialized_result_set_compare)
  | File "/root/tests/rptest/wasm/wasm_test.py", line 282, in verify_results
  | input_results, output_results = self.wait_on_results()
  | File "/root/tests/rptest/wasm/wasm_test.py", line 214, in wait_on_results
  | raise Exception(
  | Exception: Consumed 7108 expected 10240 output records
  |  
  | --------------------------------------------------------------------------------

@ajfabbri ajfabbri added kind/bug Something isn't working area/wasm WASM Data Transforms ci-failure labels Mar 18, 2022
@graphcareful
Copy link
Contributor

Looks like this is the EADDR port already in use issue again:

2022-03-17T05:56:03.152Z [service] info: Starting redpanda wasm service...
2022-03-17T05:56:03.154Z [service] info: Reading from config file: /etc/redpanda/redpanda.yaml
2022-03-17T05:56:03.157Z [service] info: Starting redpanda wasm service on port: 43189
Server listen error:  Error: listen EADDRINUSE: address already in use :::43189
    at Server.setupListenHandle [as _listen2] (net.js:1309:16)
    at listenInCluster (net.js:1357:12)
    at Server.listen (net.js:1445:7)
    at t.e.listen (/var/lib/buildkite-agent/builds/buildkite-arm64-builders-i-0057186edb2bab731-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/opt/wasm/main.js:1:294554)
    at /var/lib/buildkite-agent/builds/buildkite-arm64-builders-i-0057186edb2bab731-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/opt/wasm/main.js:1:300787 {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 43189
}

@graphcareful
Copy link
Contributor

Closing as this is a duplicate of #4023

graphcareful pushed a commit to graphcareful/redpanda that referenced this issue May 4, 2022
- Killing the wasm_engine should be a part of the clean_node() routine

- Fixes: redpanda-data#4038
vbotbuildovich pushed a commit to vbotbuildovich/redpanda that referenced this issue Jun 3, 2022
- Killing the wasm_engine should be a part of the clean_node() routine

- Fixes: redpanda-data#4038

(cherry picked from commit e70b777)
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/wasm WASM Data Transforms ci-failure kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants