#897536 mustache.js: FTBFS: make[1]: rake: Command not found

Package:
src:mustache.js
Source:
mustache.js
Submitter:
Lucas Nussbaum
Date:
2025-08-17 17:48:20 UTC
Severity:
important
Tags:
#897536#5
Date:
2018-05-02 20:51:57 UTC
From:
To:
Hi,

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

Relevant part (hopefully):
http://aws-logs.debian.net/2018/05/02/mustache.js_2.3.0-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.
#897536#10
Date:
2018-05-11 10:12:44 UTC
From:
To:
Hello,

I just tried to reproduce the FTBFS and failed. rake is defined as
build-dependency and correctly pulled in according to linked the build logs.

My best guess is that rake 12.3.1-2 had some bug that got fixed in 12.3.1-3.

Lucas, could you trigger another rebuild to see whether this got fixed
by the latest rake upload?

In any case, it doesn't look like a bug in mustache.js package to me.

Cheers,
 jonas
#897536#17
Date:
2018-05-11 14:54:04 UTC
From:
To:
In this case build-depends on 12.3.1-3.

Bastien
#897536#22
Date:
2018-05-13 22:30:36 UTC
From:
To:
Le vendredi 11 mai 2018 à 12:12:44+0200, Jonas Meurer a écrit :

Indeed the rake issue is gone with the latest upload of rake.

Yet, [1] shows that mustache.js still FTBFS.

The reason seems to be that the mustache.js CLI takes too much time to do
its job in some tests on the build servers of the reproducible-builds
project. As the timeout of mocha testsuite is 2s, this leads to some
failures.

A fix should be designed. I see two solutions:

 1) In all describe statements of cli-test.js[2], add a more reasonable
    timeout delay to mocha, such as
    """
    describe('Mustache CLI', function () {
    this.timeout(5000);
    var expectedOutput;
    […]
    """
 2) Disable these tests.

It should be noted that tests that may fail based on a time-dependency
(timeout, time-based tests) are not fit for reproducibility tests.

Cheers.

[1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mustache.js.html
[2] https://github.com/janl/mustache.js/blob/master/test/cli-test.js
#897536#27
Date:
2018-05-17 08:17:09 UTC
From:
To:
Le 17 mai 2018 10:14:41 GMT+02:00, "Martín Ferrari" <tincho@tincho.org> a écrit :

I have no issue with this decision.

Cheers!
#897536#32
Date:
2018-05-17 08:14:41 UTC
From:
To:
severity 897536 important
thanks

While we should fix this, I don't think this counts as a serious bug.
The tests fail sometimes (probably on a busy server), but that's it.

I think the severity of this bug should be lowered, as this is
threatening to remove from testing mustache.js and its reverse dependencies.
#897536#39
Date:
2018-05-17 08:48:02 UTC
From:
To:
was retried on a idle server after the initial failure.

Lucas
#897536#44
Date:
2018-05-17 12:00:07 UTC
From:
To:
Not sure what happened, but you can see there is some timing info in
some tests, and the run that failed was 3 times slower than the other,
and the tests that passed were very close to the cut-off:

Passing:

  Mustache CLI
    ✓ writes syntax hints into stderr when runned with wrong number of
arguments (531ms)
    ✓ writes hints about JSON parsing errors when given invalid JSON (639ms)
    ✓ writes module version into stdout when runned with --version (605ms)
    ✓ writes module version into stdout when runned with -v (550ms)

Failing:

  Mustache CLI
    ✓ writes syntax hints into stderr when runned with wrong number of
arguments (1795ms)
    1) writes hints about JSON parsing errors when given invalid JSON
    ✓ writes module version into stdout when runned with --version (1828ms)
    ✓ writes module version into stdout when runned with -v (1931ms)