Issue metadata
Sign in to add a comment
|
Not able to associate bug 776449 with an alert group |
||||||||||||||||||||||||
Issue description
I'm trying to associate a bug with a premade alert group ("bot affinity 'build92-m1', 'build93-m1', 'build95-m1' is broken on chromium.perf/Win 7 Nvidia GPU Perf, affecting 74 tests"). However, when I try to do that after creating the bug, I get the error "404 page not found". I've tried refreshing SOM and trying again to no avail.
Any idea what's happening?
,
Oct 19 2017
Interesting wrinkle: it doesn't seem restricted to linking a bug. The same thing happens if I just try to snooze the alert. Is SOM having problems right now?
,
Oct 19 2017
checking logs...
,
Oct 19 2017
I see some 404s for POST to /api/v1/annotations/bot%20affinity%20'build92-m1',%20'build93-m1',%20'build95-m1'%20is%20broken%20on%20chromium.perf%2FWin%207%20Nvidia%20GPU%20Perf,%20affecting%2074%20tests/add I think that *should* work fine. but there might be an encoding problem that confuses the request router.
,
Oct 19 2017
,
Oct 19 2017
Testing a bit. It looks like this only happens on groups with non-url-safe names. In the past, group names would have a generated hash (this doesn't change even if the group name changes) that was used as the key, which prevented this from being a problem. It looks like the autogenerated groups use the human readable name as the key. So we should probably switch them to using a separate generated key as well.
,
Oct 19 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by charliea@chromium.org
, Oct 19 2017122 KB
122 KB View Download
21.8 KB
21.8 KB View Download