File: emulator-wait-for-ready.sh

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 1,998,520 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (30 lines) | stat: -rwxr-xr-x 1,207 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
#!/usr/bin/env bash
#===----------------------------------------------------------------------===##
#
# Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
# See https://llvm.org/LICENSE.txt for license information.
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
#
#===----------------------------------------------------------------------===##

set -ex

# Time to wait in seconds. The emulator ought to start in 5-15 seconds or so,
# so add a safety factor in case something takes longer in CI.
TIMEOUT=${1-300}

# This syntax (using an IP address of 127.0.0.1 rather than localhost) seems to
# prevent the adb client from ever spawning an adb host server.
export ADB_SERVER_SOCKET=tcp:127.0.0.1:5037

# Invoke nc first to ensure that something is listening to port 5037. Otherwise,
# invoking adb might fork an adb server.
#
# TODO: Consider waiting for `adb shell getprop dev.bootcomplete 2>/dev/null
# | grep 1 >/dev/null` as well. It adds ~4 seconds to 21-def-x86 and ~15 seconds
# to 33-goog-x86_64 and doesn't seem to be necessary for running libc++ tests.
timeout ${TIMEOUT} bash -c '
until (nc -z localhost 5037 && adb wait-for-device); do
    sleep 0.5
done
'