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

[v22.1.x] Temporarily disable coproc on ci #5022

Merged

Conversation

vbotbuildovich
Copy link
Collaborator

Backport from pull request: #4557.

Rob Blafford added 5 commits June 3, 2022 18:52
- Many obscure wasm test failures can be traced to a root issue of a
previous wasm engine still existing and listening on port 43189.

- When this occurs only some of the deployed wasm engines will be
started and the test output will confusingly show not enough data was
read from redpanda.

(cherry picked from commit aa7cdd8)
- Killing the wasm_engine should be a part of the clean_node() routine

- Fixes: redpanda-data#4038

(cherry picked from commit e70b777)
- These tests all attempt to remove a materialized topic while the
coprocessor is still running.

- However due to the initial design of the system, coproc will attempt
to recreate the topic and re-populate it up until the previous high
watermark. If this was not performed there would be an inconsistency
between the coprocessors defined metadata and random commands sent to the
cluster by the user.

- The tests have been beneficial in understanding that this type of
concurrent delete can occur without any crashes.

- If a user wants to truly delete a materialized topic he/she must
shutdown the coprocessor first.

- Fixes: redpanda-data#3384

(cherry picked from commit 964bb41)
- Disabling temporarily due to a difficult to debug memory leak detected
by ASAN on rare occassions.

- Marking issue for tracking here: redpanda-data#4053

(cherry picked from commit 811ce07)
@vbotbuildovich vbotbuildovich added this to the v22.1.x-next milestone Jun 3, 2022
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jun 3, 2022
@ajfabbri ajfabbri modified the milestones: v22.1.x-next, v22.1.4 Jun 3, 2022
@ajfabbri ajfabbri marked this pull request as ready for review June 3, 2022 18:53
@ajfabbri
Copy link
Contributor

ajfabbri commented Jun 3, 2022

Once this CI is clean I'll merge and restart runs for affected v22.1.x backports.

@ajfabbri ajfabbri merged commit 65b310a into redpanda-data:v22.1.x Jun 3, 2022
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants