Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Ubuntu 24.04 LTS
PASSZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Debian 12 Bookworm
PASSActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Rocky Linux 9
PASSActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on CentOS 9 Stream
PASSActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Ubuntu 24.04 LTS
PASSActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on Ubuntu 22.04 LTS
PASSActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ActiveMQ 6.1 Startup Timeout — Taking Too Long to Initialize on RHEL 9
PASSActiveMQ 6.1 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
ZeroMQ 4.3 Startup Timeout — Taking Too Long to Initialize on Ubuntu 22.04 LTS
PASSZeroMQ 4.3 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Arch Linux
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Fedora 40 Server
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Oracle Linux 9
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on AlmaLinux 9
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on SUSE Enterprise 15 SP5
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Amazon Linux 2023
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on RHEL 9
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Debian 12 Bookworm
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Rocky Linux 9
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on CentOS 9 Stream
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Ubuntu 24.04 LTS
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Pulsar 3.2 Startup Timeout — Taking Too Long to Initialize on Ubuntu 22.04 LTS
PASSPulsar 3.2 is taking over 5 minutes to start, exceeding the systemd/Docker timeout. Service killed before becoming ready.
Every scenario is tested against Corax's Neural Engine in a production environment with AI-powered root cause analysis.
Tests run continuously as new infrastructure patterns are added.