Closed Bug 630732 Opened 14 years ago Closed 13 years ago

Talos remote does not respect logFile and fails

Categories

(Testing :: Talos, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cmtalbert, Unassigned)

Details

Attachments

(1 file)

1. Run talos remotePerfConfigurator with the command line: python remotePerfConfigurator.py -v -e org.mozilla.fennec --remoteDevice 10.250.5.102 --activeTests tp4 --sampleConfig remote.config --output tegratp4-noc-test.config --noChrome --webServer 10.250.5.14 --logFile foo.log 2. Check out your tegratp4-noc-test.config file. You'll note that the talos.logFile setting in the preference is "browser_output.txt". It ought to be foo.log. 3. Run test: python run_tests.py tegratp4-noc-test.config = Expected = Things would work and you'd get your output back in foo.log. = Actual = Instead you do get a foo.log created, and inside it you get an error. The error comes about because Talos goes looking for the browser output on the device and is looking for /sdcard/tests/foo.log. It won't find foo.log on the device, because it wasn't created due to the talos.logFile setting in the config file. You will note that /sdcard/tests/browser_output.txt does exist.
Attached patch Ok, this worksSplinter Review
Ok, I found an easy way to do this.
Attachment #508964 - Flags: review?(jmaher)
Comment on attachment 508964 [details] [diff] [review] Ok, this works in testing this it seems to work well. I recall this being a tricky thing to solve when I first did this remotely. One of the quirks is having browser_log (for getInfo) and talos.logFile (for the extensions) be synchronized. In this case, we are synchronized and all is well, but it is something too look out for.
Attachment #508964 - Flags: review?(jmaher) → review+
(In reply to comment #2) > Comment on attachment 508964 [details] [diff] [review] > Ok, this works > > in testing this it seems to work well. I recall this being a tricky thing to > solve when I first did this remotely. One of the quirks is having browser_log > (for getInfo) and talos.logFile (for the extensions) be synchronized. In this > case, we are synchronized and all is well, but it is something too look out > for. Um, ok, does this mean we can check this in? Or are we waiting for something? I don't have commit access to talos (I think) so I'll need you to do this? (The tables have turned bwahahaha).
Has this been pushed to production?
I am not sure, I can't find reference to a talos downtime in related bugs after Feb 3rd.
Okay, should it be in production? :)
Also, if we have landed the patch should this bug be closed?
Yes :)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: