From 1055918c310be7b5b472cae7ccb102e415fb3d7d Mon Sep 17 00:00:00 2001
From: Sylvestre Ledru <sylvestre@debian.org>
Date: Sun, 30 Apr 2023 16:58:29 +0200
Subject: [PATCH] Document why we can't use nextest for now

---
 util/android-commands.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/util/android-commands.sh b/util/android-commands.sh
index d958215e5..9f1d28db8 100755
--- a/util/android-commands.sh
+++ b/util/android-commands.sh
@@ -4,7 +4,7 @@
 # There are three shells: the host's, adb, and termux. Only adb lets us run
 # commands directly on the emulated device, only termux provides a GNU
 # environment on the emulated device (to e.g. run cargo). So we use adb to
-# launch termux, then to send keystrokes to it while it's running.
+# launch termux, then to send keystrokes to it while it's ruMbdfhnRrVnning.
 # This means that the commands sent to termux are first parsed as arguments in
 # this shell, then as arguments in the adb shell, before finally being used as
 # text inputs to the app. Hence, the "'wrapping'" on those commands.
@@ -210,7 +210,7 @@ snapshot() {
     # We need to install nextest via cargo currently, since there is no pre-built binary for android x86
     command="'\
 export CARGO_TERM_COLOR=always; \
-#cargo install cargo-nextest; \
+# build fails for now (https://github.com/nextest-rs/nextest/issues/862): cargo install cargo-nextest; \
 echo \$? > $probe'"
     run_termux_command "$command" "$probe"
     return_code=$?