include a .pyc cleanup in prod pushes |
||||
Issue descriptionA recent sysmon outage on one server (chromeos-gt-devserver13) was due to stale .pyc files in chromeos-test's checkout of chromite. Each time this requires manual intervention, it is expensive and slow because blaming .pyc files is among the last things to occur to try. Maybe we should clean these files up either periodically, or upon prod pushes.
,
Sep 29
https://chromium.googlesource.com/chromiumos/third_party/autotest/+/086df1c4432d49da65333838893d6ca8a5f9ae06/site_utils/deploy_server_local.py#188 Huh, we do cleanup pyc when we sync the chromiumos checkout during push.
,
Sep 29
I don't think I ever dug into the original problem (both due to the estimated time investment and due to being not reproducible and leaving behind no trace), but I don't think the original issue is due to stale .pyc files. There have been a few cases of AttributeError when 1. that name is clearly defined in the module. 2. that name was not touched, added, or removed recently (hence it shouldn't be a stale .pyc from before when that name was added.)
,
Oct 1
,
Oct 5
,
Oct 25
|
||||
►
Sign in to add a comment |
||||
Comment 1 by zamorzaev@chromium.org
, Sep 24Owner: ayatane@chromium.org