Awesome--that worked super! Thank you, Henrik! I did a try run that increases the timeout to 1000 and now I'm seeing mozcrash output for Linux, macOS, and Windows. Then I removed symbols.mozilla.org symbols-url, forcing minidump-stackwalk to use the symbols that were built that should be on disk and none of the stacks are symbolicated: Linux, macOS, or Windows. https://treeherder.mozilla.org/jobs?repo=try&revision=4b1cf6306b1a19cf3867bd3aa9e392dd00b305fe Therefore, minidump-stackwalk is symbolicating stacks _solely_ with symbols it's downloading from symbols.mozilla.org. I claim this is not what we want. What we want is for mozcrash to use the symbols that were created with the build and use symbols.mozilla.org for system symbols. This will work in situations where symbols were not uploaded to symbols.mozilla.org and possibly speed up the tests a little (downloading the symbols from the build artifacts as a big zip vs. downloading individual symbols files from symbols.mozilla.org and wherever the symbols live (AWS S3 for now, but GCP GCS soon)). However, because mozcrash is currently set up to use symbols.mozilla.org for stackwalking on all platforms and crash stacks are symbolicated, I think this bug is fixed and was fixed by my fix to minidump-stackwalk's support for https on Windows. (And then that was all moot-ified by Aria's replacing minidump-stackwalk with the far superior Rust one which also works with https.) Given that, I'm going to mark this bug as FIXED and open a new bug for mozcrash should use build symbols and then degrade to symbols.mozilla.org.
Bug 1594515 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Awesome--that worked super! Thank you, Henrik! I did a try run that increases the timeout to 1000 and now I'm seeing mozcrash output for Linux, macOS, and Windows. https://treeherder.mozilla.org/jobs?repo=try&revision=64cf0beaba279d96af6c10ff9163dcc923d7f682 Then I removed symbols.mozilla.org symbols-url, forcing minidump-stackwalk to use the symbols that were built that should be on disk and none of the stacks are symbolicated: Linux, macOS, or Windows. https://treeherder.mozilla.org/jobs?repo=try&revision=4b1cf6306b1a19cf3867bd3aa9e392dd00b305fe Therefore, minidump-stackwalk is symbolicating stacks _solely_ with symbols it's downloading from symbols.mozilla.org. I claim this is not what we want. What we want is for mozcrash to use the symbols that were created with the build and use symbols.mozilla.org for system symbols. This will work in situations where symbols were not uploaded to symbols.mozilla.org and possibly speed up the tests a little (downloading the symbols from the build artifacts as a big zip vs. downloading individual symbols files from symbols.mozilla.org and wherever the symbols live (AWS S3 for now, but GCP GCS soon)). However, because mozcrash is currently set up to use symbols.mozilla.org for stackwalking on all platforms and crash stacks are symbolicated, I think this bug is fixed and was fixed by my fix to minidump-stackwalk's support for https on Windows. (And then that was all moot-ified by Aria's replacing minidump-stackwalk with the far superior Rust one which also works with https.) Given that, I'm going to mark this bug as FIXED and open a new bug for mozcrash should use build symbols and then degrade to symbols.mozilla.org.