New issue
Advanced search Search tips

Issue 665483 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

crosperf: could not run crosperf with images on trybot.

Project Member Reported by yunlian@chromium.org, Nov 15 2016

Issue description

See the log on chrotomation2.
/usr/local/google2/crostc/buildbot_tester.peppy.295217,315731.Tue.out 

OUTPUT: Preparing to download control_files.tar package to local directory.
OUTPUT: CMD: gsutil cp gs://chromeos-image-archive/peppy-chrome-pfq/R56-8991.0.0-rc1/control_files.tar /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; tar -xvf  autotest_packages.tar
(Uncompressing autotest file autotest_packages.tar .)
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; rm -f autotest_packages.tar
(Removing processed autotest file autotest_packages.tar .)
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; tar -jxvf  autotest_server_package.tar.bz2
(Uncompressing autotest file autotest_server_package.tar.bz2 .)
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; rm -f autotest_server_package.tar.bz2
(Removing processed autotest file autotest_server_package.tar.bz2 .)
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; tar -xvf  control_files.tar
(Uncompressing autotest file control_files.tar .)
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; rm -f control_files.tar
(Removing processed autotest file control_files.tar .)
OUTPUT: CMD: cd /tmp/peppy-chrome-pfq/R56-8991.0.0-rc1 ; mv autotest autotest_files
(Moving downloaded autotest files to autotest_files)
OUTPUT: Acquiring checksum for 'nonafdo_image'.
df6af0887b895ae968b3421207c13e03  /usr/local/google2/crostc/chromeos/chroot/tmp/peppy-chrome-pfq/R56-8991.0.0-rc1/chromiumos_test_image.bin
OUTPUT: Computed checksum is : df6af0887b895ae968b3421207c13e03
OUTPUT: Checksum is: df6af0887b895ae968b3421207c13e03
OUTPUT: Preparing to download trybot-peppy-release/R56-8992.0.0-b7189 image to local directory.
OUTPUT: CMD: gsutil cp gs://chromeos-image-archive/trybot-peppy-release/R56-8992.0.0-b7189/chromiumos_test_image.tar.xz /tmp/trybot-peppy-release/R56-8992.0.0-b7189
OUTPUT: CMD: cd /tmp/trybot-peppy-release/R56-8992.0.0-b7189 ; tar -Jxf chromiumos_test_image.tar.xz
(Uncompressing and un-tarring may take a couple of minutes...please be patient.)
OUTPUT: CMD: cd /tmp/trybot-peppy-release/R56-8992.0.0-b7189 ; rm -f chromiumos_test_image.tar.xz;
(Removing file chromiumos_test_image.tar.xz.)
OUTPUT: Using image from /usr/local/google2/crostc/chromeos/chroot/tmp/trybot-peppy-release/R56-8992.0.0-b7189/chromiumos_test_image.bin.
Crosperf error: MissingFile('Cannot find autotest package file: autotest_packages.tar.',)
Traceback (most recent call last):
  File "./buildbot_test_toolchains.py", line 392, in <module>
    retval = Main(sys.argv)
  File "./buildbot_test_toolchains.py", line 388, in Main
    return fc.DoAll()
  File "./buildbot_test_toolchains.py", line 330, in DoAll
    self._TestImages(trybot_image, vanilla_image, nonafdo_image)
  File "./buildbot_test_toolchains.py", line 229, in _TestImages
    raise RuntimeError('Crosperf execution error!')
RuntimeError: Crosperf execution error!

 
This error means server chromeos-image-archive/trybot-peppy-release/R56-8992.0.0-b7189/ did not have this file. 

Comment 2 by cmt...@chromium.org, Nov 15 2016

That is correct; we need to update crosperf so that it's not a fatal error if the autotest_packages.* files are not there.

Comment 3 by cmt...@chromium.org, Nov 15 2016

Or we need to change the way the trybot images are generated so that they generate/upload the autotest packages...

Comment 4 by cmt...@chromium.org, Nov 15 2016

From a little investigation, it looks like our nightly performance test trybot images are not generating/uploading the autotest packages because we run them with the --notests flag (to not run any HWTests and finish faster).  I think we want to keep doing that, so we need to update crosperf to not make this a fatal error.

Comment 5 by cmt...@chromium.org, Nov 15 2016

You should probably issue a warning log message in this case, so if the user is trying to run a test that requires an autotest package, he/she can at least look at the log and figure out what went wrong...
Another option is to specify an autotest directory in the experiment file. Then no attempt will be made to download packages.
Owner: manojgupta@chromium.org

Comment 8 by cmt...@chromium.org, Nov 15 2016

That will solve the current problem with the nightly tests, but I still think that it would be best if, in the absence of such an option, if the autotest packages cannot be downloaded crosperf should issue a warning to the user and fall back on trying to use ~/src/third_party/autotest.
Project Member

Comment 9 by bugdroid1@chromium.org, Nov 16 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/toolchain-utils/+/ac9bd776a41cc591eb47c9d588f236a9aeb7b218

commit ac9bd776a41cc591eb47c9d588f236a9aeb7b218
Author: Manoj Gupta <manojgupta@google.com>
Date: Tue Nov 15 21:47:52 2016

Yunlian, Is this still a problem?
Status: Verified (was: Untriaged)
No, thanks.
Status: Fixed (was: Verified)

Comment 13 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58
Status: Verified (was: Fixed)

Sign in to add a comment