1493082 - Taskcluster Windows builds aren't resolving symbols for crashes

Status: RESOLVED INACTIVE

(Testing :: Raptor, enhancement, P3)

Description

[Bob Owen (:bobowen)]

The builds on taskcluster for Windows don't seem to be resolving the symbols for crashes.

I think this might only be affecting opt builds, not sure if this happened with the move to clang.

Comment 1

[(not currently active) Ted Mielczarek]

Can you link to an example?

Comment 2

[Bob Owen (:bobowen)]

(In reply to Ted Mielczarek [:ted] [:ted.mielczarek] from comment #1)
> Can you link to an example?

Here's one I found on m-c:
https://treeherder.mozilla.org/logviewer.html#?job_id=199744795&repo=mozilla-central&lineNumber=1079

Comment 3

[(not currently active) Ted Mielczarek]

This looks like a bug in this test harness. I can see from the log that it gets a `--symbolsPath` argument that looks correct:
17:54:30     INFO - Calling ['C:\\Users\\task_1537206572\\build\\venv\\Scripts\\python', u'C:\\Users\\task_1537206572\\build\\tests\\raptor\\raptor\\raptor.py', u'--test', 'raptor-gdocs', u'--binary', 'C:\\Users\\task_1537206572\\build\\application\\firefox\\firefox.exe', u'--app', u'firefox', u'--symbolsPath', 'https://queue.taskcluster.net/v1/task/aQCrSVgiTd2BrhREtyOmwA/artifacts/public/build/target.crashreporter-symbols.zip', u'--log-tbpl-level=debug'] with output_timeout 3600

...but it doesn't seem to actually use the symbols when processing the minidump:
18:00:12     INFO -  0x7ff7fe190000 - 0x7ff7fe21bfff  firefox.exe  64.0.0.6834  (main)  (WARNING: No symbols, firefox.pdb, B0E2E90284CF618938185019144622C01)
18:00:12     INFO -  0x7ffaeaff0000 - 0x7ffaf08c6fff  xul.dll  64.0.0.6834  (WARNING: No symbols, xul.pdb, 391BF9A05254DDC10A7F5C95E755F7DF1)

The harness has the commandline option:
https://dxr.mozilla.org/mozilla-central/rev/8265be8d02b079c1d6131a2505356f770bf564df/testing/raptor/raptor/cmdline.py#26

...but doesn't seem to use it anywhere.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

All the tests will be eventually moved to browsertime, and there is bug 1585036 for adding crash analysis support. I don't think it makes sense to keep this bug open, also because there was no activity within the last year.

Comment 5

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Closing this as inactive as there have been no further reported occurrences in over a year.