Test 'build_RootFilesystemSizeCoral' fails on Coral device. |
||||||||||
Issue descriptionCoral device fails with the below error message. Test details - https://sponge.corp.google.com/target?tab=Output+Files&sortBy=STATUS&show=ALL&id=cbe99991-74b0-4c87-9c42-e6d362192b32&target=coral-release/R67-10575.22.0/bvt-inline/build_RootFilesystemSize&searchFor=user:chromeos-test+build:coral-release/R67-10575.22.0+suite:bvt-inline+build_RootFilesystemSize Test failure link - https://sponge.corp.googleusercontent.com/file?invocationId=cbe99991-74b0-4c87-9c42-e6d362192b32&targetResultIndex=0&largeText=logs%2Fdebug%2Fclient.0.INFO&filename=client.0.INFO&contentType=text%2Fplain%3B%20charset%3Dutf-8&format=ansi&setTZID=America%2FLos_Angeles TestFail: 8495104 bytes free is less than the 15728640 required. Logs snapshot: 04/30 11:41:03.390 INFO | job:0200| Writing results to /usr/local/autotest/results/default 04/30 11:41:03.726 INFO | job:0232| START ---- ---- timestamp=1525113663 localtime=Apr 30 11:41:03 04/30 11:41:03.774 INFO | packages:0190| Fetching packages.checksum from http://100.115.219.132:8082/static/coral-release/R67-10575.22.0/autotest/packages to /usr/local/autotest/packages.checksum 04/30 11:41:03.813 INFO | packages:0207| Successfully fetched packages.checksum from http://100.115.219.132:8082/static/coral-release/R67-10575.22.0/autotest/packages/packages.checksum 04/30 11:41:03.903 INFO | job:0232| START build_RootFilesystemSize build_RootFilesystemSize timestamp=1525113663 localtime=Apr 30 11:41:03 04/30 11:41:03.998 INFO | packages:0190| Fetching test-build_RootFilesystemSize.tar.bz2 from http://100.115.219.132:8082/static/coral-release/R67-10575.22.0/autotest/packages to /usr/local/autotest/packages/test-build_RootFilesystemSize.tar.bz2 04/30 11:41:04.057 INFO | packages:0207| Successfully fetched test-build_RootFilesystemSize.tar.bz2 from http://100.115.219.132:8082/static/coral-release/R67-10575.22.0/autotest/packages/test-build_RootFilesystemSize.tar.bz2 04/30 11:41:04.233 INFO | test:0907| Starting before_hook for build_RootFilesystemSize 04/30 11:41:04.237 INFO | test:0911| before_hook completed 04/30 11:41:04.354 INFO | base_sysinfo:0395| ChromeOS BOARD = coral_1.1GHz_4GB 04/30 11:41:04.458 WARNI| test:0637| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/common_lib/test.py", line 631, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 495, in execute dargs) File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/build_RootFilesystemSize/build_RootFilesystemSize.py", line 59, in run_once (free, required_free_space)) TestFail: 8495104 bytes free is less than the 15728640 required. 04/30 11:41:04.480 INFO | test:0924| Starting after_hook for build_RootFilesystemSize 04/30 11:41:05.093 INFO | test:0928| after_hook completed 04/30 11:41:05.095 ERROR| parallel:0026| child process failed 04/30 11:41:05.159 INFO | job:0232| FAIL build_RootFilesystemSize build_RootFilesystemSize timestamp=1525113665 localtime=Apr 30 11:41:05 8495104 bytes free is less than the 15728640 required. 04/30 11:41:05.170 INFO | job:0232| END FAIL build_RootFilesystemSize build_RootFilesystemSize timestamp=1525113665 localtime=Apr 30 11:41:05 04/30 11:41:12.265 INFO | job:0232| END GOOD ---- ---- timestamp=1525113672 localtime=Apr 30 11:41:12
,
May 2 2018
change component and add infra deputy
,
May 2 2018
Based on history, people just keep dropping the require sizes https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/build_RootFilesystemSize/build_RootFilesystemSize.py?dr=CSs&g=0&rcl=e03af666edf65c140cadaeae1f2ecbb2fa581b63
,
May 2 2018
I can put up a quick fix, but this is an indication we may have problems if we keep growing, if coral is already near its peak model/device roll out we may be ok. I suspect if we keep adding different firmware binaries the image may run out of space again, and coral is likely the first of the 2GB rootfs systems that will break if other components grow.
,
May 2 2018
FYI we have some 5 more coral devices coming and the way pan out. May be we should limit the number different FW.
,
May 3 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/7b940dcd7f6f07e79ed2a8c054b80d9219ce63a9 commit 7b940dcd7f6f07e79ed2a8c054b80d9219ce63a9 Author: Bernie Thompson <bhthompson@google.com> Date: Thu May 03 05:21:26 2018 baseboard-coral: give coral 25MB more rootfs space Coral is starting to fail build_RootFilesystemSize, so it needs a bit more space. BUG= chromium:838749 TEST=trybot Change-Id: I840c3a208ca71ffcd2d286592894a8b576757744 Reviewed-on: https://chromium-review.googlesource.com/1039875 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: YH Lin <yueherngl@chromium.org> Reviewed-by: C Shapiro <shapiroc@google.com> [modify] https://crrev.com/7b940dcd7f6f07e79ed2a8c054b80d9219ce63a9/baseboard-coral/scripts/disk_layout.json
,
May 4 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/b1eeb26a0aff2573ec27fd3d320818ef5dc42aec commit b1eeb26a0aff2573ec27fd3d320818ef5dc42aec Author: Bernie Thompson <bhthompson@google.com> Date: Fri May 04 17:18:11 2018 baseboard-coral: give coral 25MB more rootfs space Coral is starting to fail build_RootFilesystemSize, so it needs a bit more space. BUG= chromium:838749 TEST=trybot Change-Id: I840c3a208ca71ffcd2d286592894a8b576757744 Reviewed-on: https://chromium-review.googlesource.com/1039875 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: YH Lin <yueherngl@chromium.org> Reviewed-by: C Shapiro <shapiroc@google.com> (cherry picked from commit 7b940dcd7f6f07e79ed2a8c054b80d9219ce63a9) Reviewed-on: https://chromium-review.googlesource.com/1044277 Commit-Queue: YH Lin <yueherngl@chromium.org> Tested-by: YH Lin <yueherngl@chromium.org> [modify] https://crrev.com/b1eeb26a0aff2573ec27fd3d320818ef5dc42aec/baseboard-coral/scripts/disk_layout.json
,
May 7 2018
is this check into M67 ? I still see failure https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?boards=coral&milestone=67&chromeOsVersion=&chromeVersion=&startTimeFrom=&startTimeTo=#/
,
May 7 2018
,
May 7 2018
Approving Merge for M67 Chrome OS after reviewing with bhthompson@
,
May 7 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/4f039b4a43f4d86f97e882f8e28a71c952d91467 commit 4f039b4a43f4d86f97e882f8e28a71c952d91467 Author: Bernie Thompson <bhthompson@google.com> Date: Mon May 07 17:34:33 2018 baseboard-coral: give coral 25MB more rootfs space Coral is starting to fail build_RootFilesystemSize, so it needs a bit more space. BUG= chromium:838749 TEST=trybot Change-Id: I840c3a208ca71ffcd2d286592894a8b576757744 Reviewed-on: https://chromium-review.googlesource.com/1039875 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: YH Lin <yueherngl@chromium.org> Reviewed-by: C Shapiro <shapiroc@google.com> Reviewed-on: https://chromium-review.googlesource.com/1047885 Reviewed-by: Bernie Thompson <bhthompson@chromium.org> Trybot-Ready: Bernie Thompson <bhthompson@chromium.org> Commit-Queue: Bernie Thompson <bhthompson@chromium.org> [modify] https://crrev.com/4f039b4a43f4d86f97e882f8e28a71c952d91467/baseboard-coral/scripts/disk_layout.json
,
May 7 2018
,
May 11 2018
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 15 2018
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by dchan@google.com
, May 2 2018Components: Infra>Client>ChromeOS>Build