You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would perhaps be useful to keep the memory test running even after errors are found.
For example I only saw bit 2 to be broken after running the test several times, swapped out the chip and bit 2 is not broken anymore. But now bit 5 gives errors after a longer period of running. I would have been nice to catch both of those on one go.
The text was updated successfully, but these errors were encountered:
Well... maybe, I'm not sure how common this would be, really. Also in larger memory systems you would not know which memory area caused which bit error. Unless I updated the reporting, somehow.
It would perhaps be useful to keep the memory test running even after errors are found.
For example I only saw bit 2 to be broken after running the test several times, swapped out the chip and bit 2 is not broken anymore. But now bit 5 gives errors after a longer period of running. I would have been nice to catch both of those on one go.
The text was updated successfully, but these errors were encountered: