All issues

Search results

Recover corpus replay cleanup after root supervisor SIGKILL

Status: Open.

#895 In ejc3/fcvm;

· ejc3 opened on Aug 31, 2026

Runner autoscaler kills runners mid-job at the 12h age cap, and the failure reads as an AWS spot reclaim

Status: Open.

#884 In ejc3/fcvm;

· ejc3 opened on Aug 29, 2026

arm64 runner wedged: firecracker D-state in synchronize_srcu (mmu_notifier_unregister/kvm_destroy_vm) after the warm SnapshotEnabled pass

Status: Open.

#871 In ejc3/fcvm;

· ejc3 opened on Aug 28, 2026

Fuzz oracles for companion-process death and hostile host config

Status: Open.

#852 In ejc3/fcvm;

· ejc3 opened on Aug 16, 2026

Guest podman exec dies with empty conmon output: "container create failed (no logs from conmon): conmon bytes \"\""

Status: Open.

#841 In ejc3/fcvm;

· ejc3 opened on Aug 16, 2026

Self-hosted runner agents die mid-job, presenting as test failures (3x in one evening)

Status: Open.

#834 In ejc3/fcvm;

· ejc3 opened on Aug 15, 2026

Tracking: benchmark close-out + firecracker base migration

Status: Open.

#819 In ejc3/fcvm;

· ejc3 opened on Aug 14, 2026

Open work after the restore-latency round: remaining 136ms, eth0 assumptions, cache opt-outs, 7.x wedge attribution

Status: Open.

#806 In ejc3/fcvm;

· ejc3 opened on Aug 12, 2026

Kernel patch audit vs 7.0.14: NV2 crash has an upstream fix we lack; 4 patches can be dropped

Status: Open.

#770 In ejc3/fcvm;

· ejc3 opened on Aug 8, 2026

Cloud Hypervisor reboots in-process: intentional guest reboots bypass fcvm's reboot-in-place path

Status: Open.

#709 In ejc3/fcvm;

· ejc3 opened on Aug 6, 2026

Nested-test CI gaps after #630: x86 L2-over-restored-L1, vsock-integrity runner capacity, remaining re-enables

Status: Open.

#664 In ejc3/fcvm;

· ejc3 opened on Jun 11, 2026

Re-measure and re-enable the expensive nested tests (L3/L4, podman-load-over-fuse) post-#630

Status: Open.

#660 In ejc3/fcvm;

· ejc3 opened on Jun 10, 2026