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

bug(ci): flaky parallel e2e test due to connection pool timed out #18966

Open
yezizp2012 opened this issue Oct 17, 2024 · 0 comments
Open

bug(ci): flaky parallel e2e test due to connection pool timed out #18966

yezizp2012 opened this issue Oct 17, 2024 · 0 comments
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@yezizp2012
Copy link
Contributor

Describe the bug

end-to-end test (parallel) uses Sqlite as meta backend with only one connection in the pool. It sometimes fails due to encountering Connection pool timed out error. https://buildkite.com/risingwavelabs/pull-request/builds/60205#0192989c-5558-4b07-8d13-7e67b46fa61a

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

@yezizp2012 yezizp2012 added the type/bug Something isn't working label Oct 17, 2024
@yezizp2012 yezizp2012 self-assigned this Oct 17, 2024
@github-actions github-actions bot added this to the release-2.2 milestone Oct 17, 2024
@yezizp2012 yezizp2012 changed the title bug: flaky parallel e2e test due to connection pool timed out bug(ci): flaky parallel e2e test due to connection pool timed out Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant