can't figure out 'repo upload' error message

47 views
Skip to first unread message

Juan Ramon Martinez

unread,
Feb 1, 2016, 5:54:52 PM2/1/16
to chromiu...@chromium.org
Hi 
I have been getting this error message every time I run repo upload: 

juanramon@juanramon0:~/chromiumos/src/third_party/autotest/files/client$ repo upload .
Repo must run the script:
  /usr/local/google/home/juanramon/chromiumos/src/repohooks/pre-upload.py

Do you want to allow this script to run (yes/yes-never-ask-again/NO)? yes

Errors in PROJECT *chromiumos/third_party/autotest*!
    COMMIT 2e53d374:
        Description:
            >Implement longevity test.
            >
            >BUG=chromium:579336
            >TEST=test_that longevity_Tracker
            >
            >Change-Id: I350b2e3236f7aff8527bd47d8912e5db76c62599
            >
            >
        Errors:
            * Hook script "./site_utils/presubmit_hooks/check_suite_scheduler.py" failed with code 1:
              Traceback (most recent call last):
                File "./site_utils/presubmit_hooks/check_suite_scheduler.py", line 46, in <module>
                  main()
                File "./site_utils/presubmit_hooks/check_suite_scheduler.py", line 39, in main
                  output = utils.system_output(suite_scheduler + ' --sanity')
                File "/usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/files/client/common_lib/base_utils.py", line 1196, in system_output
                  args=args).stdout
                File "/usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/files/client/common_lib/base_utils.py", line 893, in run
                  "Command returned non-zero exit status")
              autotest_lib.client.common_lib.error.CmdError: Command </usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/files/site_utils/suite_scheduler/suite_scheduler.py --sanity> failed, rc=1, Command returned non-zero exit status
              * Command: 
                  /usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/file
                  s/site_utils/suite_scheduler/suite_scheduler.py --sanity
              Exit status: 1
              Duration: 0.111357927322
              
              stderr:
              WARNING:root:Unable to import chromite.
              Traceback (most recent call last):
                File "/usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/files/site_utils/suite_scheduler/suite_scheduler.py", line 40, in <module>
                  import board_enumerator, deduping_scheduler, driver, forgiving_config_parser
                File "/usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/files/site_utils/suite_scheduler/board_enumerator.py", line 5, in <module>
                  from autotest_lib.server.cros.dynamic_suite import frontend_wrappers
                File "/usr/local/google/home/juanramon/chromiumos/src/third_party/autotest/files/server/cros/dynamic_suite/frontend_wrappers.py", line 13, in <module>
                  from chromite.lib import retry_util
              ImportError: No module named chromite.lib
              

Preupload failed due to errors in project(s). HINTS:
- To disable some source style checks, and for other hints, see <checkout_dir>/src/repohooks/README
- To upload only current project, run 'repo upload .'



I would appreciate any help solving this issue.

Juan Martinez

Aseda

unread,
Feb 1, 2016, 6:00:09 PM2/1/16
to Chromium OS dev
The error is that it can't find the chromite library. Be sure to run this command from actually entering the chroot. (`cd ~/chromiumos`, then `cros_sdk --enter`).

--
Aseda Aboagye

Mike Frysinger

unread,
Feb 1, 2016, 6:08:00 PM2/1/16
to Aseda, Chromium OS dev
yeah, currently autotest CL uploads need to be run from inside the chroot.  other repos should upload in or out.
-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en


Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages