Fix dawn_wire_server_and_frontend_fuzzer's timeout

This was caused by DeviceNull's APITick() always returning true leading
to the Instance.ProcessEvents() polling code looping forever.

Until we fix the DeviceNull's implementation, only call
Instance.ProcessEvents() once for now.

Bug: chromium:1424846
Bug: dawn:1712
Change-Id: Ieead95230cfd9a5ee7c977a7da2a98e7486ea4ad
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/124282
Kokoro: Austin Eng <enga@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
Commit-Queue: Quyen Le <lehoangquyen@chromium.org>
diff --git a/src/dawn/fuzzers/DawnWireServerFuzzer.cpp b/src/dawn/fuzzers/DawnWireServerFuzzer.cpp
index 53e5604..2f85f17 100644
--- a/src/dawn/fuzzers/DawnWireServerFuzzer.cpp
+++ b/src/dawn/fuzzers/DawnWireServerFuzzer.cpp
@@ -134,8 +134,9 @@
     wireServer->HandleCommands(reinterpret_cast<const char*>(data), size);
 
     // Flush remaining callbacks to avoid memory leaks.
-    do {
-    } while (sInstance->ProcessEvents());
+    // TODO(crbug.com/dawn/1712): DeviceNull's APITick() will always return true so cannot
+    // do a polling loop here.
+    sInstance->ProcessEvents();
 
     // Note: Deleting the server will release all created objects.
     // Deleted devices will wait for idle on destruction.