Gamut Mapping Test Failures (due to htest?)

[facelessuser]

Gamut mapping tests are currently failing due to the call stack blowing up:

Uncaught RangeError: Maximum call stack size exceeded
    at custom (util.js:75:11)
    at callee (objects.js:225:15)
    at Module.stringify (objects.js:212:9)
    at stringify (util.js:151:17)
    at output (util.js:74:9)
    at Array.map (<anonymous>)
    at custom (util.js:77:16)
    at callee (objects.js:225:15)
    at Module.stringify (objects.js:212:9)
    at stringify (util.js:151:17)

This affects a few other tests as well.

I suspect this is due to special functions related to htest getting called? check.deep etc. I have no idea though, and I didn't look to close.

[lloydk]

Strange, the tests run fine for me.

[facelessuser]

This is what I get looking at the official tests via Chrome and Safari.

I can check when I'm no longer behind my company's network.

[lloydk]

I was running the tests from the command line. Not seeing the same error you're seeing when running the tests from the browser but I'm seeing quite a few test failures and some errors in the console.

[facelessuser]

@lloydk Are you checking colorjs.io/tests or colorjs.io/test? The former runs with errors, the latter is what I'm seeing, which I thought was the new tests, but correct me if I am wrong.

[lloydk]

/tests is old, /test has the new tests

…

On Wed, Sep 3, 2025 at 11:30 AM Isaac Muse ***@***.***> wrote: *facelessuser* left a comment (color-js/color.js#673) <#673 (comment)> @lloydk <https://github.com/lloydk> Are you checking colorjs.io/tests or colorjs.io/test? The former runs with errors, the latter is what I'm seeing, which I thought was the new tests, but correct me if I am wrong. — Reply to this email directly, view it on GitHub <#673 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAP4MEXAYFJTSRXGHNZZYT3Q4QSDAVCNFSM6AAAAACFRFVOZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJQGE2DMNRUGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[facelessuser]

I've tested colorjs.io/test on 3 different computers (2 Windows and 1 Mac). I've tested it in Chrome, Firefox, and Safari. I can't explain why you may not see the same errors I see, but it seems broken from every system I've tried to look at it with.

[lloydk]

I've tested colorjs.io/test on 3 different computers (2 Windows and 1 Mac). I've tested it in Chrome, Firefox, and Safari. I can't explain why you may not see the same errors I see, but it seems broken from every system I've tried to look at it with.

Running the tests from https://colorjs.io/test/ I do see the same error. I was running the tests locally using the live-server npm package and saw different errors for some reason.

[facelessuser]

Oh, okay