Bug 144446 - [GTK] Performance bot fails to download binary
Summary: [GTK] Performance bot fails to download binary
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-30 04:31 PDT by Csaba Osztrogonác
Modified: 2015-06-01 06:05 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Osztrogonác 2015-04-30 04:31:36 PDT
It started to fail 2 days before
https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Perf%29/builds/2519

Extracting /home/slave/webkitgtk/gtk-linux-64-release-perf-tests/build/WebKitBuild/Release
Downloaded file from http://webkitgtk-release.igalia.com/built-products/release_r183625_b58076.zip to /home/slave/webkitgtk/gtk-linux-64-release-perf-tests/build/WebKitBuild/release.zip
Archive:  /home/slave/webkitgtk/gtk-linux-64-release-perf-tests/build/WebKitBuild/release.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /home/slave/webkitgtk/gtk-linux-64-release-perf-tests/build/WebKitBuild/release.zip or
        /home/slave/webkitgtk/gtk-linux-64-release-perf-tests/build/WebKitBuild/release.zip.zip, and cannot find /home/slave/webkitgtk/gtk-linux-64-release-perf-tests/build/WebKitBuild/release.zip.ZIP, period.
Comment 1 Csaba Osztrogonác 2015-05-04 01:15:08 PDT
The bot is still broken for ~ a week.
Comment 2 Martin Robinson 2015-05-04 08:09:51 PDT
Hopefully we can get this fixed soon. Sorry for the continued breakage, but the person who set this up is on vacation ATM.
Comment 3 Csaba Osztrogonác 2015-06-01 06:05:05 PDT
Somebody fixed it on 13rd May, thanks.