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

build: run socket test with linux-aio reactor backend #2317

Closed

Conversation

tchaikov
Copy link
Contributor

@tchaikov tchaikov commented Jul 1, 2024

to workaround #2302, before it is fixed.

Refs #2302

to workaround scylladb#2302, before it is fixed.

Refs scylladb#2302

Signed-off-by: Kefu Chai <[email protected]>
@tchaikov
Copy link
Contributor Author

tchaikov commented Jul 1, 2024

@xemul hi Pavel, could you help review this change?

@xemul
Copy link
Contributor

xemul commented Jul 1, 2024

How is backend selected when it's run on CI? Automatically by seastar itself, as it it would select it for any other application?

@tchaikov
Copy link
Contributor Author

tchaikov commented Jul 1, 2024

How is backend selected when it's run on CI? Automatically by seastar itself, as it it would select it for any other application?

@xemul yeah, when running on CI, tests select the seastar backend automatically if we don't pick one for them. i think that's also why, all of a sudden, the tests are failing after switching to the new image. see #2316

@xemul xemul closed this in 4c7a802 Jul 1, 2024
@tchaikov tchaikov deleted the test-socket-with-linux-aio branch July 1, 2024 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants