Add new chromium.clang bots to perf dashboard bot whitelist |
|||||||
Issue descriptionThe bots are currently failing to upload size data, e.g. from https://uberchromegw.corp.google.com/i/chromium.clang/builders/ToTLinux/builds/26/steps/sizes/logs/stdio "HTTPError: 403. Reponse: IP address 104.154.8.147 not in IP whitelist!" eakuefner, you helped with this last time ( Bug 673497 ). Can you help again or redirect to the right person? Currently, the bots are: chromium.clang/ToTAndroid, ToTAndroid64, ToTLinux, ToTLinux (dbg), ToTLinuxASan, ToTLinuxLLD, ToTLinuxMSan, ToTLinuxThinLTO, ToTLinuxUBSanVPtr. We'll be adding more bots to this waterfall, so if you can teach me how to do this myself, that would also be great.
,
Oct 5 2017
Actually, eakuefner seems to be out. +sullivan, do you know who could help with this?
,
Oct 5 2017
Once uploaded, the perf data from these also needs to be whitelisted for being publicly visible.
,
Oct 6 2017
Dirk, sorry I missed this earlier; are these the bots you fixed?
,
Oct 6 2017
Yup, I'll take this for any of the remaining bots.
,
Oct 9 2017
Thanks! Can you point to CLs / procedure for this? It'd be great if I could do (some) of this myself for any new bots in the future.
,
Oct 9 2017
Currently you have to be an admin on the perf dashboard, so it's probably better to leave this as an ops-managed task for now. I believe we're planning to move to using service accounts for this in the relatively near future, so hopefully this will go away then as well.
,
Oct 9 2017
All of the current chromium.clang bots should be authorized, but I'm going to leave this open until I've migrated the remaining bots over as well, since they'll also need them.
,
Oct 9 2017
,
Oct 10 2017
ToTLinuxMSan seems to be missing from the whitelist: https://build.chromium.org/p/chromium.clang/builders/ToTLinuxMSan/builds/329
,
Oct 10 2017
added 104.154.8.151 for TotLinuxMSan.
,
Oct 12 2017
added 104.154.8.157 for ToTAndroid64, 104.154.8.117 for ToTLinuxASanLibfuzzer.
,
Oct 12 2017
This is hopefully done. Feel free to reopen or file a new bug if I missed something. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by h...@chromium.org
, Oct 5 2017Blocking: 765859