Rebuild working context after a session restart. Reads branch state, recent commits, open PRs, and changed files to produce a "what was I doing" summary.

2026-06-17667

frl-coding-standard

FoundationDB/fdb-record-layer

Coding standards for all Java code in fdb-record-layer. Apply when writing or reviewing any Java code.

2026-06-17667

name	test-runner
description	Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures.

Always apply the using-gradle skill for Gradle task syntax and build commands.

How to run tests

For yaml-tests: ./gradlew :yaml-tests:test (or --tests 'YamlIntegrationTests.<name>').
For embedded-only yaml-tests (faster): ./gradlew :yaml-tests:quickTest.
For mixed-mode yaml-tests locally: ./gradlew :yaml-tests:mixedModeTest.
For JUnit tests in a module: ./gradlew :<module>:test --tests '<fully.qualified.ClassName>'.

Diagnosing failures

Read the full test output — look for the stack trace and the assertion message.
Check if the failure is in a yaml test:
- plan mismatch → the actual query plan changed; edit YamlIntegrationTests.java to add @MaintainYamlTestConfig(YamlTestConfigFilters.CORRECT_EXPECTATIONS) to the test entry, then re-run — the framework will auto-correct the expected plan.
- result mismatch → data or query logic changed; inspect the yamsql file.
Check if the failure is an async issue:
- BlockingInAsyncContextException → something called join()/get() inside a future.
- Timeout → possible deadlock; check for blocking calls in completion lambdas.
Check if FDB connectivity is the issue:
- FDBException or connection refused → FDB is not running or cluster file is wrong.