Issue metadata
Sign in to add a comment
|
Stack traces from tests running on ASAN builds in CQ not symbolized |
||||||||||||||||||||||||
Issue description
,
Jan 9 2018
#1: we've done symbolization work elsewhere. I'd lean toward us owning it. That logdog doesn't have that when it's only from two months ago is a little concerning...
,
Jan 9 2018
As for a more recent example: perhaps https://logs.chromium.org/v/?s=chromium%2Fbb%2Ftryserver.chromium.linux%2Flinux_chromium_asan_rel_ng%2F521696%2F%2B%2Frecipes%2Fsteps%2Fbrowser_tests__with_patch_%2F0%2Flogs%2FCaptivePortalBrowserTest.InterstitialTimerCertErrorAfterSlowLoad%2F0 ? The log contains: [27758:27781:0109/092523.920241:FATAL:scoped_refptr.h(208)] Check failed: ptr_. #0 0x000007bbcf71 (/b/s/w/ir/out/Release/browser_tests+0x7bbcf70) #1 0x0000133a2e0c (/b/s/w/ir/out/Release/browser_tests+0x133a2e0b) #2 0x000013413ecc (/b/s/w/ir/out/Release/browser_tests+0x13413ecb) #3 0x00000e87c512 (/b/s/w/ir/out/Release/browser_tests+0xe87c511) #4 0x00000c8be957 (/b/s/w/ir/out/Release/browser_tests+0xc8be956) #5 0x00000bcfb4eb (/b/s/w/ir/out/Release/browser_tests+0xbcfb4ea) #6 0x000017940133 (/b/s/w/ir/out/Release/browser_tests+0x17940132) #7 0x000017949ad8 (/b/s/w/ir/out/Release/browser_tests+0x17949ad7) #8 0x0000179445cc (/b/s/w/ir/out/Release/browser_tests+0x179445cb) #9 0x000017973562 (/b/s/w/ir/out/Release/browser_tests+0x17973561) #10 0x00001797156d (/b/s/w/ir/out/Release/browser_tests+0x1797156c) #11 0x000017949ad8 (/b/s/w/ir/out/Release/browser_tests+0x17949ad7) #12 0x00001793ad6d (/b/s/w/ir/out/Release/browser_tests+0x1793ad6c) #13 0x00001793d3c8 (/b/s/w/ir/out/Release/browser_tests+0x1793d3c7) #14 0x00001793cd21 (/b/s/w/ir/out/Release/browser_tests+0x1793cd20) #15 0x00000d426df5 (/b/s/w/ir/out/Release/browser_tests+0xd426df4) #16 0x0000179b5d7a (/b/s/w/ir/out/Release/browser_tests+0x179b5d79) #17 0x0000179b7009 (/b/s/w/ir/out/Release/browser_tests+0x179b7008) #18 0x0000133a6a50 (/b/s/w/ir/out/Release/browser_tests+0x133a6a4f) #19 0x0000134397e2 (/b/s/w/ir/out/Release/browser_tests+0x134397e1) #20 0x000013432c8d (/b/s/w/ir/out/Release/browser_tests+0x13432c8c) #21 0x000013433886 (/b/s/w/ir/out/Release/browser_tests+0x13433885) #22 0x000013434201 (/b/s/w/ir/out/Release/browser_tests+0x13434200) #23 0x000013446901 (/b/s/w/ir/out/Release/browser_tests+0x13446900) #24 0x0000134315a5 (/b/s/w/ir/out/Release/browser_tests+0x134315a4) #25 0x0000134e7a4b (/b/s/w/ir/out/Release/browser_tests+0x134e7a4a) #26 0x0000135ad9b5 (/b/s/w/ir/out/Release/browser_tests+0x135ad9b4) #27 0x00000dfe9812 (/b/s/w/ir/out/Release/browser_tests+0xdfe9811) #28 0x00000dfe9e71 (/b/s/w/ir/out/Release/browser_tests+0xdfe9e70) #29 0x0000135aeb10 (/b/s/w/ir/out/Release/browser_tests+0x135aeb0f) #30 0x000013591b73 (/b/s/w/ir/out/Release/browser_tests+0x13591b72) #31 0x7fb1bee0a184 (/lib/x86_64-linux-gnu/libpthread-2.19.so+0x8183) #32 0x7fb1b8410ffd (/lib/x86_64-linux-gnu/libc-2.19.so+0xfdffc)
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 14
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sergeybe...@chromium.org
, Jan 9 2018Status: Available (was: Untriaged)