Found this while peeking into the generated code: the arbiters code is not `synchronized` for sync tests, although it should match what other threads are doing. This seems to be innocuous on current platforms, because arbiter always runs "last" with the relevant volatile sychronization. This is not guaranteed to work generally, though.