Twitter/X

Author asked Codex to set GPUs to 2; Codex generated a unit test asserting…

2026-07-28 · 22:45 UTC ·@jxmnop ·0 min read

Brief

Jack Morris shows a short interaction where he asks Codex to set GPUs to 2; Codex emits a pytest that checks config.num_gpus is an int equal to 2 and the test runs successfully. He warns that Codex’s verbose, unreadable unit tests bloat large codebases, get deleted when they fail, and leave him joking about declaring “Test Bankruptcy.”

Why it matters

Author asked Codex to set GPUs to 2; Codex generated a unit test asserting config.num_gpus == 2 and the test passed locally (1 passed in 0.04s).

Key details

  • Author (Jack Morris/@jxmnop) criticizes AI-generated CPU unit-test bloat as unreadable “Neuralese,” saying failing tests are often deleted and rewritten by agents and joking about declaring “Test Bankruptcy.”
Source evidence

me: pleas set gpus to 2

codex: Sure!

  • def testsyntheticgpu_config():
  • assert config is not None
  • assert hasattr(config, "num_gpus")
  • assert isinstance(config.num_gpus, int)
  • assert config.num_gpus == 2

$ uv run pytest tests/testsyntheticgpu_config.py

============================== 1 passed in 0.04s ===============================

Jack Morris (@jxmnop)

The bloat in CPU unit tests that Codex adds to a large codebase is truly insane. it's unreadable Neuralese and whenever the tests fail agents just delete them and rewrite entirely new ones from scratch

I fear I may soon have to declare Test Bankruptcy

— https://nitter.net/jxmnop/status/2082228790537892149#m