A register-write test wants an error-injecting driver, which corrupts one bit of every write so the DUT’s write-parity checker gets exercised. It swaps drivers with a factory type override, base_write_driver -> error_inject_write_driver, so the env never needs to know the variant exists.
Right nowThe test believes it configured the error-injecting driver, but env.drv is still a plain base_write_driver.
Fix the code so env.drv is an error_inject_write_driver.
One working answer: brokenbench's own fix for this exercise. Try a few runs first.
What changes, against the code you started with:
docker run --pull always --rm -p 127.0.0.1:8787:8787 ghcr.io/adibis/brokenbench-runnerLooking for a runner on this computer…
The first start downloads about 250 MB; after that it starts in seconds and only downloads again when there's an update. Your code goes to the runner on your computer, not to chipdv.io.