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

qe: Allow to run query engine test suite against wasm engines #4467

Merged
merged 10 commits into from
Nov 22, 2023

Conversation

SevInf
Copy link
Contributor

@SevInf SevInf commented Nov 20, 2023

Intoroduces new environment variable/test config option,
EXTERNAL_TEST_EXECUTOR_ENGINE that can be either NAPI (default) or
WASM that affects which engine external test executor will start with.

Adds a bunch of additional test configs for driver adapters that
duplicate existing ones, but run against WASM engine.

Close prisma/team-orm#551

@SevInf SevInf requested a review from a team as a code owner November 20, 2023 11:06
@SevInf SevInf requested review from jkomyno and Weakky and removed request for a team November 20, 2023 11:06
@SevInf SevInf added this to the 5.7.0 milestone Nov 20, 2023
@SevInf
Copy link
Contributor Author

SevInf commented Nov 20, 2023

Should wasm test run be added to GH Actions now, even though it fails for pretty much every unskipped test? Or should we wait until vertical slice/functioning WASM engine is in main?

@SevInf SevInf marked this pull request as draft November 20, 2023 11:15
Copy link

codspeed-hq bot commented Nov 20, 2023

CodSpeed Performance Report

Merging #4467 will not alter performance

Comparing feat/wasm-test-executor (4fc6b33) with main (63a4fd9)

Summary

✅ 11 untouched benchmarks

@SevInf SevInf marked this pull request as ready for review November 20, 2023 13:58
@SevInf
Copy link
Contributor Author

SevInf commented Nov 20, 2023

Should wasm test run be added to GH Actions now, even though it fails for pretty much every unskipped test? Or should we wait until vertical slice/functioning WASM engine is in main?

Added them to the workflow, but commented out until we have an actual engine.

@SevInf SevInf requested review from miguelff and removed request for jkomyno November 20, 2023 15:35
Copy link
Contributor

@miguelff miguelff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left non-blocking, but desirable feedback for simplifying a bit the runner configuration.

Intoroduces new environment variable/test config option,
`EXTERNAL_TEST_EXECUTOR_ENGINE` that can be either `NAPI` (default) or
`WASM` that affects which engine external test executor will start with.

Adds a bunch of additional test configs for driver adapters that
duplicate existing ones, but run against WASM engine.

Close prisma/team-orm#551
Specify engine option in `external_test_executor`
@SevInf SevInf merged commit 2c867f4 into main Nov 22, 2023
54 of 55 checks passed
@SevInf SevInf deleted the feat/wasm-test-executor branch November 22, 2023 10:07
@miguelff
Copy link
Contributor

Thank you for addressing the feedback!

miguelff added a commit that referenced this pull request Nov 22, 2023
…ests

* origin/main:
  qe: Allow to run query engine test suite against wasm engines (#4467)
  query-engine-wasm: Fix build & ensure it stays fixed (#4488)
  feat(driver-adapters): enable Wasm on `request-handlers` (#4455)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants