[qiqitori]

With regards to Linux (though Android's Chrome has chrome://flags and chrome://gpu as well, so maybe some of this applies as well):

It didn't work for at first, but I got it to show me the "Ah snap! There was no error compiling the test kernel or running it, but the numbers don't check out." message at least. By changing the deviation var to e.g. 0 in the debugger you can also force it show you the results (JS: 0.56, JS&Turbo.js: 1.74), but I don't know if those results mean anything.

Steps to maybe fix:

Does e.g. glxgears work?

On Chrome, check the following two pages:

chrome://flags/ <-- I enabled "Override software rendering list", "Experimental canvas features", "WebGL Draft Extensions" but don't know if all of those are necessary. Better change them back later.

chrome://settings <-- Advanced -> System -> Use hardware acceleration when available

chrome://gpu/ <-- Check if WebGL is enabled, etc. (also check log messages at the bottom)

My graphics hardware is a positively ancient Intel 965GM. (On Windows on a much faster CPU and using Intel HD Graphics 4000, I get JS: 1.28, JS&Turbo.js: 3.82.)

[alphaneuron]

Reading the benchmark script, and the explanation of it at github, I think the deviation is there to account for floating point artifacts. I.e. where JS = 0.01499.. and GPU = 0.01500.., that's fine, but if the numbers (read results from the fractal function) are deviating more, that's an error.

Edit: Actually, "(JS: 0.56, JS&Turbo.js: 1.74)" seems to be a valid result from what I've seen. May just be that the chosen deviation value is an unfortunate edge case.