socorro deploy: 2021.10.27
Categories
(Socorro :: Infra, task, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
Details
We want to do a deploy for socorro tagged 2021.10.27.
It consists of the following:
0001ce7: bug 1733910: add ERROR_NOT_ENOUGH_MEMORY as OOM indicator (willkg)
74137b4: bug 1733907: add glib functions to irrelevant list (willkg)
8f142bd: Bump django-jinja from 2.9.0 to 2.9.1 (from PR #5871) (dependabot[bot])
7371950: Bump sphinx from 4.1.2 to 4.2.0 (from PR #5872) (dependabot[bot])
988ed84: Bump black from 21.8b0 to 21.9b0 (from PR #5873) (dependabot[bot])
04b3c31: Update requirements (willkg)
7f99aa1: Update docs requirements (willkg)
058f371: Add __rust_end_short_backtrace to ignored frames (jrmuizel)
8e2b1f7: bug 1735815: add XPCOMSpinEventLoopStack to index (willkg)
bdacdb2: bug 1737643: build rust-minidump minidump-stackwalker (willkg)
f750f02: Fix releases link in README (willkg)
b37a523: bug 1737878: return normalized frames in signature result (willkg)
| Assignee | ||
Comment 1•4 years ago
|
||
Tagged:
tag 2021.10.27
Tagger: Will Kahn-Greene <willkg@mozilla.com>
Date: Wed Oct 27 10:29:16 2021 -0400
`0001ce7`: bug 1733910: add ERROR_NOT_ENOUGH_MEMORY as OOM indicator (willkg)
`74137b4`: bug 1733907: add glib functions to irrelevant list (willkg)
`8f142bd`: Bump django-jinja from 2.9.0 to 2.9.1 (from PR #5871) (dependabot[bot])
`7371950`: Bump sphinx from 4.1.2 to 4.2.0 (from PR #5872) (dependabot[bot])
`988ed84`: Bump black from 21.8b0 to 21.9b0 (from PR #5873) (dependabot[bot])
`04b3c31`: Update requirements (willkg)
`7f99aa1`: Update docs requirements (willkg)
`058f371`: Add __rust_end_short_backtrace to ignored frames (jrmuizel)
`8e2b1f7`: bug 1735815: add XPCOMSpinEventLoopStack to index (willkg)
`bdacdb2`: bug 1737643: build rust-minidump minidump-stackwalker (willkg)
`f750f02`: Fix releases link in README (willkg)
`b37a523`: bug 1737878: return normalized frames in signature result (willkg)
Deploy bug #1738043
-----BEGIN PGP SIGNATURE-----
iQEzBAABCgAdFiEEzY3I6/E2Vh8o9nPoGL3RpvBm7BEFAmF5YjwACgkQGL3RpvBm
7BFCgwgArh2cp4GtudXzzRrN4zy6NCPTHWEMADi4/jOfn+69JhwwDf25EJCm48Zr
bKhm3976wljSe1g9mQRg366rdp1RO2mQxdmGi/1v5Hnfs3UJj7jYsx24KlhnKwdC
hoU/Lrh+XWuSJn5Ijxb0naWUTitCCf/5tBGLhqllo/SdJB9OBIo7cKjgyK9nrxYa
7crarMfGk4SklSQTOpa8v71Ah7CClL+/abSRv+SmplUhqWWzavVJQovK9Eun51SR
GVqGkAR9I6PY+z3EYr/e9oAxrna5FctqigqAm9fVWFhCvmAq+EXNqD+Y6TX/WVQR
J+jwBSh6fLj6+kKfoCvEUhPzsMG1UQ==
=r0k7
-----END PGP SIGNATURE-----
commit b37a523681cf87b520d89f88c09da4304ede25b3 (HEAD -> main, tag: 2021.10.27, official/main)
Author: Will Kahn-Greene <willkg@mozilla.com>
Date: Tue Oct 26 16:20:50 2021 -0400
bug 1737878: return normalized frames in signature result
This tweaks signature generation such that if the CSignatureRule
generates normalized versions of the frames in order to build the
signature, it returns those frames in `result.extra["normalized_frames"]`.
Notes for future me: the normalized frames were already in
`result.extra["proto_signature"]` as a pipe-delimited mess. If someone
needed individual frames, splitting that string isn't safe since frames
can have pipes in them because everything is awesome.
While I was doing that, I also fixed the verbose output and
markdown-formatted output of the signature command.
| Assignee | ||
Comment 2•4 years ago
|
||
I went through and verified the bugs. Everything looks good. Marking as FIXED.
Description
•