[Pkg-javascript-devel] Bug#1011806: node-livescript: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-livescript
Version: 1.6.1+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> mkdir -p lib/
> /usr/bin/lsc --output lib --bare --compile "src/ast.ls"
> /usr/bin/lsc --output lib --bare --compile "src/browser.ls"
> /usr/bin/lsc --output lib --bare --compile "src/command.ls"
> /usr/bin/lsc --output lib --bare --compile "src/grammar.ls"
> /usr/bin/lsc --output lib --bare --compile "src/index.ls"
> /usr/bin/lsc --output lib --bare --compile "src/lang-ls.ls"
> /usr/bin/lsc --output lib --bare --compile "src/lexer.ls"
> /usr/bin/lsc --output lib --bare --compile "src/mode-ls.ls"
> /usr/bin/lsc --output lib --bare --compile "src/node.ls"
> /usr/bin/lsc --output lib --bare --compile "src/options.ls"
> /usr/bin/lsc --output lib --bare --compile "src/repl.ls"
> /usr/bin/lsc --output lib --bare --compile "src/util.ls"
> ./scripts/build-parser
> /usr/bin/lsc --compile package.json.ls
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> help2man --no-info /usr/bin/lsc >lsc.1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_auto_test --buildsystem=nodejs
> 	mkdir -p node_modules
> 	ln -s ../. node_modules/livescript
> 	/bin/sh -ex debian/tests/pkg-js/test
> + ./scripts/test
> Testing with async.
> Testing with async generators.
> test/accessor.ls
> test/assignment.ls
> test/async-generators.ls
> test/async.ls
> test/chaining.ls
> test/cli.ls
> test/comment.ls
> test/compilation.ls
> test/cs-classes.ls
> test/declaration.ls
> test/existence.ls
> test/function.ls
> test/generators.ls
> test/heredoc.ls
> test/if.ls
> test/label.ls
> test/lib.ls
> test/literal.ls
> test/loop.ls
> Expected values to be strictly equal:
> + actual - expected
> 
> + "Cannot read properties of null (reading 'length')"
> - "Cannot read property 'length' of null"
> at test/loop.ls:757:1
> 
> # Certain literals could result in illegal JavaScript if not carefully
> # handled. These are all nonsensical use cases and could just as easily
> # be LiveScript syntax errors. The thing to avoid is for them to be JavaScript
> # syntax errors; lsc should never produce illegal JavaScript on any input,
> # silly or otherwise.
> deep-equal [] [0 for x in 42]
> deep-equal [] [0 for x in -42]
> throws "Cannot read property 'length' of null" -> [0 for x in null]
> throws "Cannot read property 'length' of undefined" -> [0 for x in void]
> 
> # [LiveScript#1035](https://github.com/gkz/LiveScript/issues/1035)
> for [1 2 3] then 1 else 0
> 
> # [LiveScript#1039](https://github.com/gkz/LiveScript/issues/1039)
> arr = [3 2 1 0]
> x = for arr case .. in [1 2] => 1
> test/null.ls
> test/oo.ls
> test/operator.ls
> test/regex.ls
> test/repl.ls
> test/splat.ls
> test/string.ls
> test/switch.ls
> test/try.ls
> failed 1 and passed 2235 tests in 1.73 seconds
> 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/2022/05/25/node-livescript_1.6.1+dfsg-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lucas@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.