Closed Bug 1306502 Opened 8 years ago Closed 8 years ago

Make these "unzip: cannot find zipfile directory in one of mozharness.zip" failures starrable on treeherder

Categories

(Taskcluster :: General, defect)

Product:
Taskcluster
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1307177

People

(Reporter: KWierso, Assigned: dustin)

References

(Depends on 1 open bug)

Details

I'm seeing several failures like https://treeherder.mozilla.org/logviewer.html#?job_id=4249878&repo=autoland#L0-L135 and Treeherder isn't able to parse a failure out of the logs. Looks like it's failing in extracting mozharness.zip?

The line that should probably be highlighted is:
unzip:  cannot find zipfile directory in one of mozharness.zip or mozharness.zip.zip, and cannot find mozharness.zip.ZIP, period. 

Not sure if this is a mozharness bug or a taskcluster bug, though.
I'm moving this to TaskCluster since it is not a Mozharness bug.
I believe this is related to bug 1306189 where we download properly a zip file, however, it's corrupted on S3 (?).

Mozharness logs add ERROR when we try to get TH's log parsing's attention, however, the unzipping of mozharness happens in the TaskCluster scripts that invoke Mozharness.

Maybe a || echo "ERROR: Failed to unzip Mozharness" might be sufficient.
Component: Mozharness → General
Product: Release Engineering → Taskcluster
QA Contact: jlund
Version: unspecified → Trunk
This will not be an issue once bug 1286900 and its follow-ons land, and we are no longer copying tests.zip or mozharness.zip around to testers.
Depends on: 1286900
That said, the suggestion in the last line of comment 0 is a good stopgap :)
Assignee: nobody → dustin
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.