Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1102837 > unrolled thread

Bug#1010864: node-chokidar: flaky autopkgtest on most architectures:

Started byPaul Gevers <elbrus@debian.org>
First post2022-05-11 22:00 +0200
Last post2022-05-11 22:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1010864: node-chokidar: flaky autopkgtest on most architectures: Paul Gevers <elbrus@debian.org> - 2022-05-11 22:00 +0200

#1102837 — Bug#1010864: node-chokidar: flaky autopkgtest on most architectures:

FromPaul Gevers <elbrus@debian.org>
Date2022-05-11 22:00 +0200
SubjectBug#1010864: node-chokidar: flaky autopkgtest on most architectures:
Message-ID<Em0F3-eP6k-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Source: node-chokidar
Version: 3.4.3-3
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org
User: debian-ci@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on ppc64el 
because it was showing up as a regression for the upload of nodejs. I 
noticed that the test regularly fails and I saw failures on other 
architectures too (but not on amd64).

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/n/node-chokidar/testing/ppc64el/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/n/node-chokidar/21552316/log.gz

   214 passing (1m)
   12 pending
   1 failing

   1) chokidar
        fs.watch (non-polling)
          watch a directory
            should emit `add`, not `change`, when previously deleted 
file is re-added:
      AssertionError: expected change to not have been called
       at Context.<anonymous> (test.js:301:38)
       at processTicksAndRejections (node:internal/process/task_queues:96:5)

https://ci.debian.net/data/autopkgtest/testing/ppc64el/n/node-chokidar/20264730/log.gz

   213 passing (1m)
   12 pending
   2 failing

   1) chokidar
        fs.watch (non-polling)
          watch options
            awaitWriteFinish
              should emit an unlink event when a file is updated and 
deleted just after that:
      AssertionError: expected spy to not have been called with 
arguments 'change', 'add.txt'
       at Context.<anonymous> (test.js:1590:34)
       at runMicrotasks (<anonymous>)
       at processTicksAndRejections (internal/process/task_queues.js:97:5)

   2) chokidar
        fs.watchFile (polling)
          watch options
            awaitWriteFinish
              should emit an unlink event when a file is updated and 
deleted just after that:
      AssertionError: expected spy to not have been called with 
arguments 'change', 'add.txt'
       at Context.<anonymous> (test.js:1590:34)
       at runMicrotasks (<anonymous>)
       at processTicksAndRejections (internal/process/task_queues.js:97:5)

https://ci.debian.net/data/autopkgtest/testing/ppc64el/n/node-chokidar/20267086/log.gz

   214 passing (1m)
   12 pending
   1 failing

   1) chokidar
        fs.watch (non-polling)
          watch options
            awaitWriteFinish
              should emit an unlink event when a file is updated and 
deleted just after that:
      AssertionError: expected spy to not have been called with 
arguments 'change', 'add.txt'
       at Context.<anonymous> (test.js:1590:34)
       at runMicrotasks (<anonymous>)
       at processTicksAndRejections (internal/process/task_queues.js:95:5)

[toc] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web