Your message dated Mon, 24 Aug 2020 19:03:56 +0000 with message-id <[email protected]> and subject line Bug#964667: fixed in node-chokidar 3.4.2-1 has caused the Debian Bug report #964667, regarding node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 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 [email protected] immediately.) -- 964667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964667 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: node-chokidar Version: 3.4.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > # No pkg-js-tools auto build > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test --buildsystem=nodejs > /bin/sh -ex debian/tests/pkg-js/test > + mocha --exit --reporter spec --timeout 8000 > > > chokidar > ✓ should expose public API methods > fs.watch (non-polling) > watch a directory > ✓ should produce an instance of chokidar.FSWatcher > ✓ should expose public API methods > ✓ should emit `add` event when file was added (44ms) > ✓ should emit nine `add` events when nine files were added in one > directory (1294ms) > ✓ should emit thirtythree `add` events when thirtythree files were > added in nine directories (2857ms) > ✓ should emit `addDir` event when directory was added > ✓ should emit `change` event when file was changed > ✓ should emit `unlink` event when file was removed (102ms) > ✓ should emit `unlinkDir` event when a directory was removed (43ms) > ✓ should emit two `unlinkDir` event when two nested directories were > removed (5025ms) > ✓ should emit `unlink` and `add` events when a file is renamed (123ms) > ✓ should emit `add`, not `change`, when previously deleted file is > re-added (165ms) > ✓ should not emit `unlink` for previously moved files (404ms) > ✓ should survive ENOENT for missing subdirectories > ✓ should notice when a file appears in a new directory > ✓ should watch removed and re-added directories (1544ms) > ✓ should emit `unlinkDir` and `add` when dir is replaced by file > (84ms) > ✓ should emit `unlink` and `addDir` when file is replaced by dir > (144ms) > watch individual files > ✓ should detect changes > ✓ should detect unlinks (121ms) > ✓ should detect unlink and re-add (164ms) > ✓ should ignore unwatched siblings (43ms) > Skipping gh-682: should detect unlink > - should detect unlink while watching a non-existent second file in > another directory > - should detect unlink and re-add while watching a second file > - should detect unlink and re-add while watching a non-existent > second file in another directory > - should detect unlink and re-add while watching a non-existent > second file in the same directory > - should detect two unlinks and one re-add > - should detect unlink and re-add while watching a second file and > a non-existent third file > renamed directory > ✓ should emit `add` for a file in a renamed directory (1024ms) > watch non-existent paths > ✓ should watch non-existent file and detect add (42ms) > ✓ should watch non-existent dir and detect addDir/add (63ms) > watch glob patterns > ✓ should correctly watch and emit based on glob input (47ms) > ✓ should respect negated glob patterns (122ms) > ✓ should traverse subdirs to match globstar patterns (177ms) > ✓ should resolve relative paths with glob patterns (45ms) > ✓ should correctly handle conflicting glob patterns (131ms) > ✓ should correctly handle intersecting glob patterns (44ms) > ✓ should not confuse glob-like filenames with globs (63ms) > ✓ should treat glob-like directory names as literal directory names > when globbing is disabled (45ms) > ✓ should treat glob-like filenames as literal filenames when globbing > is disabled (42ms) > ✓ should not prematurely filter dirs against complex globstar > patterns (67ms) > ✓ should emit matching dir events (45ms) > ✓ should correctly handle glob with braces > watch symlinks > ✓ should watch symlinked dirs > ✓ should watch symlinked files > ✓ should follow symlinked files within a normal dir > ✓ should watch paths with a symlinked parent > ✓ should not recurse indefinitely on circular symlinks > ✓ should recognize changes following symlinked dirs > ✓ should follow newly created symlinks (43ms) > ✓ should watch symlinks as files when followSymlinks:false > ✓ should watch symlinks within a watched dir as files when > followSymlinks:false (344ms) > ✓ should not reuse watcher when following a symlink to elsewhere > (64ms) > ✓ should properly match glob patterns that include a symlinked dir > ✓ should emit ready event even when broken symlinks are encountered > watch arrays of paths/globs > ✓ should watch all paths in an array > ✓ should accommodate nested arrays in input > ✓ should throw if provided any non-string paths > watch options > ignoreInitial > false > ✓ should emit `add` events for preexisting files > ✓ should emit `addDir` event for watched dir > ✓ should emit `addDir` events for preexisting dirs > true > ✓ should ignore initial add events > ✓ should ignore add events on a subsequent .add() (1002ms) > ✓ should notice when a file appears in an empty directory > ✓ should emit a change on a preexisting file as a change > ✓ should not emit for preexisting dirs when depth is 0 (422ms) > ignored > ✓ should check ignore after stating > ✓ should not choke on an ignored watch path > ✓ should ignore the contents of ignored dirs (322ms) > ✓ should allow regex/fn ignores (44ms) > depth > ✓ should not recurse if depth is 0 > ✓ should recurse to specified depth (44ms) > ✓ should respect depth setting when following symlinks > ✓ should respect depth setting when following a new symlink > ✓ should correctly handle dir events when depth is 0 (62ms) > atomic > ✓ should ignore vim/emacs/Sublime swapfiles (906ms) > ✓ should ignore stale tilde files > cwd > ✓ should emit relative paths based on cwd (103ms) > ✓ should emit `addDir` with alwaysStat for renamed directory > (1004ms) > ✓ should allow separate watchers to have different cwds (125ms) > ✓ should ignore files even with cwd (47ms) > ignorePermissionErrors > false > ✓ should not watch files without read permissions (202ms) > true > ✓ should watch unreadable files if possible > ✓ should not choke on non-existent files > awaitWriteFinish > ✓ should use default options if none given > ✓ should not emit add event before a file is fully written (203ms) > ✓ should wait for the file to be fully written before emitting the > add event (524ms) > ✓ should emit with the final stats (824ms) > ✓ should not emit change event while a file has not been fully > written (304ms) > ✓ should not emit change event before an existing file is fully > updated (302ms) > ✓ should wait for an existing file to be fully updated before > emitting the change event (523ms) > ✓ should emit change event after the file is fully written (1028ms) > ✓ should not raise any event for a file that was deleted before > fully written (804ms) > ✓ should be compatible with the cwd option (1107ms) > ✓ should still emit initial add events > ✓ should emit an unlink event when a file is updated and deleted > just after that (165ms) > race condition > ✓ should handle unlink that happens while waiting for stat to > return (857ms) > getWatched > ✓ should return the watched paths > ✓ should set keys relative to cwd & include added paths > unwatch > ✓ should stop watching unwatched paths (343ms) > ✓ should ignore unwatched paths that are a subset of watched paths > (343ms) > ✓ should unwatch relative paths (343ms) > ✓ should watch paths that were unwatched and added again (82ms) > ✓ should unwatch paths that are relative to options.cwd (348ms) > close > ✓ should ignore further events on close (903ms) > ✓ should not prevent the process from exiting (112ms) > ✓ should always return the same promise > env variable option override > CHOKIDAR_USEPOLLING > ✓ should make options.usePolling `true` when CHOKIDAR_USEPOLLING is > set to true > ✓ should make options.usePolling `true` when CHOKIDAR_USEPOLLING is > set to 1 > ✓ should make options.usePolling `false` when CHOKIDAR_USEPOLLING > is set to false > ✓ should make options.usePolling `false` when CHOKIDAR_USEPOLLING > is set to 0 > ✓ should not attenuate options.usePolling when CHOKIDAR_USEPOLLING > is set to an arbitrary value > fs.watchFile (polling) > watch a directory > ✓ should produce an instance of chokidar.FSWatcher > ✓ should expose public API methods > ✓ should emit `add` event when file was added (42ms) > ✓ should emit nine `add` events when nine files were added in one > directory (1293ms) > ✓ should emit thirtythree `add` events when thirtythree files were > added in nine directories (2825ms) > ✓ should emit `addDir` event when directory was added > ✓ should emit `change` event when file was changed > ✓ should emit `unlink` event when file was removed > ✓ should emit `unlinkDir` event when a directory was removed (43ms) > ✓ should emit two `unlinkDir` event when two nested directories were > removed (5024ms) > ✓ should emit `unlink` and `add` events when a file is renamed (42ms) > ✓ should emit `add`, not `change`, when previously deleted file is > re-added (64ms) > ✓ should not emit `unlink` for previously moved files (323ms) > ✓ should survive ENOENT for missing subdirectories > ✓ should notice when a file appears in a new directory > ✓ should watch removed and re-added directories (1541ms) > ✓ should emit `unlinkDir` and `add` when dir is replaced by file > (84ms) > ✓ should emit `unlink` and `addDir` when file is replaced by dir > (81ms) > watch individual files > ✓ should detect changes > ✓ should detect unlinks (40ms) > ✓ should detect unlink and re-add (82ms) > ✓ should ignore unwatched siblings (41ms) > Skipping gh-682: should detect unlink > - should detect unlink while watching a non-existent second file in > another directory > - should detect unlink and re-add while watching a second file > - should detect unlink and re-add while watching a non-existent > second file in another directory > - should detect unlink and re-add while watching a non-existent > second file in the same directory > - should detect two unlinks and one re-add > - should detect unlink and re-add while watching a second file and > a non-existent third file > renamed directory > ✓ should emit `add` for a file in a renamed directory (1022ms) > watch non-existent paths > ✓ should watch non-existent file and detect add (41ms) > ✓ should watch non-existent dir and detect addDir/add (63ms) > watch glob patterns > ✓ should correctly watch and emit based on glob input (42ms) > ✓ should respect negated glob patterns (41ms) > ✓ should traverse subdirs to match globstar patterns (117ms) > ✓ should resolve relative paths with glob patterns (41ms) > ✓ should correctly handle conflicting glob patterns (45ms) > ✓ should correctly handle intersecting glob patterns (42ms) > ✓ should not confuse glob-like filenames with globs (61ms) > ✓ should treat glob-like directory names as literal directory names > when globbing is disabled (42ms) > ✓ should treat glob-like filenames as literal filenames when globbing > is disabled (42ms) > ✓ should not prematurely filter dirs against complex globstar > patterns (68ms) > ✓ should emit matching dir events (45ms) > ✓ should correctly handle glob with braces > watch symlinks > ✓ should watch symlinked dirs > ✓ should watch symlinked files > ✓ should follow symlinked files within a normal dir > ✓ should watch paths with a symlinked parent > ✓ should not recurse indefinitely on circular symlinks > ✓ should recognize changes following symlinked dirs > ✓ should follow newly created symlinks (62ms) > ✓ should watch symlinks as files when followSymlinks:false > ✓ should watch symlinks within a watched dir as files when > followSymlinks:false (1244ms) > ✓ should not reuse watcher when following a symlink to elsewhere > (945ms) > 1) should properly match glob patterns that include a symlinked dir > ✓ should emit ready event even when broken symlinks are encountered > watch arrays of paths/globs > ✓ should watch all paths in an array > ✓ should accommodate nested arrays in input > ✓ should throw if provided any non-string paths > watch options > ignoreInitial > false > ✓ should emit `add` events for preexisting files > ✓ should emit `addDir` event for watched dir > ✓ should emit `addDir` events for preexisting dirs > true > ✓ should ignore initial add events > ✓ should ignore add events on a subsequent .add() (1000ms) > ✓ should notice when a file appears in an empty directory > ✓ should emit a change on a preexisting file as a change > ✓ should not emit for preexisting dirs when depth is 0 (421ms) > ignored > ✓ should check ignore after stating > ✓ should not choke on an ignored watch path > ✓ should ignore the contents of ignored dirs (321ms) > ✓ should allow regex/fn ignores (43ms) > depth > ✓ should not recurse if depth is 0 > ✓ should recurse to specified depth (43ms) > ✓ should respect depth setting when following symlinks > ✓ should respect depth setting when following a new symlink > ✓ should correctly handle dir events when depth is 0 (63ms) > atomic > ✓ should ignore vim/emacs/Sublime swapfiles (903ms) > ✓ should ignore stale tilde files > cwd > ✓ should emit relative paths based on cwd > ✓ should emit `addDir` with alwaysStat for renamed directory > (1022ms) > ✓ should allow separate watchers to have different cwds (42ms) > ✓ should ignore files even with cwd (45ms) > ignorePermissionErrors > false > ✓ should not watch files without read permissions (201ms) > true > ✓ should watch unreadable files if possible > ✓ should not choke on non-existent files > awaitWriteFinish > ✓ should use default options if none given > ✓ should not emit add event before a file is fully written (201ms) > ✓ should wait for the file to be fully written before emitting the > add event (525ms) > ✓ should emit with the final stats (822ms) > ✓ should not emit change event while a file has not been fully > written (302ms) > ✓ should not emit change event before an existing file is fully > updated (301ms) > ✓ should wait for an existing file to be fully updated before > emitting the change event (522ms) > ✓ should emit change event after the file is fully written (1068ms) > ✓ should not raise any event for a file that was deleted before > fully written (804ms) > ✓ should be compatible with the cwd option (1105ms) > ✓ should still emit initial add events > ✓ should emit an unlink event when a file is updated and deleted > just after that (83ms) > race condition > ✓ should handle unlink that happens while waiting for stat to > return (774ms) > getWatched > ✓ should return the watched paths > ✓ should set keys relative to cwd & include added paths > unwatch > ✓ should stop watching unwatched paths (342ms) > ✓ should ignore unwatched paths that are a subset of watched paths > (343ms) > ✓ should unwatch relative paths (340ms) > ✓ should watch paths that were unwatched and added again (81ms) > ✓ should unwatch paths that are relative to options.cwd (343ms) > close > ✓ should ignore further events on close (901ms) > ✓ should not prevent the process from exiting (111ms) > ✓ should always return the same promise > env variable option override > CHOKIDAR_USEPOLLING > ✓ should make options.usePolling `true` when CHOKIDAR_USEPOLLING is > set to true > ✓ should make options.usePolling `true` when CHOKIDAR_USEPOLLING is > set to 1 > ✓ should make options.usePolling `false` when CHOKIDAR_USEPOLLING > is set to false > ✓ should make options.usePolling `false` when CHOKIDAR_USEPOLLING > is set to 0 > ✓ should not attenuate options.usePolling when CHOKIDAR_USEPOLLING > is set to an arbitrary value > > > 212 passing (1m) > 12 pending > 1 failing > > 1) chokidar > fs.watchFile (polling) > watch symlinks > should properly match glob patterns that include a symlinked dir: > AssertionError: expected addSpy to have been called with arguments > test-fixtures/155-link/add.txt > Call 1: > test-fixtures/155-link/change.txt test-fixtures/155-link/add.txt > [Stats] { > atime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > atimeMs: 1594256061312.3408, > birthtime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > birthtimeMs: 1594256061312.3408, > blksize: 4096, > blocks: 8, > ctime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > ctimeMs: 1594256061312.3408, > dev: 66308, > gid: 1001, > ino: 5113916, > mode: 33188, > mtime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > mtimeMs: 1594256061312.3408, > nlink: 1, > rdev: 0, > size: 1, > uid: 1001 > } > Call 2: > test-fixtures/155-link/unlink.txt test-fixtures/155-link/add.txt > [Stats] { > atime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > atimeMs: 1594256061312.3408, > birthtime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > birthtimeMs: 1594256061312.3408, > blksize: 4096, > blocks: 8, > ctime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > ctimeMs: 1594256061312.3408, > dev: 66308, > gid: 1001, > ino: 5113917, > mode: 33188, > mtime: Thu Jul 09 2020 00:54:21 GMT+0000 (Coordinated Universal Time), > mtimeMs: 1594256061312.3408, > nlink: 1, > rdev: 0, > size: 1, > uid: 1001 > } > Call 3: > test-fixtures/155-link/subdir/add.txt test-fixtures/155-link/add.txt > [Stats] { > atime: Thu Jul 09 2020 00:55:06 GMT+0000 (Coordinated Universal Time), > atimeMs: 1594256106680.6865, > birthtime: Thu Jul 09 2020 00:55:06 GMT+0000 (Coordinated Universal Time), > birthtimeMs: 1594256106680.6865, > blksize: 4096, > blocks: 8, > ctime: Thu Jul 09 2020 00:55:06 GMT+0000 (Coordinated Universal Time), > ctimeMs: 1594256106680.6865, > dev: 66308, > gid: 1001, > ino: 5114787, > mode: 33188, > mtime: Thu Jul 09 2020 00:55:06 GMT+0000 (Coordinated Universal Time), > mtimeMs: 1594256106680.6865, > nlink: 1, > rdev: 0, > size: 1, > uid: 1001 > } > at Context.<anonymous> (test.js:1203:31) > > > > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2020/07/09/node-chokidar_3.4.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---Source: node-chokidar Source-Version: 3.4.2-1 Done: Xavier Guimard <[email protected]> We believe that the bug you reported is fixed in the latest version of node-chokidar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard <[email protected]> (supplier of updated node-chokidar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 24 Aug 2020 17:18:39 +0200 Source: node-chokidar Architecture: source Version: 3.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers <[email protected]> Changed-By: Xavier Guimard <[email protected]> Closes: 964667 Changes: node-chokidar (3.4.2-1) unstable; urgency=medium . * Team upload * Set test timeout to the value given by upstream (Closes: #964667) * New upstream version 3.4.2 * Bump debhelper compatibility level to 13 Checksums-Sha1: b51c54808f946d0542dee3c198fe44cafb209266 2804 node-chokidar_3.4.2-1.dsc 8f66dbcd55a883acdae4408af8b035a5044c1894 7985 node-chokidar_3.4.2.orig-upath.tar.gz ea8db092159c1a631b3d9f9f435295efe18257ed 45822 node-chokidar_3.4.2.orig.tar.gz f1afb6cfe141375d3144f0e053cde2c42f9baa23 3188 node-chokidar_3.4.2-1.debian.tar.xz Checksums-Sha256: 79085eeef60635f974aa8e4ab646189f07623636a967b2b31fca6a0cc708d275 2804 node-chokidar_3.4.2-1.dsc 73ed9ceee7c677bf1dd2aca6c2dce843975a6d267ff9afe754e6e3af69a11d10 7985 node-chokidar_3.4.2.orig-upath.tar.gz 95d79ab038ccbd4d4cd0faff76698c4db606c868146c3bda5a0aee907a93318a 45822 node-chokidar_3.4.2.orig.tar.gz efa5466b95a5892e7457dcda44f397cee451d763d576530ba5450861a1393989 3188 node-chokidar_3.4.2-1.debian.tar.xz Files: b13beac0342bd2cf0802303a5d101e40 2804 javascript optional node-chokidar_3.4.2-1.dsc d9f10129f1b6f6bfba6d4de6646d8906 7985 javascript optional node-chokidar_3.4.2.orig-upath.tar.gz 80b52b3d58f6bbccee5dfed315b55096 45822 javascript optional node-chokidar_3.4.2.orig.tar.gz 323da2dbff547ef3f0885d5056390655 3188 javascript optional node-chokidar_3.4.2-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl9ECioACgkQ9tdMp8mZ 7ukpNA//XrqJOUS5xqTAErCoUS26/H3I/S1U640C1+n7bNxGY6d7AeFyjZUNMq0l ltGDFHfOxPXU4Z/8MBB6nMXX/vobxmX4HgKnHH+HZGHE7G50XER5udBC/I6MJCrJ iqVLsdAxqNvQFM0ntVZlfBb0Ky78hLsqsGMWABKbnK1/u0CdgyDnidTVrgXyOSyz 0aas8Ztzbm94sl0AuAu5FhQig1WqT8gVxJE02lhmaSoO7CtONZkCscdXHL5+KNqB m/mRr+7bH9Asv6BMdZFLJrdlneSCx9VGqpXHIO6dnMBSkRgQtPmEH4/uDVhfI8cv QHyISdLv1+YITEy/HItC7gRFU62E2XAZjLJ7aP4jN+ehZbxazZdgmB7AzUbx7LVA sZb9DaXRTxJOmwzQXeNw817ewnlMyuES666/LM/tUj9AYLyQX2yy0fts/ItWzwXn L46xb0r1PMvEsVkuomDCpccMyfS5tTYsiqi7wHkKi2cSdUXJpOuxxpetCoGxPlNX vY5ITQO9mJGE2BWfScRdrGXwWczrQ8KkQViRIqRsmBl6pwt8ne9k5rSqDfZRLPfN z4d1tUnnks2k5uc00WX8lCx0diwlycZaN6mjVaqTWAOckGbh8ssPMz8CaXYfi5qt j4uGIDDSKSgr0YrqFh+ycnuzxRm5KSPCF4wK+8suBp0/Z9Z8Kig= =aRBh -----END PGP SIGNATURE-----
--- End Message ---
