Infrastructure Scenario Tests

We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.

21,502
Total Tests
100.0%
Pass Rate
21,502
Passed
0
Failed

MySQL 8.4 Hitting cgroup CPU Throttle on Ubuntu 22.04 LTS

PASS

MySQL 8.4 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

MySQL 8.4 Hitting cgroup CPU Throttle on RHEL 9

PASS

MySQL 8.4 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

MySQL 8.4 Hitting cgroup CPU Throttle on Debian 12 Bookworm

PASS

MySQL 8.4 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

MySQL 8.4 Hitting cgroup CPU Throttle on Oracle Linux 9

PASS

MySQL 8.4 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

MySQL 8.4 Hitting cgroup CPU Throttle on Rocky Linux 9

PASS

MySQL 8.4 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Hitting cgroup CPU Throttle on Windows Server 2019

PASS

PostgreSQL 16 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Hitting cgroup CPU Throttle on Ubuntu 24.04 LTS

PASS

PostgreSQL 16 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

MySQL 8.4 Hitting cgroup CPU Throttle on Arch Linux

PASS

MySQL 8.4 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Hitting cgroup CPU Throttle on Fedora 40 Server

PASS

PostgreSQL 16 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Hitting cgroup CPU Throttle on Ubuntu 22.04 LTS

PASS

PostgreSQL 16 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Hitting cgroup CPU Throttle on Windows Server 2022

PASS

PostgreSQL 16 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

PostgreSQL 16 Hitting cgroup CPU Throttle on Windows 11 Enterprise

PASS

PostgreSQL 16 is being CPU-throttled by cgroup limits. Container CPU quota exhausted, causing severe latency spikes.

DatabasePattern: HIGH_CPUSeverity: HIGHConfidence: 68%Auto-Heal

Neo4j 5.18 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 22.04 LTS

PASS

Neo4j 5.18 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Neo4j 5.18 Failed Graceful Shutdown — Killed with SIGKILL on Ubuntu 24.04 LTS

PASS

Neo4j 5.18 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Neo4j 5.18 Failed Graceful Shutdown — Killed with SIGKILL on CentOS 9 Stream

PASS

Neo4j 5.18 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Oracle Database 23c Failed Graceful Shutdown — Killed with SIGKILL on Windows 10 Enterprise

PASS

Oracle Database 23c did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

TimescaleDB 2.14 Failed Graceful Shutdown — Killed with SIGKILL on Arch Linux

PASS

TimescaleDB 2.14 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

TimescaleDB 2.14 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

TimescaleDB 2.14 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

Oracle Database 23c Failed Graceful Shutdown — Killed with SIGKILL on Windows 11 Enterprise

PASS

Oracle Database 23c did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal

ScyllaDB 6.0 Failed Graceful Shutdown — Killed with SIGKILL on Fedora 40 Server

PASS

ScyllaDB 6.0 did not shut down within the timeout period and was force-killed with SIGKILL. Data corruption possible.

DatabasePattern: PROCESS_CRASH_LOOPSeverity: HIGHConfidence: 72%Auto-Heal
PreviousPage 8 of 275Next

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.