Closed
Bug 873693
Opened 12 years ago
Closed 10 years ago
Download symbols and pass their location to the jetpack test harness
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mossop, Unassigned)
References
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2451] )
In order to fix bug 873204 we'll need to have the two places where jetpack tests are run by buildbot include some step to download the symbols and pass their path to the test harness.
Comment 1•12 years ago
|
||
FYI downloading the symbols is no longer required, you simply pass the URL in the symbol path and it's downloaded on-demand.
Reporter | ||
Comment 2•12 years ago
|
||
Ok good to know, so we just need to pass the symbol url to the jetpack harness
Reporter | ||
Comment 3•12 years ago
|
||
Unless there is some way to predict it from the Firefox build?
Comment 4•12 years ago
|
||
All the other harnesses have it passed in as a --symbols-path argument from buildbot or mozharness.
Comment 5•12 years ago
|
||
In the case of not-the-Jetpack-tree, no sweat, if you look at a log you'll see it's already doing a "set props: symbols_url" buildstep, so it's already available to pass through.
For the Jetpack tree, it's predictable, just sort of tacky, replace .dmg|.zip|.tar.bz2 with crashreporter-symbols.zip in the path of the build you download, since the symbols for http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux64/1368826242/firefox-24.0a1.en-US.linux-x86_64.tar.bz2 are at http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux64/1368826242/firefox-24.0a1.en-US.linux-x86_64.crashreporter-symbols.zip.
Fortunately, touching the code that downloads the build in http://mxr.mozilla.org/build/source/tools/buildfarm/utils/run_jetpack.py already requires that you abandon all dignity, so the tackiness isn't that big a deal. Horribly fragile, since nobody will remember that any change in the naming of symbols files will require changing that, but again, it's already horribly fragile.
Comment 6•12 years ago
|
||
On the plus side, symbol package names are based on the package basename anyway, so it's unlikely to ever break:
http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/package-name.mk#128
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2443]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2443] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2451]
Comment 7•10 years ago
|
||
I assume this will be (or already is) fixed by bug 1035512?
Updated•10 years ago
|
Blocks: sdk-test-issues
Reporter | ||
Comment 9•10 years ago
|
||
No longer needed now mochitest-jetpack is running
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•