Posted by Martin on Mar 16, 2022; 11:12am
URL: https://forum.jogamp.org/JOGL-2-4-and-Java-17-report-tp4041572p4041693.html

Hi Mabula,

A side remark : I often had poor results running JOGL on virtual machines.

You may indeed end up using Mesa OpenGL implementation instead of your GPU driver. Not a big deal per se, but this is a different execution path where you are not relying on the OS-provided OpenGL. It may be slower than running on real hardware and you may have to modify timeouts through JOGL properties to avoid some JOGL exception. If not, you may get a slow rendering.

If you do this for the purpose of validating the compatibility of your software with one of your client OS, it won't be a realistic test. This is why I stoped running unit and integration tests on Github Actions VM and finally used self hosted nodes to run the automated tests (these nodes are all normal computers linked to Github Actions).

This being said, I don't think it would explain this IOException with error=13 code.