Source: node-postgres
Version: 7.14.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
> dh_update_autotools_config
> dh_autoreconf
> dh_auto_configure --buildsystem=nodejs
> Link node_modules/buffer-writer -> ../buffer-writer
> Link node_modules/packet-reader -> ../packet-reader
> Link node_modules/pg-connection-string -> ../pg-connection-string
> Link node_modules/pg-cursor -> ../pg-cursor
> Link node_modules/pg-int8 -> ../pg-int8
> Link node_modules/pg-numeric -> ../pg-numeric
> Link node_modules/pg-pool -> ../pg-pool
> Link node_modules/pg-types -> ../pg-types
> Link node_modules/pgpass -> ../pgpass
> Link node_modules/postgres-array -> ../postgres-array
> Link node_modules/postgres-bytea -> ../postgres-bytea
> Link node_modules/postgres-date -> ../postgres-date
> Link node_modules/postgres-interval -> ../postgres-interval
> Link pg-pool/node_modules/pg-cursor -> ../../pg-cursor
> Link pg-types/node_modules/pg-int8 -> ../../pg-int8
> dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> dh_auto_test --buildsystem=nodejs
> ln -s ../debian/tests/test_modules/pff node_modules/pff
> ln -s ../. node_modules/pg
> cd ./buffer-writer && sh -ex ../debian/nodejs/buffer-writer/test
> + mocha
>
>
> undefined writes char
> undefined gets correct byte length
> undefined can add arbitrary buffer to the end
> undefined resizing to much larger
> adding int32
> undefined writes 0
> undefined writes 1
> undefined writes 256
> undefined writes largest int32
> undefined writing multiple int32s
> having to resize the buffer
> undefined after resize correct result returned
>
> int16
> undefined writes 0
> undefined writes 400
> undefined writes many
> undefined resizes if internal buffer fills up
>
> cString
> undefined writes empty cstring
> undefined writes two empty cstrings
> undefined writes non-empty cstring
> undefined resizes if reached end
> undefined writes multiple cstrings
>
> can write normal string
> undefined can write cString too
> undefined can resize
>
> clearing
> undefined clears
> undefined writing more
> undefined returns result
> undefined clears the writer
>
> flush
> undefined added as a hex code to a full writer
> undefined added as a hex code to a non-full writer
> undefined added as a hex code to a buffer which requires resizing
>
> header
> undefined adding two packets with headers
>
>
> 29 passing (16ms)
>
> cd ./packet-reader && sh -ex ../debian/nodejs/packet-reader/test
> + mocha
>
>
> packet-reader
> undefined reads perfect 1 length buffer
> undefined reads perfect longer buffer
> undefined reads two parts
> undefined reads multi-part
> undefined resets internal buffer at end of packet
> undefined reads multiple messages from single chunk
> undefined reads 1 and a split
>
> variable length header
> undefined reads double message buffers
>
> 1 length code
> undefined reads code
> undefined is set on uncompleted read
>
> postgres style packet
> undefined reads with padded length
>
>
> 11 passing (12ms)
>
> cd ./pg-int8 && sh -ex ../debian/nodejs/pg-int8/test
> + tap test
> TAP version 13
> not ok 1 - test # time=18.914ms {
> not ok 1 - ENOENT: no such file or directory, stat 'test'
> ---
> stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object.<anonymous> (/usr/share/nodejs/tap/bin/run.js:874:23)
> at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
> errno: -2
> syscall: stat
> code: ENOENT
> path: test
> test: test
> ...
>
> 1..1
> # failed 1 test
> }
>
> 1..1
> # failed 1 test
> # time=43.096ms
> ----------|---------|----------|---------|---------|-------------------
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> ----------|---------|----------|---------|---------|-------------------
> All files | 0 | 0 | 0 | 0 |
> ----------|---------|----------|---------|---------|-------------------
> dh_auto_test: error: cd ./pg-int8 && sh -ex ../debian/nodejs/pg-int8/test
> returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-postgres_7.14.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
