Some GTK Release testing bots are getting stuck in the extract-test-results step. Sample output, from GTK-Release-Wayland, took 13 hours to be processed. https://build.webkit.org/#/builders/15/builds/1 unzip -q -o public_html/results/GTK-Linux-64-bit-Release-Wayland-Tests/r272466 (1).zip -d public_html/results/GTK-Linux-64-bit-Release-Wayland-Tests/r272466 (1) ** RUNNING ON BUILDMASTER ** in dir /var/buildbot/build-webkit-org argv: ['unzip', '-q', '-o', 'public_html/results/GTK-Linux-64-bit-Release-Wayland-Tests/r272466 (1).zip', '-d', 'public_html/results/GTK-Linux-64-bit-Release-Wayland-Tests/r272466 (1)'] exit status 0 Another example, GTK-Release (https://build.webkit.org/#/builders/57/builds/2). The test is still running but this step is already taking over 10 hours. Manually logging into the worker, the layout test is ~50MB zipped and <200MB unzipped. Bots affected: GTK-Linux-64-bit-Release-Tests GTK-Linux-64-bit-Release-Wayland-Tests GTK-Linux-64-bit-Release-GTK4-Tests On a side note, starting the day before the buildbot update over Feb 5th to 6th, the GTK-Linux-64-bit-Release-Build had some svn issues, requiring a manual checkout Saturday morning, as the update step through the bot was failing consistently.
This seems to be affecting non-GTK bots too: Apple-BigSur-Release-WK2-Tests: 8 hours https://build.webkit.org/#/builders/70/builds/19 WinCairo-64-bit-WKL-Release-Tests: 5 hours https://build.webkit.org/#/builders/60/builds/16
Made some changes on the server. Should be fast now. e.g.: extract-test-results in https://build.webkit.org/#/builders/15/builds/6 took 2 seconds.