[Hotfix] fixed update-listener not working #338
build-test.yml
on: pull_request
Matrix: build
Matrix: test
Matrix: e2e-test
Annotations
14 errors, 11 warnings, and 6 notices
[integrations] › integrations/summarizer.spec.ts:69:5 › 测试 @cf/qwen/qwen1.5-1.8b-chat 模型的AI总结结果:
tests/integrations/summarizer.spec.ts#L56
1) [integrations] › integrations/summarizer.spec.ts:69:5 › 测试 @cf/qwen/qwen1.5-1.8b-chat 模型的AI总结结果
Error: expect(received).toContain(expected) // indexOf
Expected substring: "麦当劳"
Received string: "互动内容:
1. 观众询问了日本vtuber直播的内容,包括她今天吃了什么、新产品的热门程度、久违的出门情况、漫展的参与情况、购买的物品种类和花费情况以及回家途中看到的蟑螂尸体对她的影响。
2. 主播表示,虽然之前看到很多人可能会感到社恐,但这次参加漫展并没有,反而意外地没有。她认为,随着年龄的增长,自己变得更加独立和自信,能够面对和处理各种情况。
3. 观众询问了主播今天出门的原因,她表示平时都是宅在家里的,但这次是因为最近新推出的热门产品,所以决定出门看看。她还提到,这次出门让她有机会接触到更多的人和事物,也让她感到更加开阔和自由。
4. 主播分享了自己在漫展上购买的物品,包括插画、手办和周边等,她表示这些物品虽然花费了大笔金钱,但她觉得值得,因为这些物品能够让她感受到动漫文化的魅力和乐趣。
5. 观众对主播的购物行为表示了赞赏,认为花出去的钱物有所值,而且她也表示,这次经历让她的心情得到了改善,因为看到了蟑螂的尸体,这让她的心情受到了打击,但通过和主播的交谈,她的心情得到了恢复。
6. 主播感谢观众的陪伴,表示下次再见,同时也向观众道别。"
54 |
55 | if (!trash) {
> 56 | maybe(res).toContain('麦当劳')
| ^
57 | maybe(res).toContain('漫展')
58 | maybe(res).toContain('蟑螂')
59 | }
at /home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/integrations/summarizer.spec.ts:56:24
|
[theme-setup] › theme.setup.ts:5:6 › 預先搜索大海報房間:
tests/helpers/bilibili-api.ts#L55
1) [theme-setup] › theme.setup.ts:5:6 › 預先搜索大海報房間 ────────────────────────────────────────────────
Error: apiRequestContext.get: socket hang up
Call log:
- → GET https://api.live.bilibili.com/room/v1/Room/room_init?id=22901614
- user-agent: Playwright/1.48.0 (x64; ubuntu 22.04) node/20.18 CI/1
- accept: */*
- accept-encoding: gzip,deflate,br
- cookie: LIVE_BUVID=AUTO1717300317572233
at helpers/bilibili-api.ts:55
53 | const release = await this.mutex.acquire()
54 | try {
> 55 | const res = await this.context.get(path)
| ^
56 | if (!res.ok()) throw new Error(`获取bilibili API失败:${res.statusText()}`)
57 | return await res.json()
58 | } finally {
at BilbiliApi.fetch (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/bilibili-api.ts:55:44)
at BilbiliApi.getRoomStatus (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/bilibili-api.ts:70:22)
at BilibiliPage.isStatus (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/bilibili-page.ts:65:16)
at RoomTypeFinder.getRoomType (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/room-finder.ts:51:17)
at RoomTypeFinder.findRoomType (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/room-finder.ts:97:30)
at /home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/theme.setup.ts:16:18
|
[chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕:
tests/content.spec.ts#L1
1) [chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕 ──────────────────────────────────
Test timeout of 360000ms exceeded.
|
[chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕:
tests/content.spec.ts#L317
1) [chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕 ──────────────────────────────────
Error: locator.dblclick: Target page, context or browser has been closed
Call log:
- waiting for locator('#live-player')
- locator resolved to <div id="live-player" class="live-player-mounter h-100">…</div>
- attempting dblclick action
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <img alt="Scan me!" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKAAAACgCAYAAACLz2ctAAAAAXNSR0IArs4c6QAAEW1JREFUeF7tne162zoMg7v7v+idJ026KjIFvKSU063l/q2R9UGCIEg7zq+3t7ffb5v/fv++T/Hr16/LTB+frT7/uGAc9/G3j/ncHGr9cUPzuMq8ap+RGaPx0bjIdtn53Bx0L8r+82eb0Hm7IaYBaIJndGwD8A45B3YKzD8ArEbHbaEsA0VRlJ2jwrbqjBHb7jCVckDW1uNc1PEkUKIM4K6L/JQ9z3iGBuDDuw3Au3z6cgC6CFMRQFlpRzMSFluxD2FZ5wDKbM4Wq3midL/zN8ri1K90nNKvkgEbgFdJ7GwSFVINwCsEI/BeUrAzdjYClM5wTnKfz0es7H2eoxnws5NBfU0yy6pWOArASCxTAO4cVoEmu372DGNF6ES9CpAdIU8rzoip…/> from <div class="bili-mini-mask fade-leave-active fade-leave-to">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <img alt="Scan me!" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKAAAACgCAYAAACLz2ctAAAAAXNSR0IArs4c6QAAEW1JREFUeF7tne162zoMg7v7v+idJ026KjIFvKSU063l/q2R9UGCIEg7zq+3t7ffb5v/fv++T/Hr16/LTB+frT7/uGAc9/G3j/ncHGr9cUPzuMq8ap+RGaPx0bjIdtn53Bx0L8r+82eb0Hm7IaYBaIJndGwD8A45B3YKzD8ArEbHbaEsA0VRlJ2jwrbqjBHb7jCVckDW1uNc1PEkUKIM4K6L/JQ9z3iGBuDDuw3Au3z6cgC6CFMRQFlpRzMSFluxD2FZ5wDKbM4Wq3midL/zN8ri1K90nNKvkgEbgFdJ7GwSFVINwCsEI/BeUrAzdjYClM5wTnKfz0es7H2eoxnws5NBfU0yy6pWOArASCxTAO4cVoEmu372DGNF6ES9CpAdIU8rzoip…/> from <div class="bili-mini-mask fade-leave-active fade-leave-to">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <img alt="Scan me!" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKAAAACgCAYAAACLz2ctAAAAAXNSR0IArs4c6QAAEW1JREFUeF7tne162zoMg7v7v+idJ026KjIFvKSU063l/q2R9UGCIEg7zq+3t7ffb5v/fv++T/Hr16/LTB+frT7/uGAc9/G3j/ncHGr9cUPzuMq8ap+RGaPx0bjIdtn53Bx0L8r+82eb0Hm7IaYBaIJndGwD8A45B3YKzD8ArEbHbaEsA0VRlJ2jwrbqjBHb7jCVckDW1uNc1PEkUKIM4K6L/JQ9z3iGBuDDuw3Au3z6cgC6CFMRQFlpRzMSFluxD2FZ5wDKbM4Wq3midL/zN8ri1K90nNKvkgEbgFdJ7GwSFVINwCsEI/BeUrAzdjYClM5wTnKfz0es7H2eoxnws5NBfU0yy6pWOArASCxTAO4cVoEmu372DGNF6ES9CpAdIU8rzoip…/> from <div class="bili-mini-mask fade-leave-active fade-leave-to">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #3
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #5
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #6
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled
|
[chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕:
tests/content.spec.ts#L1
1) [chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕 ──────────────────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 360000ms exceeded.
|
[chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕:
tests/content.spec.ts#L317
1) [chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕 ──────────────────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.dblclick: Target page, context or browser has been closed
Call log:
- waiting for locator('#live-player')
- locator resolved to <div id="live-player" class="live-player-mounter h-100">…</div>
- attempting dblclick action
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #3
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div data-v-7a0dfec7="" class="qrcode-loading">…</div> from <div class="bili-mini-mask fade-enter-active fade-enter-to">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <img alt="Scan me!" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKAAAACgCAYAAACLz2ctAAAAAXNSR0IArs4c6QAAEY9JREFUeF7tndt22zoMRJP//+ie5cquKQqc2SCprOQEfWtE8wIMBgNIlj8/Pj7+fCz++/PnmOLz8/My0+tae739W/8BOkf7ObW+Ghftzc0b7T3a82seddZ2LTUH3ZObg/rptd5rvuyZM3B6IKYAaIKndWzWGQVADcd/AKSG6qPj8X8aWSqiom0qNpwBBWFeZwfHMiT63RpqjsiGLmtkGM0FWOTr7Hna/RYAn96hwVEAvMqtrQB0BlYRMMNKSitlI9uxD9GKjgHUGlRTEoYbZZas/SOfZDOLm4PYdXSeCwMWAK+S2NkkCiIaPKoI2w02IpVmwFYADKrviGWIoYoB352MlQCg9t/KgFFbYaUNsyJ4CQNRyeDOoAoDl5az7RparGXnzbaS…/> from <div class="bili-mini-mask fade-leave-active fade-leave-to">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #5
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #6
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #7
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
- retrying dblclick action, attempt #8
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class=""></div> from <div id="jimaku-area">…</div> subtree intercepts pointer events
|
[chrome] › content.spec.ts:157:5 › 測試添加到黑名单按鈕:
tests/content.spec.ts#L1
1) [chrome] › content.spec.ts:157:5 › 測試添加到黑名单按鈕 ─────────────────────────────────────────────────
Test timeout of 120000ms exceeded.
|
[chrome] › content.spec.ts:157:5 › 測試添加到黑名单按鈕:
tests/content.spec.ts#L162
1) [chrome] › content.spec.ts:157:5 › 測試添加到黑名单按鈕 ─────────────────────────────────────────────────
Error: locator.click: Target page, context or browser has been closed
Call log:
- waiting for getByText('添加到黑名单')
- locator resolved to <button type="button" class="align-middle select-none font-sans font-bold text-center uppercase transition-all disabled:opacity-50 disabled:shadow-none disabled:pointer-events-none py-3.5 px-7 rounded-lg border border-gray-900 text-gray-900 hover:opacity-75 focus:ring focus:ring-gray-300 active:opacity-[0.85] gap-3 text-lg">添加到黑名单</button>
- attempting click action
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="bili-mini-mask">…</div> from <body class="supportWebp risk-captcha-adapt-pc risk-captcha-adapt">…</body> subtree intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="bili-mini-mask">…</div> from <body class="supportWebp risk-captcha-adapt-pc risk-captcha-adapt">…</body> subtree intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="bili-mini-mask fade-leave-active fade-leave-to">…</div> from <body class="supportWebp risk-captcha-adapt-pc risk-captcha-adapt">…</body> subtree intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is not stable
- retrying click action, attempt #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #5
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #6
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #7
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #8
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #9
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #10
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #11
- waiting 500ms
- waiting for element to be visible, enabled a
|
[chrome] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在:
tests/features/jimaku.spec.ts#L471
2) [chrome] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在 ───────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeAttached()
Locator: locator('#jimaku-full-area')
Expected: attached
Received: <element(s) not found>
Call log:
- expect.toBeAttached with timeout 5000ms
- waiting for locator('#jimaku-full-area')
469 |
470 | const area = p.locator('#jimaku-full-area')
> 471 | await expect(area).toBeAttached()
| ^
472 |
473 | const subtitleList = area.locator('#subtitle-list')
474 | await expect(subtitleList).toBeVisible()
at /home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/features/jimaku.spec.ts:471:24
|
[chrome] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在:
tests/features/jimaku.spec.ts#L471
2) [chrome] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在 ───────────────────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeAttached()
Locator: locator('#jimaku-full-area')
Expected: attached
Received: <element(s) not found>
Call log:
- expect.toBeAttached with timeout 5000ms
- waiting for locator('#jimaku-full-area')
469 |
470 | const area = p.locator('#jimaku-full-area')
> 471 | await expect(area).toBeAttached()
| ^
472 |
473 | const subtitleList = area.locator('#subtitle-list')
474 | await expect(subtitleList).toBeVisible()
at /home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/features/jimaku.spec.ts:471:24
|
[edge] › content.spec.ts:363:5 › 測試底部的按鈕:
tests/content.spec.ts#L1
1) [edge] › content.spec.ts:363:5 › 測試底部的按鈕 ──────────────────────────────────────────────────────
Test timeout of 120000ms exceeded.
|
[edge] › content.spec.ts:363:5 › 測試底部的按鈕:
tests/content.spec.ts#L370
1) [edge] › content.spec.ts:363:5 › 測試底部的按鈕 ──────────────────────────────────────────────────────
Error: locator.click: Target page, context or browser has been closed
Call log:
- waiting for getByTitle('查看源代码')
- locator resolved to <button title="查看源代码" type="button" class="relative align-middle select-none font-sans font-medium text-center uppercase transition-all disabled:opacity-50 disabled:shadow-none disabled:pointer-events-none w-12 max-w-[48px] h-12 max-h-[48px] text-sm text-gray-900 hover:bg-gray-900/10 active:bg-gray-900/20 rounded-full shadow-md bg-white">…</button>
- attempting click action
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="bili-mini-mask">…</div> from <body class="supportWebp risk-captcha-adapt-pc risk-captcha-adapt">…</body> subtree intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="bili-mini-mask fade-leave-active fade-leave-to">…</div> from <body class="supportWebp risk-captcha-adapt-pc risk-captcha-adapt">…</body> subtree intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is not stable
- retrying click action, attempt #3
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is not stable
- retrying click action, attempt #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #5
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #6
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #7
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #8
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #9
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #10
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #11
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element is outside of the viewport
- retrying click action, attempt #12
- waiting 500m
|
[edge] › content.spec.ts:363:5 › 測試底部的按鈕:
tests/content.spec.ts#L369
1) [edge] › content.spec.ts:363:5 › 測試底部的按鈕 ──────────────────────────────────────────────────────
Error: browserContext.waitForEvent: Target page, context or browser has been closed
367 | await button.click()
368 | await content.locator('#bjf-main-menu').waitFor({ state: 'visible' })
> 369 | let popup = context.waitForEvent('page', { predicate: p => p.url().includes('github.com') })
| ^
370 | await content.getByTitle('查看源代码').click()
371 | const p1 = await popup
372 |
at /home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/content.spec.ts:369:25
|
[edge] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在:
tests/helpers/bilibili-api.ts#L55
2) [edge] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在 ─────────────────────────────────────
Error: apiRequestContext.get: socket hang up
Call log:
- → GET https://api.live.bilibili.com/room/v1/Room/room_init?id=63758
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6723.31 Safari/537.36 Edg/130.0.6723.31
- accept: */*
- accept-encoding: gzip,deflate,br
- cookie: LIVE_BUVID=AUTO5017300322065559
at helpers/bilibili-api.ts:55
53 | const release = await this.mutex.acquire()
54 | try {
> 55 | const res = await this.context.get(path)
| ^
56 | if (!res.ok()) throw new Error(`获取bilibili API失败:${res.statusText()}`)
57 | return await res.json()
58 | } finally {
at BilbiliApi.fetch (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/bilibili-api.ts:55:44)
at BilbiliApi.getRoomStatus (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/bilibili-api.ts:70:22)
at BilibiliPage.isStatus (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/bilibili-page.ts:65:16)
at RoomTypeFinder.getRoomType (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/room-finder.ts:51:17)
at RoomTypeFinder.findRoomType (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/room-finder.ts:97:30)
at RoomTypeFinder.findRoomTypeWithCache (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/helpers/room-finder.ts:130:22)
at Object.exports.test._extension.extensionBase.extend.themeRoom.timeout (/home/runner/work/bilibili-vup-stream-enhancer/bilibili-vup-stream-enhancer/tests/fixtures/content.ts:53:26)
|
test (units)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Slow Test:
[units] › units/capture.spec.ts#L1
[units] › units/capture.spec.ts took 32.2s
|
test (integrations)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
e2e-test (edge, -theme)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
e2e-test (chrome, -theme)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Slow Test:
[chrome-theme] › features/jimaku.spec.ts#L1
[chrome-theme] › features/jimaku.spec.ts took 5.5m
|
Slow Test:
[theme-setup] › theme.setup.ts#L1
[theme-setup] › theme.setup.ts took 1.4m
|
Slow Test:
[chrome-theme] › pages/encoder.spec.ts#L1
[chrome-theme] › pages/encoder.spec.ts took 16.5s
|
e2e-test (chrome)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Slow Test:
[chrome] › pages/encoder.spec.ts#L1
[chrome] › pages/encoder.spec.ts took 16.2s
|
e2e-test (edge)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
🎭 Playwright Run Summary
3 skipped
15 passed (2.2m)
|
🎭 Playwright Run Summary
1 flaky
[integrations] › integrations/summarizer.spec.ts:69:5 › 测试 @cf/qwen/qwen1.5-1.8b-chat 模型的AI总结结果
1 skipped
7 passed (1.8m)
|
🎭 Playwright Run Summary
1 flaky
[theme-setup] › theme.setup.ts:5:6 › 預先搜索大海報房間 ─────────────────────────────────────────────────
2 skipped
65 passed (11.4m)
|
🎭 Playwright Run Summary
1 flaky
[chrome-theme] › content.spec.ts:311:5 › 測試全屏時有否根據設定顯示隱藏浮動按鈕 ───────────────────────────────────
6 skipped
61 passed (36.7m)
|
🎭 Playwright Run Summary
2 flaky
[chrome] › content.spec.ts:157:5 › 測試添加到黑名单按鈕 ──────────────────────────────────────────────────
[chrome] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在 ────────────────────────────────────
2 skipped
63 passed (38.9m)
|
🎭 Playwright Run Summary
2 flaky
[edge] › content.spec.ts:363:5 › 測試底部的按鈕 ───────────────────────────────────────────────────────
[edge] › features/jimaku.spec.ts:463:5 › 測試大海報房間下字幕區塊是否存在 ──────────────────────────────────────
2 skipped
63 passed (39.7m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
chrome-mv3
Expired
|
49.7 MB |
|
chrome-test-results
Expired
|
12.3 GB |
|
chrome-theme-test-results
Expired
|
9.89 GB |
|
chromium-mv3
Expired
|
49.7 MB |
|
edge-mv3
Expired
|
49.7 MB |
|
edge-test-results
Expired
|
11.8 GB |
|
edge-theme-test-results
Expired
|
1.59 GB |
|
integrations-test-results
Expired
|
124 MB |
|
units-test-results
Expired
|
151 MB |
|