dmajor reports that the super search field "GraphicsCriticalError" added in bug 1106156 is now absent. Any idea how this could have happened? Could it be related to the AWS move (I don't know where this info is stored)
I guess it is related to the AWS move, and we didn't copy the ``socorro`` index in Elasticsearch from the PHX cluster to the AWS one. Let's get together today and fix it, that should be quite easy.
3 years ago
Fixed! Thanks :rhelmer. :)
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Thanks! Just to clarify - when I try to search now, it will let me search for "graphics critical error", rather than GraphicsCriticalError; this is OK? When I do that search and find a crash that suggests it has something in it (e.g., https://crash-stats.mozilla.com/report/index/568efdac-d523-45a5-b921-147232150623), in the past I'd see a "GraphicsCriticalError" entry in the metadata tab - now I do not. Can you check if we are doing the right thing?
The fact that the field is named "graphics critical error" is expected. I don't know about the fact that it doesn't show in the report/index/ page. Peter do know more about how that page is generated? Does it feed on the Super Search Fields list at all?
On the "Metadata" tab (on report index) it gets its fields from the same SuperSearch fields https://github.com/mozilla/socorro/blob/7fc5b6a5f396b44d392a150693f13fc9107ac7bc/webapp-django/crashstats/crashstats/views.py#L1122 It comes from https://github.com/mozilla/socorro/blob/7fc5b6a5f396b44d392a150693f13fc9107ac7bc/webapp-django/crashstats/crashstats/models.py#L1166 So yes, it depends on SuperSearch Fields.
I don't know what was concluded at this point :), but I still can't find a report that shows a graphics critical error row in the metadata tab of any crash reports. David, you can usually find anything related to crashes - maybe I'm just not searching properly. Can you find a crash report that has a graphics critical error, and does it show it in the metadata? A link to an example would be great. Thanks!
Note that it might be a matter of having the "View Personal Identifiable Information" permission too. If you view a crash (aka. report index) the list of keys under the "Metadata" table is only filtered (based on entered whitelist fields) if you DON'T have this permission. But either way, if we can find a UUID that definitely should have it I'm all ears to try to find out if or why not it's not being displayed.
Here's one from 40b1: https://crash-stats.mozilla.com/report/index/86436cff-2f44-4d1b-87a8-d61752150704#metadata GraphicsCriticalError |[GFX1]: [CompositorD3D11] error code: 0x80070057|[GFX1-]: Failed VerifyBufferSize in UpdateRenderTarget|[GFX1]: [CompositorD3D11] error code: 0x887a0001 If you're not seeing it then I'm guessing a permissions issue. Can we get this field onto the whitelist? I assume it must have been whitelisted before.
That must be it, because I'm not seeing it. Part of this bug, or do you want me to open another one?
(shrug) Might as well keep it here. Peter are you still the go-to person for whitelisting?
(In reply to David Major [:dmajor] from comment #10) > (shrug) Might as well keep it here. > > Peter are you still the go-to person for whitelisting? It's mostly Adrian or Kairo who adds them but I can help.
I can add it.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Uh. It's already in there https://crash-stats.mozilla.com/admin/supersearch-field/?name=graphics_critical_error
Created attachment 8630108 [details] Screenshot 2015-07-06 12.50.13.png I tried in Chrome, where I'm not signed in, and it's there. Resolve?
Well, I see it now as well. Wonder why it wasn't there for me an hour and a half ago...
3 years ago
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago → 3 years ago
Resolution: --- → FIXED
Same here, it didn't work for me on my not-logged-in SeaMonkey instance when I got the bugmail for comment #8, but it works now.
Thanks by the way, this helps a lot!
I'm going to guess that the fix was already on stage, and got pushed to prod just recently.
You need to log in before you can comment on or make changes to this bug.