Adopt MariaDB project test harness#694
Open
brandonpayton wants to merge 37 commits into
Open
Conversation
This reverts commit 953828e.
Phase B-1 matrix build status —
|
| Package | Arch | Status | Sha |
|---|---|---|---|
| kandelo-sdk | wasm32 | built | 4acc0935 |
| mariadb-test | wasm32 | built | f1ccd75d |
| rootfs | wasm32 | built | c92afe60 |
| shell | wasm32 | built | 16f0839a |
| lamp | wasm32 | built | a7a1c0a9 |
| node-vfs | wasm32 | built | 29cae749 |
| wordpress | wasm32 | built | c43a94fe |
Auto-generated; replaced on each push. Raw data in the publish-status workflow artifact.
…un.26@mqe4ebil' into HEAD
… into HEAD # Conflicts: # docs/mariadb-project-tests.md # scripts/run-browser-mariadb-tests.sh
…b.com:Automattic/kandelo into HEAD
…finery/kad-wisp-28i
…o refinery/kad-wisp-e77
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adopts the MariaDB project test harness work from the PR #3 reference branch into Kandelo, with current Node and browser host validation captured on the
integration/kad-qun-mariadb-testsbranch.Scope included in this integration branch:
mysql-test/main, including Node and browser entry points.docs/mariadb-project-tests.md.Tracking epic:
kad-qun.Reference PR: brandonpayton#3.
MariaDB mysql-test/main final status
Full-suite artifacts now cover all 1183 upstream
mysql-test/maintests on both supported hosts. Node used:Browser used:
LD_LIBRARY_PATH=/tmp/pwdeps/root/usr/lib/x86_64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} MARIADB_BROWSER_RUNNER_RETRIES=3 scripts/run-mariadb-project-tests.sh --host browser --all --chunk-size 10 --timeout-ms 60000test-runs/mariadb-project/kad-qun.4-node-20260613T112749Z/plus focused reruns for chunks 54/55/56/92test-runs/gastown-mariadb-browser-full-pr3/The Node artifact's raw primary-wrapper count of 596 PASS / 27 FAIL / 311 XFAIL / 0 XPASS / 239 SKIP / 1173 TOTAL is superseded by the reconciled total above because chunk 56 hit the known zero-result harness path (
kad-lf9) and chunks 54, 55, 56, and 92 have authoritative focused reruns. The browser artifact already folds its pre-rebase chunks 1-49 and post-rebase resumed chunks 50-119 into one final total.Post-artifact fixes already landed on the integration branch but are not folded into these hard totals without a rerun:
kad-qun.14,kad-qun.16,kad-qun.17, andkad-qun.18.Detailed follow-up inventory is in
docs/mariadb-project-tests.md#failure-inventory-for-follow-up-routing: it lists all 18 Node unexpected failures individually and accounts for the 371 browser FAIL rows by clusters whose counts sum to the hard browser total.Known follow-ups
Remaining tracked follow-ups are intentionally left as narrow beads rather than blocking this PR:
kad-lf9: Node wrapper must fail loudly when a child harness run produces zero result rows.kad-qun.9: browser wrapper should run from resolver-fetched artifacts in a fetch-only worktree.kad-qun.10: browser all-suite runner needs stronger isolation after timeouts, page death, or contaminated MariaDB state.kad-qun.20: Node optimizer/range/subselect/window failures need root-cause classification or timeout/resource-envelope treatment.kad-qun.21: Nodesp_stress_casestill needs isolated memory-envelope classification after the mysql.proc recovery fix.kad-qun.23: browser MariaDB expected-fail classifications need to cover release-build, plugin/event-scheduler, unsupported helper, and SQL-result limitations that currently appear as raw FAIL rows.kad-qun.24: browser VFS fixture coverage needs std_data, timezone, locale, charset, and cross-suite include path gaps fixed or classified.kad-qun.25: browser VFS/storage-state short reads, read-only tables, file descriptor/resource errors, and corrupted table/index rows need focused reproduction and classification.Verification
Latest
kad-qun.22report-update verification on the integration branch:cargo test -p kandelo --target aarch64-apple-darwin --lib: 883 passed, 0 failed.cd host && npx vitest run: 76 files passed, 24 skipped; 634 tests passed, 109 skipped.scripts/run-libc-tests.sh: PASS=302, FAIL=0, XFAIL=20, XPASS=0, FLAKY=2, BUILD=0, TIMEOUT=0, TOTAL=324.scripts/run-posix-tests.sh: PASS=174, FAIL=0, XFAIL=3, XPASS=0, SKIP=2, BUILD=0, UNRESOLVED=0, TIMEOUT=0, TOTAL=179.scripts/dev-shell.sh bash scripts/check-abi-version.sh: passed; snapshot/header/TS bindings in sync and ABI_VERSION consistent. Direct ambientbash scripts/check-abi-version.shused stable Cargo on this host and failed before the canonical dev-shell rerun.This PR is left open for human review. It should not be merged by the final PR handoff agent.