Your message dated Fri, 25 Mar 2022 15:29:58 +0000
with message-id <9e2043f1-0ffc-bb34-ba25-5cfba374b...@debian.org>
and subject line Re: node-puppeteer: broken autopkgtest keeping chromium from
migrating to testing
has caused the Debian Bug report #1007983,
regarding node-puppeteer: broken autopkgtest keeping chromium from migrating to
testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1007983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-puppeteer
Control: found -1 node-puppeteer/13.1.0+dfsg-6
Control: affects -1 chromium
Severity: serious
Tags: sid bookworm
node-puppeteer is keeping chromium from migrating; as
https://tracker.debian.org/pkg/chromium describes,
"Issues preventing migration:
∙ ∙ autopkgtest for node-puppeteer/13.1.0+dfsg-6: amd64: Regression ♻
(reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻
(reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Not a
regression"
One of the failure logs is here:
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20095690/log.gz
1 failing
1) AriaQueryHandler
queryOne (Chromium web test)
should find by role "button":
Error: expect(received).toEqual(expected) // deep equality
- Expected - 0
+ Received + 1
Array [
"node5",
"node6",
+ "node7",
"node8",
"node10",
"node21",
]
I'm not entirely sure why it's failing, as the test in
node-puppeteer-13.1.0+dfsg/test/ariaqueryhandler.spec.ts seems to be
searching for button nodes and finds an extra (hidden) button:
it('should find by role "button"', async () => {
const { page } = getTestState();
const found = await
page.$$<HTMLButtonElement>('aria/[role="button"]'); const ids =
await getIds(found); expect(ids).toEqual(['node5', 'node6',
'node8', 'node10', 'node21']); });
Please fix the test; or if this is an actual bug in chromium, please
reassign and let me know.
Thanks,
Andres
--- End Message ---
--- Begin Message ---
Package: node-puppeteer
Version: 13.4.1+dfsg-1
I had forgotten to close this bug with my last upload, which fixes those
issues.
--
Martina Ferrari (Tina)
--- End Message ---
