Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSScyllaDB 6.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Neo4j 5.18 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS
PASSNeo4j 5.18 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on Arch Linux
PASSTimescaleDB 2.14 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on Fedora 40 Server
PASSTimescaleDB 2.14 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on Oracle Linux 9
PASSTimescaleDB 2.14 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on AlmaLinux 9
PASSTimescaleDB 2.14 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
TimescaleDB 2.14 Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5
PASSTimescaleDB 2.14 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSScyllaDB 6.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSScyllaDB 6.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSScyllaDB 6.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSScyllaDB 6.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ScyllaDB 6.0 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream
PASSScyllaDB 6.0 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.