Getting garbled Appium logs when I am trying to programmatically start Appium on and ios simulator and android device in parallel
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- java
- 领域
- mobile-dev, testing-qa
调研方向
从 startAppiumServer() 开始，重点检查 server.start()，并审查所提供的、配置为并行测试的 TestNG 套件。在列出的 macOS、iOS 和 Android 环境上使用 Appium 1.22.3 重现问题，然后确定四台设备的并行启动是否能够可靠完成，且不会出现日志乱码或执行挂起。
由索引模型根据 Issue 内容生成。
描述
Do I have the most recent component updates?
- I use the most recent available driver/plugin and server versions
Is the component officially supported by the Appium team?
- I have verified the component repository is present under the Appium organization in GitHub
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I am trying to programmatically start Appium server on 2-4 different devices, different/ same platforms in parallel and it isn't working at the moment with a great success rate. Out of the 5 times I ran it, it fails 4 times.
Here are my Appium logs:
[Appium] Welcome to Appium v1.22[
35[[3A5pmp[iAupmp]i9mm] [e3l9cm oNme otno- dAepfpaiulutm sve1r.v2e2r. 3
ar[s3:5
m[[p3p5imu[mA]pm Nionu-md]e[a3u9lmt s erpvoerrt :a r6g3s8:2
7
[Appium] port: 63826
[Appium] Appium REST ht[p 3i5nmt[eArpfpaicue ml]i[t3e9nme rA psptiaurmt eRdE SoTn h0.0.t0t.p0 :i6n3t8e2r7f
ace listener started on 0.0.0.0:63826
[HTTP] --> GET[[3395mm [[T3TP7]mwd/3h9umb/st a[u3s7[-3-9>m
[3[m3 5[[H37TmTGPE]T[39[m3 9[ 9[m3{7}mw3d9/mh
ub[/dsetbautgu]s [[3395mm[
[HTTP][E3N9EmR I[9]0[{3}9[ 3C9allinmg
A[pdpeibuumgD]r i[e3r5.mg[eGtESNtEaRtIuCs]( 3w9imt hC aalrlgisn:g [A]p
piu[mdDerbiuvge] rg3e5tmS[tGaEtNuEsR(I)C ]w[t3h9 ma rRgess:p o[n]d
in[gd etbou gc]l i[n3t5 mw[iGtEhN EdRrIiCv]e[.3g9emt SRteastpuosn(d) irnegs utlot :c l{i"ebnuti lwdi"th: {d"rvievresri.ogne"t:S"t1a.t2u2s.(3)" }r}e
sult: {"build":{"version":"1.22.3"}}
[HTTP] <-- GET /wd/hub/status 200 5 ms - 68
[HTTP][39[m3 5[[90HmT[P3]9[
39m <-- GET /wd/hub/status 200 5 ms - 68
[HTTP]
Asserting whether server started...
Asserting whether server started...
[HTTP] --> GET /wd/hub/status
[3[35m[HTTP] m3H7TmT-P-]>[[3399mm [90m{}393m7
mGE[Td[b3u9gm] [[3375mm/[wGdE/NhEuRbI/Cs]t[t3u9smC3a9lml
ing A[pHpTiTuPm]D[i3v9emr .[e9t0Smt{a}t[s3(9)m
w[idtehb uagr]g s[ 3[5]m
[GE[NERIC]d eCbaulgl]i n[ 3A5pm[pGiEuNmEDrRiIvCe]r.g eRteSstpaotnudsi(n)g wtiot hc lairegns: []
[debug] [GENERIC] Responding to client with driver.getStatus() result: {"build":{"vet rwsiitohn "d:r"iv1e.r2.2g.e3t"S}t}a
tus( 3r5ems[uHlTtT:P ]{"9umi l["3:7{m"<v-e-r sGiEoTn "/:w"d1/.h2u2b.3"}}
/st[t3us5 mH3T9TmP
The logs get stuck here ^^ and rest of the execution doesn't start
Please note that my Appium version is 1.22.3 and I cannot upgrade to >2 since there is a java-client limitation.
Expected Behavior
I want the Appium server to start at least for a parallel run with 4 devices.
Minimal Reproducible Example
This is what my testNG.xml looks like:
`
This is how I am starting the Appium server. It is failing at server.start();
public synchronized void startAppiumServer() throws Exception {
if (Globals.PLATFORM.equalsIgnoreCase("web")) return;
/* Check if a server is already running for this device */
if (!servers.containsKey(udidPerThread.get())) {
int port = getAvailablePort();
AppiumServiceBuilder appiumServiceBuilder = new AppiumServiceBuilder();
appiumServiceBuilder.usingPort(port);
AppiumDriverLocalService server = AppiumDriverLocalService.buildService(appiumServiceBuilder);
server.start();
Assert.assertTrue(server.isRunning());
servers.put(udidPerThread.get(), server);
System.out.println("Appium Server Started successfully for device " + udidPerThread.get() + " on port " + port);
}
currentDevice.set(udidPerThread.get());
}
Environment
- Operating system: MAC Ventura 13.1
- Appium server version (output of
appium --version): 1.22.3 - Node.js version (output of
node --version): v16.13.2 npmversion (output ofnpm --version): 8.6.0- Platform and version under test: ios simulator v16.0, android emulator v11, android real device v13
Link to Appium Logs
No response
Futher Information
No response
- 主要语言
- Java
- 星标
- 1.3k
- 派生
- 755
- 平均合并
- 5 天 14 小时
- 30 天内合并 PR
- 8
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
appium/java-client 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
appium/java-client#2426 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 50/100
appium/java-client#2372 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 30/100
appium/java-client#2368 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 30/100
appium/java-client#2341 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 15/100
appium/java-client#2323 ·
维护者通常 1 天内回复
查看 appium/java-client 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
OpenAPITools/openapi-generator#25014 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
openhab/openhab-core#5847 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 88/100
apache/parquet-java#3820 ·
维护者通常 1 天内回复