Skip to content

Commit cdd7dcb

Browse files
committed
doc(test): suggest --no-build in conjunction with --ab
When running A/B tests, this part of the documentation explicitly builds firecracker from two revisions. However, after that it will _still_ build Firecracker from HEAD _again_, even though this third compilation of firecracker is not needed: The A/B test will only ever use the precompiled binaries. Fix this by passing --no-build in the example Signed-off-by: Patrick Roy <[email protected]>
1 parent af73ec7 commit cdd7dcb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

tests/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ branch and the `HEAD` of your current branch, run
198198
```sh
199199
tools/devtool -y build --rev main --release
200200
tools/devtool -y build --rev HEAD --release
201-
tools/devtool -y test --ab -- run build/main build/HEAD --test integration_tests/performance/test_boottime.py::test_boottime
201+
tools/devtool -y test --no-build --ab -- run build/main build/HEAD --test integration_tests/performance/test_boottime.py::test_boottime
202202
```
203203

204204
#### How to Write an A/B-Compatible Test and Common Pitfalls

0 commit comments

Comments
 (0)