I recently enabled Github CI to test Jzy3D (which uses JOGL). I have been surprised to see this kind of messages
Unable to create basic Accelerated OpenGL renderer.
Error: Core Image is now using the software OpenGL renderer. This will be slow.
Error: WARNING: GL pipe is running in software mode (Renderer ID=0x1020400)
Is this software renderer part of JOGL?
I also wonder if that may be a reason for all my VBO-related test hanging-then-failing with such message
It prevents from testing reliably. I have tests involving VBOs that sometime hang above the max 5000ms accepted by Jogl, sometime do not. Running the same build & test twice may pass or fail so it is a bit exhausting.
Good job :) By the way, sorry for the silly question, have you ever used Github continuous integration to build JOGL? It would be nice to be able to do it with Gitlab (because I left Github about one year after Microsoft bought it).
Adding self-hosted physical node to Github CI is soooo easy! I just tried with a MacOS and I can get rid of this software renderer issue due to the VM provided by Github. This encourage to go toward multiple physical computers all pointing toward a Cloud CI (whatever the CI is).
I spent so many hours building, improving and maintaining a Jenkins CI with multiple slaves to know that making it work in half a day is an impressive performance (not mine, the tool perf :). I wonder if Jogamp CI is still working? Is it able to test and release everything upon a new commit?
Julien, I will start building JOGL 2.4 for M1. I remember that you made some modification in last RC to make it compile properly. May ask you a pointer to your commit so that I continue with your work? Thanks
If you use --add-opens like me, it should work without modifying the source code. I was waiting for Sven's approval before committing a change on AppContext. Please be aware that you may have to add some other --add-opens clauses when building under other operating systems than GNU Linux.