Geoff Brown [:gbrown] Assignee
	Description • 6 years ago

As seen in https://bugzilla.mozilla.org/show_bug.cgi?id=1392946#c21, sometimes when things go wrong during an Android test run, the remote test log is dumped twice. That's confusing, and avoidable.

	Geoff Brown [:gbrown] Assignee
	Comment 1 • 6 years ago

https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=9ebc58925729e4003bf1c5050fa67f88900560bf

	Bob Clary [:bc] (inactive)
	Comment 3 • 6 years ago

Comment on attachment 9033948 [details] [diff] [review]
ensure remote log deleted before launching test app

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

I'm a little concerned that we might be deleting the contents of the log prior to running the app, but looking at the code where this is called, it seems that runApp is more about starting the framework which would make this ok.

r+

	Geoff Brown [:gbrown] Assignee
	Comment 4 • 6 years ago

I think all runApp clients use runApp to start the browser + generate the remote log + collect and report the remote log, so any remote log present at the start of runApp should have already been reported. If that hadn't happened somehow, it would be confusing; I'll add a "runApp deleted remote log" info log just in case.

	Pulsebot
	Comment 5 • 6 years ago

Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ba0acece312a
Ensure Android remote test log is deleted before launching test app; r=bc

	Bogdan Tara[:bogdan_tara | bogdant]
	Comment 6 • 6 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/ba0acece312a