You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are adding back the last batch of the [changes that were
rollbacked](c964710)
which make sure that we weren't making a lot of unnecessary calls into
the DB. By consequence the signature of multiple methods were changed to
simplified.
I also added a new tests to avoid the previous issue (the one that
caused the rollback) from ever appearing again. This tests are in its
own test class and its purpose is to check that the BadConfigError is
correctly handled when no config is found(which is the expected
bahaviour in the external and google envs)
## Tests performed in `dev` environment
This changes have been present since March 25th. Its been over one week
since then and metrics seem consistent
<img width="957" height="337" alt="image"
src="https://github.com/user-attachments/assets/1ffcdba5-9adc-434b-831e-905c4653357e"
/>
Note: Down times in fuzzing hours matches when we deployed a change into
the env.
Also no new error groups seem to be appearing in swarming, the only
notable error is one relating missing permissions for uploading a test
case, which seems unrelated
This changes have been in `dev` for quite some time and we have
successfully tested their functionality without compromising any
functionality. For example [this
Task](https://chrome-swarming.appspot.com/task?id=7743c89f08030410) was
scheduled with this changes.
---------
Co-authored-by: Diego Jardon <37823380+jardondiego@users.noreply.github.com>
Co-authored-by: Javan Lacerda <javanlacerda@google.com>
0 commit comments