Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

2022-03-21 Thread Martina Ferrari 

Hi Andres,

Thanks for your report, puppeteer will need to be updated to match the 
new version of chromium right away.


It seems there are also some flaky tests, which caused the sporadic 
failures...


On 21/03/2022 01:55, Andres Salomon wrote:

On Sat, 19 Mar 2022 17:44:02 -0400 Andres Salomon wrote:
 > 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,


It looks like the tests also failed in testing with chromium v98 
(https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20151806/log.gz), 
which did actually allow chromium v99 to migrate to testing, so you can 
ignore that part of this bug report.





--
Martina Ferrari (Tina)

Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

2022-03-20 Thread Andres Salomon 

On Sat, 19 Mar 2022 17:44:02 -0400 Andres Salomon wrote:
> 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,


It looks like the tests also failed in testing with chromium v98 
(https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20151806/log.gz), 
which did actually allow chromium v99 to migrate to testing, so you can 
ignore that part of this bug report.

Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

2022-03-19 Thread Andres Salomon 
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.$$('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