With the info I now have, I don't think updating the expected sequence is the right approach. Since it only occurs in a full test run on testbot, my options for investigating are limited. We need to either figure out what's weird about the state when newtb-w11pro64-amd-64 runs this test, or isolate it.