Source: node-chokidar Version: 3.4.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 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 > ln -s ../. node_modules/chokidar > /bin/sh -ex debian/tests/pkg-js/test > + mocha --exit --reporter spec --timeout 200000 > > > 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 (43ms) > ✓ 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 (2855ms) > ✓ 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 (5024ms) > ✓ should emit `unlink` and `add` events when a file is renamed (123ms) > ✓ should emit `add`, not `change`, when previously deleted file is > re-added (145ms) > ✓ 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 > (143ms) > watch individual files > ✓ should detect changes > ✓ should detect unlinks (121ms) > ✓ should detect unlink and re-add (164ms) > ✓ should ignore unwatched siblings (43ms) > ✓ should detect safe-edit (242ms) > 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 (1026ms) > watch non-existent paths > ✓ should watch non-existent file and detect add (40ms) > ✓ should watch non-existent dir and detect addDir/add (62ms) > watch glob patterns > ✓ should correctly watch and emit based on glob input (47ms) > ✓ should respect negated glob patterns (123ms) > ✓ should traverse subdirs to match globstar patterns (176ms) > ✓ should resolve relative paths with glob patterns (49ms) > ✓ should correctly handle conflicting glob patterns (125ms) > ✓ should correctly handle intersecting glob patterns (43ms) > ✓ should not confuse glob-like filenames with globs (62ms) > ✓ should treat glob-like directory names as literal directory names > when globbing is disabled (44ms) > ✓ should treat glob-like filenames as literal filenames when globbing > is disabled (42ms) > ✓ should not prematurely filter dirs against complex globstar > patterns (72ms) > ✓ should emit matching dir events (67ms) > ✓ 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 (343ms) > ✓ should not reuse watcher when following a symlink to elsewhere > (63ms) > ✓ 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() (1001ms) > ✓ 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 (423ms) > ignored > ✓ should check ignore after stating > ✓ should not choke on an ignored watch path > ✓ should ignore the contents of ignored dirs (323ms) > ✓ should allow regex/fn ignores (44ms) > depth > ✓ should not recurse if depth is 0 > ✓ should recurse to specified depth (45ms) > ✓ 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 (61ms) > atomic > ✓ should ignore vim/emacs/Sublime swapfiles (907ms) > ✓ should ignore stale tilde files > cwd > ✓ should emit relative paths based on cwd (102ms) > ✓ should emit `addDir` with alwaysStat for renamed directory > (1022ms) > ✓ should allow separate watchers to have different cwds (125ms) > ✓ should ignore files even with cwd (48ms) > ignorePermissionErrors > false > ✓ should not watch files without read permissions (204ms) > 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 (202ms) > ✓ should wait for the file to be fully written before emitting the > add event (603ms) > ✓ should emit with the final stats (824ms) > ✓ 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 (302ms) > ✓ should wait for an existing file to be fully updated before > emitting the change event (502ms) > ✓ should emit change event after the file is fully written (1128ms) > ✓ should not raise any event for a file that was deleted before > fully written (802ms) > ✓ should be compatible with the cwd option (1106ms) > ✓ should still emit initial add events > ✓ should emit an unlink event when a file is updated and deleted > just after that (164ms) > race condition > ✓ should handle unlink that happens while waiting for stat to > return (862ms) > 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 (343ms) > ✓ should watch paths that were unwatched and added again (81ms) > ✓ should unwatch paths that are relative to options.cwd (347ms) > close > ✓ should ignore further events on close (903ms) > ✓ should not ignore further events on close with existing watchers > ✓ should not prevent the process from exiting (108ms) > ✓ 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 (1295ms) > ✓ should emit thirtythree `add` events when thirtythree files were > added in nine directories (2822ms) > ✓ 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 (41ms) > ✓ should emit two `unlinkDir` event when two nested directories were > removed (5024ms) > ✓ should emit `unlink` and `add` events when a file is renamed (41ms) > ✓ should emit `add`, not `change`, when previously deleted file is > re-added (63ms) > ✓ should not emit `unlink` for previously moved files (322ms) > ✓ should survive ENOENT for missing subdirectories > ✓ should notice when a file appears in a new directory > ✓ should watch removed and re-added directories (1542ms) > ✓ should emit `unlinkDir` and `add` when dir is replaced by file > (82ms) > ✓ should emit `unlink` and `addDir` when file is replaced by dir > (83ms) > watch individual files > ✓ should detect changes > ✓ should detect unlinks (40ms) > ✓ should detect unlink and re-add (82ms) > ✓ should ignore unwatched siblings (42ms) > ✓ should detect safe-edit (241ms) > 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 (1023ms) > watch non-existent paths > ✓ should watch non-existent file and detect add (41ms) > ✓ should watch non-existent dir and detect addDir/add (60ms) > watch glob patterns > ✓ should correctly watch and emit based on glob input (42ms) > ✓ should respect negated glob patterns (42ms) > ✓ should traverse subdirs to match globstar patterns (115ms) > ✓ should resolve relative paths with glob patterns (40ms) > ✓ should correctly handle conflicting glob patterns (43ms) > ✓ should correctly handle intersecting glob patterns (42ms) > ✓ should not confuse glob-like filenames with globs (63ms) > ✓ should treat glob-like directory names as literal directory names > when globbing is disabled (43ms) > ✓ should treat glob-like filenames as literal filenames when globbing > is disabled (43ms) > ✓ should not prematurely filter dirs against complex globstar > patterns (76ms) > ✓ should emit matching dir events (62ms) > ✓ 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 (42ms) > ✓ should watch symlinks as files when followSymlinks:false > ✓ should watch symlinks within a watched dir as files when > followSymlinks:false (1248ms) > ✓ should not reuse watcher when following a symlink to elsewhere > (944ms) > 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 (423ms) > ignored > ✓ should check ignore after stating > ✓ should not choke on an ignored watch path > ✓ should ignore the contents of ignored dirs (323ms) > ✓ should allow regex/fn ignores (43ms) > 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 (901ms) > ✓ should ignore stale tilde files > cwd > ✓ should emit relative paths based on cwd > ✓ should emit `addDir` with alwaysStat for renamed directory > (1024ms) > ✓ should allow separate watchers to have different cwds (44ms) > ✓ should ignore files even with cwd (44ms) > 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 (202ms) > ✓ should wait for the file to be fully written before emitting the > add event (522ms) > ✓ should emit with the final stats (825ms) > ✓ 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 (300ms) > ✓ should wait for an existing file to be fully updated before > emitting the change event (521ms) > ✓ should emit change event after the file is fully written (1046ms) > ✓ should not raise any event for a file that was deleted before > fully written (801ms) > ✓ should be compatible with the cwd option (1125ms) > ✓ should still emit initial add events > ✓ should emit an unlink event when a file is updated and deleted > just after that (82ms) > race condition > ✓ should handle unlink that happens while waiting for stat to > return (783ms) > 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 (342ms) > ✓ should watch paths that were unwatched and added again (81ms) > ✓ should unwatch paths that are relative to options.cwd (342ms) > close > ✓ should ignore further events on close (902ms) > ✓ should not ignore further events on close with existing watchers > ✓ should not prevent the process from exiting (103ms) > ✓ 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 > (node:26625) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or > directory, unlink '/<<PKGBUILDDIR>>/test-fixtures/217/add.txt' > (node:26625) UnhandledPromiseRejectionWarning: Unhandled promise rejection. > This error originated either by throwing inside of an async function without > a catch block, or by rejecting a promise which was not handled with .catch(). > To terminate the node process on unhandled promise rejection, use the CLI > flag `--unhandled-rejections=strict` (see > https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection > id: 1) > (node:26625) [DEP0018] DeprecationWarning: Unhandled promise rejections are > deprecated. In the future, promise rejections that are not handled will > terminate the Node.js process with a non-zero exit code. > > > 216 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/158-link/add.txt > Call 1: > test-fixtures/158-link/change.txt test-fixtures/158-link/add.txt > [Stats] { > atime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > atimeMs: 1603801729545.9592, > birthtime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > birthtimeMs: 1603801729545.9592, > blksize: 4096, > blocks: 8, > ctime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > ctimeMs: 1603801729545.9592, > dev: 66308, > gid: 1001, > ino: 2101277, > mode: 33188, > mtime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > mtimeMs: 1603801729545.9592, > nlink: 1, > rdev: 0, > size: 1, > uid: 1001 > } > Call 2: > test-fixtures/158-link/unlink.txt test-fixtures/158-link/add.txt > [Stats] { > atime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > atimeMs: 1603801729545.9592, > birthtime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > birthtimeMs: 1603801729545.9592, > blksize: 4096, > blocks: 8, > ctime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > ctimeMs: 1603801729545.9592, > dev: 66308, > gid: 1001, > ino: 2101278, > mode: 33188, > mtime: Tue Oct 27 2020 12:28:49 GMT+0000 (Coordinated Universal Time), > mtimeMs: 1603801729545.9592, > nlink: 1, > rdev: 0, > size: 1, > uid: 1001 > } > Call 3: > test-fixtures/158-link/subdir/add.txt test-fixtures/158-link/add.txt > [Stats] { > atime: Tue Oct 27 2020 12:29:35 GMT+0000 (Coordinated Universal Time), > atimeMs: 1603801775562.5515, > birthtime: Tue Oct 27 2020 12:29:35 GMT+0000 (Coordinated Universal Time), > birthtimeMs: 1603801775562.5515, > blksize: 4096, > blocks: 8, > ctime: Tue Oct 27 2020 12:29:35 GMT+0000 (Coordinated Universal Time), > ctimeMs: 1603801775562.5515, > dev: 66308, > gid: 1001, > ino: 2228375, > mode: 33188, > mtime: Tue Oct 27 2020 12:29:35 GMT+0000 (Coordinated Universal Time), > mtimeMs: 1603801775562.5515, > nlink: 1, > rdev: 0, > size: 1, > uid: 1001 > } > at Context.<anonymous> (test.js:1225: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/10/27/node-chokidar_3.4.2-2_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. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel