4 ms·

Looking at this: https://codereview.chromium.org/1548893004/ https://codereview.chromium.org/1548893004/ and this, is there chance that there will be decent opt

by yarp 11y ago

Looking at this: https://codereview.chromium.org/1548893004/ https://codereview.chromium.org/1548893004/ and this, is there chance that there will be decent option for headless webgl testing or making screenshots? Phantomjs doesnt want to do that, slimmerjs also (on xvfb), anybody have a working solution?

bhouston 11y ago
For http://Clara.io http://Clara.io, we explored a bunch of headless gl solutions and none worked. It may have changed by now. But even if you got a headless gl solution working, it likely would have poor extension support, which means the results will suffer anyhow. :(
- yarp 11y ago
  So did you take any other solution? I was thinking about renting or collocating server with gpu and just automate whole process with ansible/fabric or just vnc. About exentions - thats true. I was able to run software rending for shaders (llvm, xvfb, ec2), framerate was acceptable (1-5 fps, which is more than fine for screenshots), but issues like having max anisotropy = 1 make it unusable for this use case.
jdashg 11y ago
Mozilla's WebGL CI tests for Linux and Android run on Mesa's software renderer, though I'm not sure if we use LLVMPipe specifically. It works...ok.
- yarp 11y ago
  Could you provide some links to results? Are you talking about mochitest-gl?
  - jdashg 11y ago
    Primarily mochitest-gl, but also others. You can get an idea of what uses it by seeing what is blocking updating our ancient version of Mesa.[1] We anticipate that this update should improve the reliability of our tests. I don't think there are specific results that are useful to anyone but us, other than that Mesa is viable for these sorts of things. We don't have a centralized tracking list for Mesa issues. Like usual, if you try running WebGL on Mesa and run into unfixed issues, file a bug and we'll fix it. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1220658 https://bugzilla.mozilla.org/show_bug.cgi?id=1220658

by yarp 11y ago

bhouston 11y ago

For http://Clara.io http://Clara.io, we explored a bunch of headless gl solutions and none worked. It may have changed by now. But even if you got a headless gl solution working, it likely would have poor extension support, which means the results will suffer anyhow. :(

yarp 11y ago
So did you take any other solution? I was thinking about renting or collocating server with gpu and just automate whole process with ansible/fabric or just vnc. About exentions - thats true. I was able to run software rending for shaders (llvm, xvfb, ec2), framerate was acceptable (1-5 fps, which is more than fine for screenshots), but issues like having max anisotropy = 1 make it unusable for this use case.

jdashg 11y ago

Mozilla's WebGL CI tests for Linux and Android run on Mesa's software renderer, though I'm not sure if we use LLVMPipe specifically. It works...ok.

yarp 11y ago
Could you provide some links to results? Are you talking about mochitest-gl?
- jdashg 11y ago
  Primarily mochitest-gl, but also others. You can get an idea of what uses it by seeing what is blocking updating our ancient version of Mesa.[1] We anticipate that this update should improve the reliability of our tests. I don't think there are specific results that are useful to anyone but us, other than that Mesa is viable for these sorts of things. We don't have a centralized tracking list for Mesa issues. Like usual, if you try running WebGL on Mesa and run into unfixed issues, file a bug and we'll fix it. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1220658 https://bugzilla.mozilla.org/show_bug.cgi?id=1220658