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

Python 3.12 (Gunicorn) Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

PASS

Python 3.12 (Gunicorn) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Python 3.12 (Gunicorn) Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

Python 3.12 (Gunicorn) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Python 3.12 (Gunicorn) Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

PASS

Python 3.12 (Gunicorn) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Java 21 (Spring Boot) Container OOM Killed — Memory Limit Hit on Windows 10 Enterprise

PASS

Java 21 (Spring Boot) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on RHEL 9

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on Rocky Linux 9

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Go 1.22 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS

PASS

Go 1.22 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Python 3.12 (Gunicorn) Container OOM Killed — Memory Limit Hit on Arch Linux

PASS

Python 3.12 (Gunicorn) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Python 3.12 (Gunicorn) Container OOM Killed — Memory Limit Hit on Fedora 40 Server

PASS

Python 3.12 (Gunicorn) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Python 3.12 (Gunicorn) Container OOM Killed — Memory Limit Hit on Oracle Linux 9

PASS

Python 3.12 (Gunicorn) running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Node.js 20 LTS Container OOM Killed — Memory Limit Hit on Oracle Linux 9

PASS

Node.js 20 LTS running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Node.js 20 LTS Container OOM Killed — Memory Limit Hit on AlmaLinux 9

PASS

Node.js 20 LTS running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Node.js 20 LTS Container OOM Killed — Memory Limit Hit on SUSE Enterprise 15 SP5

PASS

Node.js 20 LTS running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Node.js 20 LTS Container OOM Killed — Memory Limit Hit on Amazon Linux 2023

PASS

Node.js 20 LTS running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Node.js 20 LTS Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS

PASS

Node.js 20 LTS running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal

Node.js 20 LTS Container OOM Killed — Memory Limit Hit on RHEL 9

PASS

Node.js 20 LTS running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.

ServerPattern: CONTAINER_EVENTSeverity: HIGHConfidence: 68%Auto-Heal
PreviousPage 79 of 466Next

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.