Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
ZeroMQ 4.3 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSZeroMQ 4.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ZeroMQ 4.3 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSZeroMQ 4.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ActiveMQ 6.1 Container OOM Killed — Memory Limit Hit on Windows 10 Enterprise
PASSActiveMQ 6.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ActiveMQ 6.1 Container OOM Killed — Memory Limit Hit on Windows Server 2022
PASSActiveMQ 6.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ZeroMQ 4.3 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSZeroMQ 4.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ActiveMQ 6.1 Container OOM Killed — Memory Limit Hit on Windows Server 2019
PASSActiveMQ 6.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ActiveMQ 6.1 Container OOM Killed — Memory Limit Hit on Arch Linux
PASSActiveMQ 6.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ActiveMQ 6.1 Container OOM Killed — Memory Limit Hit on Fedora 40 Server
PASSActiveMQ 6.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ActiveMQ 6.1 Container OOM Killed — Memory Limit Hit on Windows 11 Enterprise
PASSActiveMQ 6.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Pulsar 3.2 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSPulsar 3.2 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ZeroMQ 4.3 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSZeroMQ 4.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ZeroMQ 4.3 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSZeroMQ 4.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
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.