See an example build:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/veyron_minnie-tot-chrome-pfq-informational/builds/7425
The earliest failed build I can track is https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/veyron_minnie-tot-chrome-pfq-informational/builds/7161
See selected error message:
03/05 13:10:26.328 INFO | fake_printer:0028| waiting for a printing request
03/05 13:10:26.376 DEBUG| test:0379| Starting before_iteration_hooks for platform_AddPrinter
03/05 13:10:26.378 DEBUG| base_sysinfo:0175| Loggable runs cmd: /opt/google/chrome/chrome --version
03/05 13:10:26.380 DEBUG| global_hooks:0056| '/opt/google/chrome/chrome --version'
03/05 13:10:26.449 DEBUG| base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_AddPrinter/sysinfo/iteration.1/interrupts.before
03/05 13:10:26.451 DEBUG| base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_AddPrinter/sysinfo/iteration.1/schedstat.before
03/05 13:10:26.452 DEBUG| base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_AddPrinter/sysinfo/iteration.1/meminfo.before
03/05 13:10:26.455 DEBUG| base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_AddPrinter/sysinfo/iteration.1/slabinfo.before
03/05 13:10:26.472 DEBUG| global_hooks:0056| 'ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq'
03/05 13:10:26.493 INFO | base_sysinfo:0395| ChromeOS BOARD = veyron_minnie_1.8GHz_4GB
03/05 13:10:26.496 DEBUG| utils:0214| Running 'logger "autotest starting iteration /usr/local/autotest/results/default/platform_AddPrinter/sysinfo/iteration.1 on veyron_minnie_1.8GHz_4GB"'
03/05 13:10:26.497 DEBUG| global_hooks:0056| 'logger "autotest starting iteration /usr/local/autotest/results/default/platform_AddPrinter/sysinfo/iteration.1 on veyron_minnie_1.8GHz_4GB"'
03/05 13:10:26.540 DEBUG| test:0384| before_iteration_hooks completed
03/05 13:10:26.541 DEBUG| test:0399| starting test(run_once()), test details follow
()
03/05 13:10:26.542 INFO |platform_AddPrinte:0109| add printer from ppd:/tmp/GenericPostScript.ppd.gz
03/05 13:10:27.241 DEBUG| utils:0214| Running 'lp -d FakePrinterID /usr/local/autotest/tests/platform_AddPrinter/to_print.pdf'
03/05 13:10:27.242 DEBUG| global_hooks:0056| 'lp -d FakePrinterID /usr/local/autotest/tests/platform_AddPrinter/to_print.pdf'
03/05 13:10:37.281 DEBUG| utils:0214| Running 'cmp /tmp/printing_request.log /usr/local/autotest/tests/platform_AddPrinter/golden_printing_request_generic.bin'
03/05 13:10:37.291 DEBUG| global_hooks:0056| 'cmp /tmp/printing_request.log /usr/local/autotest/tests/platform_AddPrinter/golden_printing_request_generic.bin'
03/05 13:10:37.336 DEBUG| test:0410| Test failed due to Command <cmp /tmp/printing_request.log /usr/local/autotest/tests/platform_AddPrinter/golden_printing_request_generic.bin> failed, rc=2, Command returned non-zero exit status
* Command:
cmp /tmp/printing_request.log /usr/local/autotest/tests/platform_AddPrint
er/golden_printing_request_generic.bin
Exit status: 2
Duration: 0.00865793228149
stderr:
cmp: /tmp/printing_request.log: No such file or directory. Exception log follows the after_iteration_hooks.
Suspect it was caused by a recent test change? https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/891665
xiaochu@, can you take a look?
Comment 1 by xiaochu@chromium.org
, Mar 6 2018Status: Duplicate (was: Untriaged)