You need to
before you can comment on or make changes to this bug.
As I'm gardening, one of the hardest things is dealing with failures that I know will go away once the bot cycles. There's a lot of state I need to keep mentally. It's both taxing and makes it harder to focus on actual tasks. We should let you minimize failures.
Next to each failure, we should have a text box that lets you insert either a time or a revision number. Until we hit that time, or all bots have run that revision, we minimize that failure (e.g. show a drop-down arrow so you can show it again, but none of the actual content).
That way, when I rebaseline a test or rollout a patch, I can get this stuff out of my visual field while I work on more pressing things.
We could store this state in localstorage so that it survives page reloads.
I think we already have all the information we need for this, so it's a strictly JS side change.
+1. I've definitely wanted some way to annotate or otherwise hide things I've already looked at.
Oh, that's a nice idea. We originally wanted to do something like this, but we didn't have the idea of having the user enter a revision number.