Closed Bug 715193 Opened 8 years ago Closed 8 years ago

Android should allow testing talos.zip changes through the try server

Categories

(Release Engineering :: General, defect, P2, blocker)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: k0scist, Assigned: armenzg)

Details

(Whiteboard: [mobile][testing])

Attachments

(3 files, 1 obsolete file)

http://armenzg.blogspot.com/2011/12/taloszip-talosjson-and-you.html is a great step forward in make Talos testable cross-platform.  However, :jmaher has pointed out that the android automation does not use this file for fetching Talos.  It should.  We currently have no staging environment that runs android :/
Armen: is this something you could take on? You deployed the other talos.json parts, and I don't think Android should be an afterthought here.
Assignee: nobody → armenzg
Priority: -- → P3
Whiteboard: [mobile][testing]
the mobile stuff is very much out of band from desktop, this might not be a simple fix.
It's completely different. IIRC the foopy checkouts the talos repo and the tegras grab it from there. Perhaps we could modify the foopy to checkout up to a given tag.

It can be independent of the talos.json or we could add a tag value inside of talos.json.

bear, aki: sounds doable?
Our workflow for talos and try is to run a set of changes we are planning on landing on try server before landing them.  So we would need to do something else other than "hg pull <tag>".
hrmmm... you're right. I don't know much about the setup on the tegras. I'll have to learn!
Priority: P3 → P2
hehe I just saw that this was mentioned in the mobile testing notes.

https://wiki.mozilla.org/Mobile/Testing/01_25_12

So I guess it is important!
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #6)
> hehe I just saw that this was mentioned in the mobile testing notes.
> 
> https://wiki.mozilla.org/Mobile/Testing/01_25_12
> 
> So I guess it is important!

it's huge!
I am giving higher priority to bug 723667.
I will get to this as soon as the other is on track to be fixed.

These are the two bugs that I am working on "P2".
With http://hg.mozilla.org/build/buildbotcustom/rev/d65002e32e87 we are close to this since we already use the talos.zip.
It is now a matter to start using talos.json.

(unrelated work, I have to fix bug 734221 first)
This is now my highest priority unless there is any follow up from bug 734221.
Priority: P2 → P1
Summary: android on try should use the talos.json file → Android jobs should take advantage of talos.json and talos_from_code.py
A couple of days before I can work on this full on.
Priority: P1 → P2
I wanted to extend talos_from_code.py and talos.json to download many other pieces but for now let's just focus on talos.zip and empower jhammel.

I will test this on Monday.
It seems I need a python with simplejson on the foopies.
I'm ok with installing simplejson if |import json| doesnt' work for you.
The foopies aren't puppetized iirc, so that'll take a csshX call or something.
This has worked for me.
I modified the steps to be retrying and testing it once more on staging.

Nothing is needed to be deployed on the foopies since they have python 2.6 on them and the json module can be imported.
Attachment #608814 - Attachment is obsolete: true
Carrying forward jmaher's review in bug 738685 to match mobile and desktop talos.zip in preparation for this buildbotcustom patch.

This could help us catch any discrepancies ahead of time.

http://hg.mozilla.org/integration/mozilla-inbound/rev/30bdb43d4a4a
Attachment #609427 - Flags: review+
Attachment #609427 - Flags: checked-in+
Comment on attachment 609413 [details] [diff] [review]
[buildbotcustom] use talos_from_code.py to retrieve talos.zip

python /builds/tegra-022/talos-data/buildfarm/utils/retry.py -s 1 -r 5 -t 1260 wget --no-check-certificate http://hg.mozilla.org/mozilla-central/raw-file/8042c37b8100/testing/talos/talos_from_code.py

python /builds/tegra-022/talos-data/buildfarm/utils/retry.py -s 1 -r 5 -t 1260 /opt/local/bin/python talos_from_code.py --talos-json-url http://hg.mozilla.org/mozilla-central/raw-file/8042c37b8100/testing/talos/talos.json
Attachment #609413 - Flags: review?(aki)
Comment on attachment 609413 [details] [diff] [review]
[buildbotcustom] use talos_from_code.py to retrieve talos.zip

>+        elif (platform.find("android") > -1):

I think we usually do |if 'android' in platform:| but this works too.

Looks good; does it work?
Attachment #609413 - Flags: review?(aki) → review+
It does work. The string was tegra_android and I thought of making it general for when we have panda_android.
Comment on attachment 609413 [details] [diff] [review]
[buildbotcustom] use talos_from_code.py to retrieve talos.zip

70e92b0482f4
Attachment #609413 - Flags: checked-in+
this was deployed during a reconfig today
I filed bug 739721 to deal with other changes that can make use of talos.json

With regards to talos.zip we are done.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Summary: Android jobs should take advantage of talos.json and talos_from_code.py → Android should allow testing talos.zip changes through the try server
It seems we broke this for mozilla-esr10. Patch coming.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Still waiting to see a passing run on staging before asking for review.
FTR, this is the problem:

python /builds/tegra-234/talos-data/buildfarm/utils/retry.py -s 1 -r 5 -t 1260 wget --no-check-certificate http://hg.mozilla.org/releases/mozilla-esr10/raw-file/578cf13bf0cb/testing/talos/talos_from_code.py
 in dir /builds/tegra-234/test/../talos-data (timeout 1320 secs)
 watching logfiles {}
 argv: ['python', '/builds/tegra-234/talos-data/buildfarm/utils/retry.py', '-s', '1', '-r', '5', '-t', '1260', 'wget', '--no-check-certificate', 'http://hg.mozilla.org/releases/mozilla-esr10/raw-file/578cf13bf0cb/testing/talos/talos_from_code.py']
 environment:
  PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-234/talos-data
  SUT_IP=10.250.51.74
  SUT_NAME=tegra-234
  __CF_USER_TEXT_ENCODING=0x1F5:0:0
 closing stdin
 using PTY: False
retry: Calling <function run_with_timeout at 0x10c84fe60> with args: (['wget', '--no-check-certificate', 'http://hg.mozilla.org/releases/mozilla-esr10/raw-file/578cf13bf0cb/testing/talos/talos_from_code.py'], 1260, None, None, False, True), kwargs: {}, attempt #1
Executing: ['wget', '--no-check-certificate', 'http://hg.mozilla.org/releases/mozilla-esr10/raw-file/578cf13bf0cb/testing/talos/talos_from_code.py']
--2012-03-28 12:11:37--  http://hg.mozilla.org/releases/mozilla-esr10/raw-file/578cf13bf0cb/testing/talos/talos_from_code.py
Resolving hg.mozilla.org (hg.mozilla.org)... 10.2.74.153
Connecting to hg.mozilla.org (hg.mozilla.org)|10.2.74.153|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-03-28 12:11:44 ERROR 404: Not Found.
Comment on attachment 610273 [details] [diff] [review]
[buildbotcustom] use talos.json method if talos_from_source_code is enabled

It looks good on staging.
Attachment #610273 - Flags: review?(aki)
Comment on attachment 610273 [details] [diff] [review]
[buildbotcustom] use talos.json method if talos_from_source_code is enabled

>+            else:
>+                self.addStep(RetryingShellCommand(
>+                 name='get_talos_zip',
>+                 command=['wget', '-O', 'talos.zip', '--no-check-certificate',
>+                          'http://build.mozilla.org/talos/zips/talos.bug738685.c08bb14e71cd.zip'],

For this else, wouldn't it be easier to point at a known-named softlink?
If we're planning on only needing this fallback for a very short amount of time, this is fine, otherwise the known-named softlink would help us deploy new talos zips (manually) without a reconfig.
Attachment #610273 - Flags: review?(aki) → review+
esr-10 is closed.
Severity: normal → blocker
I will deploy it now.
Comment on attachment 610273 [details] [diff] [review]
[buildbotcustom] use talos.json method if talos_from_source_code is enabled

I added a talos.mobile.old.zip symlink. This is needed for old branches like esr10 and 1.9.2.

http://hg.mozilla.org/build/buildbotcustom/rev/158a3faf1adf

I have reconfigured and I am now triggering the jobs.
Attachment #610273 - Flags: checked-in+
I don't know what's going on. remotePerfConfigurator.py is failing:

> python remotePerfConfigurator.py -v -e org.mozilla.firefox -t tegra-152 --branchName Mozilla-Esr10 --resultsServer graphs.mozilla.org --resultsLink /server/collect.cgi --activeTests tsspider --noChrome --symbolsPath ../symbols --remoteDevice 10.250.50.62 --sampleConfig remote.config --output local.yml --webServer bm-remote.build.mozilla.org --browserWait 60
> remotePerfConfigurator.py: ERROR: Unable to connect to remote device '10.250.51.87'

https://tbpl.mozilla.org/php/getParsedLog.php?id=10472433&tree=Mozilla-Esr10&full=1
I see green.
https://tbpl.mozilla.org/php/getParsedLog.php?id=10473964&tree=Mozilla-Esr10&full=1

I changed the symlink to the latest talos.zip to fix comment 33 as per jmaher's suggestion (the previous talos.zip was a bad one I chose).
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.