Setting P1 since this is blocking us in the LUCI emulation experiment from getting things done using the normal workflow (now we have to manually push all CLs).

I guess [1] is the vpython used and that the python-psutil simply needs to be installed and auto-rolled into the buildbot environment. It's not clear to me how to do this though - I can't find the right .spec file in my infra checkout...

machenbach: have you faced similar issue or knows how to update vpython?

[1]: https://chromium.googlesource.com/external/github.com/luci/luci-go/+/master/vpython/

Didn't experience this. But we also didn't do LUCI emulation. We just switch from normal remote-run to real LUCI directly.

Took a guess at a fix in https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/641472

iannucci@ and I are working on this as part of a larger effort to roll out hermetic Python bundles. ETA is this Thursday.

Thanks for the information dnj@, that sounds promising. I'll check back on Friday then.

The problem went away without any action from us (around 30 Aug).

I'm still seeing the same psutil problem. Ran a new tryjob today:
https://build.chromium.org/p/tryserver.webrtc/builders/mac_baremetal/builds/24575

We didn't do anything yet, so it shouldn't have changed.

The NextAction date has arrived: 2017-09-01

dnj: can you provide an update on the progress. I noticed https://bugs.chromium.org/p/chromium/issues/detail?id=741001#c29 does add psutil to the Python environment, but I guess it's not rolled out to bots yet? (since my tryjob from today failed: https://build.chromium.org/p/tryserver.webrtc/builders/mac_baremetal/builds/24610)

I failed to find a good block of time to do this yesterday. Hoping to be able to do it today.

So, now we're getting this error not only in LUCI emulation. Commit queue is blocked on failures like this: https://build.chromium.org/p/tryserver.webrtc/builders/android_rel/builds/27452/steps/android_junit_tests

I will disable this step for now :(

We did land the change on Friday, and it did fix things IIRC. However, we were forced to revert it for another reason :( Round two this week.

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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot