buildbucket recipe module should provide sane default mock responses for recipe sim test. |
|||||||||
Issue descriptionMore than once I have broken bisect because I messed up the format of the response given by buildbucket (get, put and put_batch differences for example) If the module methods had default step_test_data that is correctly structured, this would help us avoid breakages like bug 640915.
,
Aug 26 2016
,
Sep 1 2016
Pri-2 because this seems like a nice to have for right now. Vadim, feel free to unassign yourself and mark this available if you can't do this before nodir gets back.
,
Sep 1 2016
I don't have cycles to actively add something new to buildbucket, I'm just supporting it until Nodir returns.
,
Sep 2 2016
robertocn, you created the module. Do prefer not to co-own it?
,
Feb 13 2017
Simon, how would you prioritize this?
,
Feb 14 2017
+dtu Think that bisect recipe uses the buildbucket recipe api but pretty sure Pinpoint doesn't in any way, adding Dave to confirm. So given that, super low priority on our end.
,
Feb 14 2017
Yes, Pinpoint doesn't use the buildbucket recipe module.
,
Mar 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 21 2018
nodir@ I think that's still valid. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by sullivan@chromium.org
, Aug 26 2016Components: Infra>Client>Perf