Critical state of GlassFish CI @CBI
Summary
https://ci.eclipse.org/glassfish/computer/
Dozens of agents listed as offline due to error in starting.
This only fraction of the list.
No build can run (for example https://github.com/eclipse-ee4j/glassfish-hk2/pull/917 is queued for 4 hours).
https://www.eclipsestatus.io/ - all systems operational
Steps to reproduce
(How one can reproduce the issue - this is very important)
What is the current bug behavior?
(What actually happens)
What is the expected correct behavior?
(What you should see instead)
Relevant logs and/or screenshots
(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
Priority
-
Urgent -
High -
Medium -
Low
Marking as low as it's not critical (for me) now.
Severity
-
Blocker -
Major -
Normal -
Low
Marking as blocker as the instance is not operational at the moment.