New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 763170 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit 16 days ago
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

arc++ th presubmit provision failure: unknown filesystem type 'squashfs'

Project Member Reported by sbasi@chromium.org, Sep 7 2017

Issue description

I tried the new arc++ provision flow and it hit a snag:

 ./site_utils/run_suite.py --board=reef --pool=arc-presubmit --build=reef-release/R63-9917.0.0 --suite_name=dummy_server --cheets_build=git_nyc-mr1-arc/cheets_x86-user/4321890

Suite job: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=140423808

Test job:
http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=140423819


Provision error:

09/07 16:10:31.276 INFO |provision_CheetsUp:0123| Running push to device:
09/07 16:10:31.277 INFO |provision_CheetsUp:0126| python3 /usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py --use-prebuilt-file /tmp/tmpS5FnkY/cheets_x86-img-4321890.zip --simg2img /usr/bin/simg2img chromeos2-row7-rack6-host9
09/07 16:10:40.471 ERROR|provision_CheetsUp:0134| Error while executing python3 /usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py --use-prebuilt-file /tmp/tmpS5FnkY/cheets_x86-img-4321890.zip --simg2img /usr/bin/simg2img chromeos2-row7-rack6-host9
09/07 16:10:40.473 ERROR|provision_CheetsUp:0135| mount: unknown filesystem type 'squashfs'
ERROR:root:Error while executing /usr/bin/sudo /bin/mount -o loop /tmp/tmphv413hga/system.raw.img /tmp/tmp9ahuc3ju
ERROR:root:None
Traceback (most recent call last):
  File "/usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py", line 1052, in <module>
    main()
  File "/usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py", line 1008, in main
    out, product, fingerprint = provider.prepare()
  File "/usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py", line 796, in prepare
    _extract_artifact(self._simg2img, out_dir, self._prebuilt_file)
  File "/usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py", line 589, in _extract_artifact
    mnt_dir.name):
  File "/usr/local/autotest/server/site_tests/provision_CheetsUpdate/push_to_device.py", line 164, in __enter__
    self._image_path, self._mountpoint)
  File "/usr/local/autotest/server/site_tests/provision_CheetsUpdate/lib/util.py", line 40, in check_call
    return subprocess.check_call(subprocess_args, **kwargs)
  File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '('/usr/bin/sudo', '/bin/mount', '-o', 'loop', '/tmp/tmphv413hga/system.raw.img', '/tmp/tmp9ahuc3ju')' returned non-zero exit status 32

09/07 16:10:40.474 DEBUG|              test:0389| Test failed due to Pushing Android test build failed due to: mount: unknown filesystem type 'squashfs'
ERROR:root:Error while executing /usr/bin/sudo /bin/mount -o loop /tmp/tmphv413hga/system.raw.img /tmp/tmp9ahuc3ju



Not surprising that we hit a bug in production, it actually got pretty far which is a good sign.
 
Cc: rohi...@chromium.org yusukes@chromium.org
Owner: lhchavez@chromium.org
Status: Assigned (was: Untriaged)
Status: Started (was: Assigned)
Status: Fixed (was: Started)

Sign in to add a comment