For this change:

https://chromium-review.googlesource.com/c/481042/

For this build:

https://build.chromium.org/p/tryserver.chromium.android/builders/android_blink_rel/builds/2324

Many tests were disabled before, and failed with the patch; then when those tests were re-run without the patch they failed again, so they weren't considered "new failures", so they were not rebaselined.

webkit-patch rebaseline-cl wasn't very clear about what was happening... ideally, it would have been helpful for it to note that ~300 tests failed but most of them failed again on the retry. It would also be helpful if there was an option to completely ignore the retry results, or if there was a prompt asking "rebaseline only tests that failed on the first try but not the second? (Y/n)".