devicemanagerADB pushDir fallback doesn't always work

RESOLVED FIXED in Firefox 12

Status

()

Firefox for Android
General
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: cwiiis, Assigned: cwiiis)

Tracking

Trunk
Firefox 12
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
On both my devices, running the reftest-remote target (as described here: https://wiki.mozilla.org/Mobile/Fennec/Android#Reftests) fails due to unzip not being present on the device (or not working). The current devicemanagerADB.py script fails to detect this and bails out, but the fallback path works fine.
(Assignee)

Comment 1

6 years ago
Created attachment 591061 [details] [diff] [review]
Fix devicemanagerADB.py pushDir fallback

This patch allows me to run reftests locally by making sure the fallback path is always tried before bailing out.
Attachment #591061 - Flags: review?(gbrown)
Comment on attachment 591061 [details] [diff] [review]
Fix devicemanagerADB.py pushDir fallback

Review of attachment 591061 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks Chris - that's a good change. 

Out of curiosity, what was causing the exception for you?
Attachment #591061 - Flags: review?(gbrown) → review+
(Assignee)

Comment 3

6 years ago
Not sure what the error was, my python foo isn't good enough and I can't quickly find any documentation for the CalledProcessError object...

That said, I think it was just that the device doesn't have an unzip binary.

Pushed to inbound: http://hg.mozilla.org/integration/mozilla-inbound/rev/63db726e7634
Status: NEW → ASSIGNED
Whiteboard: [inbound]
https://hg.mozilla.org/mozilla-central/rev/63db726e7634
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
Target Milestone: --- → Firefox 12

Updated

6 years ago
Keywords: fennecnative-betablocker

Updated

6 years ago
Keywords: fennecnative-betablocker
You need to log in before you can comment on or make changes to this bug.