Revert "update_chroot: delete stale .pyc files from chromite"
This reverts commit e4be5613111d43fece00d51757213d975010834a.
Reason for revert: Seems to be causing more pain than it's worth
currently. The most common reason for this (stale httplib2) we've
probably cleaned up now from most user's systems.
Original change's description:
> update_chroot: delete stale .pyc files from chromite
>
> Leftover .pyc files can confuse Python when importing modules. We
> already do this in run_tests in chromite, but not everyone does
> that. update_chroot may be the best spot to add another one of these.
>
> BUG=chromium:1017859
> TEST=pyc files deleted from chromite when running ./update_chroot
>
> Cq-Depend: chromium:1879705
> Change-Id: I8e37577b722ba1ae002a83fe47f9e3eb6bb4ea69
> Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosutils/+/1879515
> Reviewed-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium:1017859, chromium:1022007
Change-Id: I157512303bd8fce6de8e4bcf587539d91ce7bec6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosutils/+/1911232
Reviewed-by: Sean Abraham <seanabraham@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
diff --git a/update_chroot b/update_chroot
index 01bd546..8fc4dff 100755
--- a/update_chroot
+++ b/update_chroot
@@ -42,12 +42,6 @@
# so will die prematurely if 'switch_to_strict_mode' is specified before now.
switch_to_strict_mode
-# Before using chromite, we need to delete any stale .pyc files from
-# the chromite directory. This is because bugs like crbug.com/1017859
-# can happen when things get moved and the .gitignore'd .pyc files are
-# still there.
-"${GCLIENT_ROOT}/chromite/scripts/run_tests" --clear-pycache
-
. ${SCRIPTS_DIR}/sdk_lib/make_conf_util.sh
# Run version hooks as pre-update
