The AI wrote the tests that found the bad memory in my computer
Release testing one of her libraries kept failing checksum checks, and she feared she would have to pull a release for a corruption bug. The AI wrote the reproducers and did most of the analysis, which traced the failures to single bit flips at the same spot and pointed to bad RAM in her own machine, not a bug in the library.
How it works
- Notices failed checksums in release testing
- Directs the AI, which writes all the reproducers and analyzes the failures
- The flips all land on the same bit position, pointing to her RAM
- She ends up with a reproducer that tells her within 20 minutes of booting if a boot was bad
Why it’s worth knowing
What looked like a release killing corruption bug in her software turned out to be one bad bit in her own computer’s memory.
Where it’s from
Summarized from a public post on bsky.app. See the original ↗