diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2023-01-19 14:28:01 +0100 |
|---|---|---|
| committer | Aleksandr Nogikh <wp32pw@gmail.com> | 2023-01-19 16:56:30 +0100 |
| commit | 7cec19129d29eb6e3a6559bcebb46bd4097f080b (patch) | |
| tree | b8b62ee1af87e862e82599efdaa8751af62cddcf /executor/style_test.go | |
| parent | 7990722a6099be6cb949b042064f62b1ecad997b (diff) | |
dashboard: handle decommissioned managers in repro retesting
Especially for old bugs, it's likely that the corresponding syz-manager
instance has already been deprecated.
The current code creates a patch testing job for the old repository, but
then only accepts the result if the repository is equal to that of the
new syz-manager instance. As a result, patch retesting goes crazy and
creates many unnecessary jobs.
Take the repo and branch data for the currently active syz-manager right
away. This should resolve the issue.
Add a test to verify the behavior.
Diffstat (limited to 'executor/style_test.go')
0 files changed, 0 insertions, 0 deletions