#!watchflakes
post <- builder ~ `android-.*` && log ~ `adb: error: connect failed: closed`
adb push /workdir/tmp/go_android_exec-cmd-go-3350234747 /data/local/tmp/go_android_exec/goroot/bin/go
adb: error: connect failed: closed
go_android_exec: exit status 1
FAIL golang.org/x/benchmarks/cmd/bent 27.763s
greplogs -l -e 'adb: error: connect failed: closed'
2022-05-04T20:30:17-39d8c21-e1e056f/android-amd64-emu
2022-03-18T06:03:39-0e9765c-3d19e8d/android-386-emu
2021-10-18T21:21:54-ffe10e5-6c0daa7/android-amd64-emu
2021-03-26T06:03:03-6b15177-9c7463c/android-amd64-emu
(注意:@golang/android)
4条答案
按热度按时间f4t66c6m1#
由于这仅影响
-emu
构建器,我想知道这是否是模拟器本身的缺陷。也许构建器镜像应该使用更新的模拟器进行更新,或者这个bug应该被升级到Android模拟器开发者那里?
ndasle7k2#
FWIW,看起来我们的
go_android_exec
Package 器明确地等待模拟器启动:https://cs.opensource.google/go/go/+/master:misc/android/go_android_exec.go;l=94-99;drc=98f3d7fecbb8a9074f5f4ffc50bb016e194940b7
f2uvfpb93#
https://go.dev/cl/412174提到了这个问题:
dashboard: add known issues for android-*-emu
kxkpmulp4#
https://go.dev/cl/465156提到了这个问题:
dashboard: unmark known-issues with low failure rates