kokoro: Remove mention of manifest.xml.

We are no longer pinned to a specific version since
https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2840057

BUG=None
TEST=read it.

Change-Id: I23750d5404f776c21de4ba11e17b5704751b247a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2902915
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Commit-Queue: Junichi Uekawa <uekawa@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Auto-Submit: Junichi Uekawa <uekawa@chromium.org>
This commit is contained in:
Junichi Uekawa 2021-05-18 17:17:06 +09:00 committed by Commit Bot
parent 2f4a80f366
commit dc2f396277

View file

@ -96,11 +96,9 @@ crosvm-aarch64$ cargo test -p kvm_sys
### Reproducing Kokoro locally
Kokoro uses the same builders and the same `run_tests` script to run tests.
However, to keep the build stable, it syncs the chromiumos checkout to the fixed
manifest found at `./ci/kokoro/manifest.xml`.
To run tests using the same manifest, as well as the same build process that
Kokoro uses, you can run: `./ci/kokoro/simulate_all`.
To sync to ToT, as well as the same build process that Kokoro uses, you can run:
`./ci/kokoro/simulate_all`.
## Implementation Overview