Closed Bug 1148630 Opened 5 years ago Closed 4 years ago

Light saber builds needs to have symbols created and sent to Socorro

Categories

(Taskcluster :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nhirata, Assigned: wcosta)

References

Details

(Whiteboard: [spark])

Attachments

(2 files, 2 obsolete files)

Note: see : https://developer.mozilla.org/en-US/docs/Uploading_symbols_to_Mozillas_symbol_server
for uploading symbols to Mozilla server

Background: currently crashes from light saber builds are making it to socorro.  Without the symbols, the crash reports are not meaningful.
fyi
Flags: needinfo?(rhelmer)
Flags: needinfo?(kairo)
Flags: needinfo?(jgong)
Flags: needinfo?(bbajaj)
James, can you look into getting the symbols pushed?  bsmedberg or kairo may be a good resource for information as well as releng.  There's something in the releng scripts that pushes the symbols to the server.
Flags: needinfo?(jlal)
The way this works is changing a bit, you now need a crash-stats token instead of an SSH key to push symbols.

Ted has been working with releng on this.
Flags: needinfo?(rhelmer) → needinfo?(ted)
What are light saber builds?
Flags: needinfo?(ted)
Flags: needinfo?(kairo)
Component: General Automation → TaskCluster
Product: Release Engineering → Testing
QA Contact: catlee
Depends on: 1150681
Depends on: 1134226
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Flags: needinfo?(bbajaj)
Depends on: 1153799
Depends on: 1085557
Blocks: tc-2015-q2
Sorry it took so long, I forgot about it, but I pushed the patch for bug 1153799.
No longer depends on: 1161287
Duplicate of this bug: 1161287
Depends on: cypress
[Blocking Requested - why for this release]: Though we can have this after dogfood is made, we will probably want to have this sooner than later.

It would be time consuming to have to verify each crash and map them manually.

What it would take to do manually : 
1) getting the build id from the crash
2) downloading the dump from socorro
3) mapping the build to the task cluster build and downloading the symbols for that build
4) then using a tool mapping the dump with the symbols.

To do this for each and every crash is a bit time consuming so I'm suggesting to mark this as a blocker for the project as a whole.
blocking-b2g: --- → spark?
Whiteboard: [spark]
Depends on: 1166217
Attached file MozReview Request: bz://1148630/wcosta (obsolete) —
/r/9115 - Bug 1148630: Enable symbol upload for nightly builds.

Pull down this commit:

hg pull -r da2679eecb5b138ef29deced282474ea40ad600a https://reviewboard-hg.mozilla.org/build-mozharness
Attachment #8608114 - Flags: review?(bhearsum)
Attached file MozReview Request: bz://1148630/wcosta (obsolete) —
/r/9119 - Bug 1148630: Add support for upload symbols from docker image.

Pull down this commit:

hg pull -r d3c076b529c638f9c9140d5238ba6adeb1dfc9e8 https://reviewboard-hg.mozilla.org/gecko/
Attachment #8608115 - Flags: review?(garndt)
No longer depends on: 1166217
Comment on attachment 8608114 [details]
MozReview Request: bz://1148630/wcosta

Is there someone on the B2G Automation team that can review this? Unless it involves update server stuff, I don't think I'm an appropriate reviewer for these sort of changes.
Attachment #8608114 - Flags: review?(bhearsum)
Attachment #8608114 - Flags: review?(garndt)
Comment on attachment 8608114 [details]
MozReview Request: bz://1148630/wcosta

/r/9115 - Bug 1148630: Enable symbol upload for nightly builds.

Pull down this commit:

hg pull -r da2679eecb5b138ef29deced282474ea40ad600a https://reviewboard-hg.mozilla.org/build-mozharness
Comment on attachment 8608114 [details]
MozReview Request: bz://1148630/wcosta

I don't see anything obvious that would break here, but I'm no MH expert.  I suspect this does what you need it to.
Attachment #8608114 - Flags: review?(garndt) → review+
Comment on attachment 8608115 [details]
MozReview Request: bz://1148630/wcosta

https://reviewboard.mozilla.org/r/9117/#review7779

::: testing/docker/phone-builder/Dockerfile:1
(Diff revision 1)
> -FROM          quay.io/mozilla/builder:0.5.4
> +FROM          quay.io/mozilla/builder:0.5.5

We'll need to be careful with this since we have another patch to move to taskclusterprivate (new amis should be deployed soon after a fix goes in).  However these land, just need to make sure the right things happen.

::: testing/docker/phone-builder/VERSION:1
(Diff revision 1)
> -0.0.13
> +0.0.14

Be careful of phone builder versions as well with the move we're making to docker hub
Attachment #8608115 - Flags: review?(garndt)
Comment on attachment 8608115 [details]
MozReview Request: bz://1148630/wcosta

https://reviewboard.mozilla.org/r/9117/#review7781

Ship It!
Attachment #8608115 - Flags: review+
(In reply to Greg Arndt [:garndt] from comment #15)
> Comment on attachment 8608115 [details]
> MozReview Request: bz://1148630/wcosta
> 
> https://reviewboard.mozilla.org/r/9117/#review7779
> 
> ::: testing/docker/phone-builder/Dockerfile:1
> (Diff revision 1)
> > -FROM          quay.io/mozilla/builder:0.5.4
> > +FROM          quay.io/mozilla/builder:0.5.5
> 
> We'll need to be careful with this since we have another patch to move to
> taskclusterprivate (new amis should be deployed soon after a fix goes in). 
> However these land, just need to make sure the right things happen.
> 

This will fix the git issue.

> ::: testing/docker/phone-builder/VERSION:1
> (Diff revision 1)
> > -0.0.13
> > +0.0.14
> 
> Be careful of phone builder versions as well with the move we're making to
> docker hub

Yeah, I am aware of this.
https://hg.mozilla.org/mozilla-central/rev/dbfb81f11bf7
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
Reopening this to see why crash symbols file is not placed where it is supposed to be.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
See Also: → 1167266
So, the real problem is that mozharness info has not been updated in gecko tree yet [1]. I have no idea how this is updated, however.

[1] http://hg.mozilla.org/mozilla-central/file/010ecb3b3b25/testing/mozharness/mozharness.json
mozharness rev has been updated and things got back to normal, closing this.
Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED
Verifed: https://crash-stats.mozilla.com/report/index/0797de7c-07fb-457b-a6da-203c62150601
Status: RESOLVED → VERIFIED
Flags: needinfo?(jlal)
Flags: needinfo?(jgong)
Attachment #8608114 - Attachment is obsolete: true
Attachment #8608115 - Attachment is obsolete: true
Attachment #8619898 - Flags: review+
Attachment #8619899 - Flags: review+
blocking-b2g: spark? → 2.5?
blocking-b2g: 2.5? → ---
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: mozilla41 → ---
You need to log in before you can comment on or make changes to this bug.