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

Issue 902127 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Test platform_PrinterPpds.all_digests failed with "Timeout encountered: /usr/bin/ssh ..."

Project Member Reported by ka...@chromium.org, Nov 5

Issue description

https://stainless.corp.google.com/search?view=matrix&row=build&col=board&days=14&test=platform_PrinterPpds.all_digests

Failure reason: 
Autotest client was disconnected: Timeout encountered: /usr/bin/ssh -a -x -o ControlPath=/tmp/_autotmp_jF6vJvssh-master/socket -o Protocol=2 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -l root -p 22 chromeos6-row3-rack3-host17 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::execute_section|_execute_daemon|run] -> ssh_run(/usr/local/autotest/bin/autotestd_monitor /tmp/autoserv-ssoQ64 0 0)\";fi; /usr/local/autotest/bin/autotestd_monitor /tmp/autoserv-ssoQ64 0 0", Test failed for 10 PPD files:...

Samle logs at https://stainless.corp.google.com/browse/chromeos-autotest-results/255137794-chromeos-test/



The test starts and runs well. It reports valid issues with 10 PPD files: 
hplip-3.18.3-hp-deskjet_d1600_series.ppd.gz, 
hplip-3.18.3-hp-deskjet_ink_advant_k109a-z.ppd.gz, 
hplip-3.18.3-hp-officejet_100_mobile_l411.ppd.gz, 
hplip-3.18.3-hp-officejet_150_mobile_l511.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8000_a809.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a909a.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a909g.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a909n.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a910.ppd.gz, 
hplip-3.18.3-hp-postscript-laserjet-pro.ppd.gz


After test reports the failure, a disconnect happens and test finalizing steps timeout:

11/05 01:05:55.224 DEBUG|              test:0386| Starting after_iteration_hooks for platform_PrinterPpds
11/05 01:05:55.225 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1/interrupts.after
11/05 01:05:55.226 DEBUG|             utils:0219| Running 'mkdir -p /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1/var/spool'
11/05 01:05:55.238 DEBUG|             utils:0219| Running 'rsync --no-perms --chmod=ugo+r -a --safe-links --exclude=/crash/**autoserv* --exclude=/crash/*.core /var/spool/crash /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1/var/spool'
11/05 01:05:55.256 DEBUG|             utils:0219| Running 'rm -rf /var/spool/crash/*'
11/05 01:05:55.269 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1/meminfo.after
11/05 01:05:55.270 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1/slabinfo.after
11/05 01:05:55.271 DEBUG|      base_sysinfo:0124| Loggable saves logs to /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1/schedstat.after
11/05 01:05:55.271 DEBUG|             utils:0219| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/platform_PrinterPpds/sysinfo/iteration.1"'
11/05 01:05:55.282 DEBUG|              test:0391| after_iteration_hooks completed
11/05 01:05:55.282 WARNI|              test:0606| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 800, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 464, in execute
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 371, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/platform_PrinterPpds/platform_PrinterPpds.py", line 266, in run_once
    % (len(failures), ', '.join(failures)) )
TestFail: Test failed for 10 PPD files: hplip-3.18.3-hp-deskjet_d1600_series.ppd.gz, hplip-3.18.3-hp-deskjet_ink_advant_k109a-z.ppd.gz, hplip-3.18.3-hp-officejet_100_mobile_l411.ppd.gz, hplip-3.18.3-hp-officejet_150_mobile_l511.ppd.gz, hplip-3.18.3-hp-officejet_pro_8000_a809.ppd.gz, hplip-3.18.3-hp-officejet_pro_8500_a909a.ppd.gz, hplip-3.18.3-hp-officejet_pro_8500_a909g.ppd.gz, hplip-3.18.3-hp-officejet_pro_8500_a909n.ppd.gz, hplip-3.18.3-hp-officejet_pro_8500_a910.ppd.gz, hplip-3.18.3-hp-postscript-laserjet-pro.ppd.gz
11/05 01:05:55.290 DEBUG|              test:0611| Running cleanup for test.


The test fails same way for different boards - hana and samus(being the only boards in this weekly suite run).

We do not know how or why this ssh timeout is happening. 
How can this timeout be investigated?
 
Labels: Hotlist-Deputy
According to the log the test finished correctly. It reported 10 invalid PPD files (what also is "correct"). However, during the test a timeout occurred. Autotest reconnects automatically in this kind of situations, and it also had place in this case. However, somehow this timeout problem (that did not interrupt the test) was reported as a reason of the failure.
Owner: ----
This is on the deputy list, and deputy curren't can't get to it.
Components: -Infra>Client>ChromeOS Test
The failure is always on these 11 'hplip-3.18.3-hp'printers ppds, no matter what device is tested - https://screenshot.googleplex.com/VRoZYs3mWRD

hplip-3.18.3-hp-LJ-Class3.ppd.gz, 
hplip-3.18.3-hp-deskjet_d1600_series.ppd.gz, 
hplip-3.18.3-hp-deskjet_ink_advant_k109a-z.ppd.gz, 
hplip-3.18.3-hp-officejet_100_mobile_l411.ppd.gz, 
hplip-3.18.3-hp-officejet_150_mobile_l511.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8000_a809.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a909a.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a909g.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a909n.ppd.gz, 
hplip-3.18.3-hp-officejet_pro_8500_a910.ppd.gz, 
hplip-3.18.3-hp-postscript-laserjet-pro.ppd.gz

The failures relate mostly to 'FAIL: valid_config - Could not setup valid printer 2' - https://screenshot.googleplex.com/UTeo58kfO1u

Owner: skau@chromium.org
Status: Assigned (was: Untriaged)
Looking into it.  It's possible the digest has changed.
Status: Started (was: Assigned)
Cc: -weifangsun@chromium.org
Owner: pawliczek@chromium.org
Looks like the PPD bundle needs to be updated.  We fixed the PPDs in the repository but didn't update the tests.
Cc: weifangsun@chromium.org
Project Member

Comment 9 by bugdroid1@chromium.org, Nov 22

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/25395256ce212d96b064b110ee277f7bd54375e0

commit 25395256ce212d96b064b110ee277f7bd54375e0
Author: Piotr Pawliczek <pawliczek@google.com>
Date: Thu Nov 22 06:49:15 2018

autotest platform_PrinterPpds: update PPD files

Update PPD files to the last version (committed in CL 220191783). Also update
description in readme.txt about generating list of ghostscript devices used
by printing system.

BUG= chromium:902127 , chromium:901985 
TEST=Tested on elm and nautilus

Change-Id: I0b2c6ee2490e411057383c9719acdece1c904ff7
Reviewed-on: https://chromium-review.googlesource.com/1325392
Commit-Ready: Sean Kau <skau@chromium.org>
Tested-by: Piotr Pawliczek <pawliczek@chromium.org>
Reviewed-by: Sean Kau <skau@chromium.org>

[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/digests/annotation_highlight_square_with_ap.pdf.digests
[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/ppds_100.tar.xz
[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/digests_blacklist.txt
[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/digests/split_streams.pdf.digests
[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/digests/embedded_images.pdf.digests
[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/ppds_all.tar.xz
[modify] https://crrev.com/25395256ce212d96b064b110ee277f7bd54375e0/client/site_tests/platform_PrinterPpds/readme.txt

Status: Fixed (was: Started)
The most of the faulty ppds are fine now. The only failing one is hplip-3.18.3-hp-LJ-Class3 e.g. in https://storage.cloud.google.com/chromeos-autotest-results/260863688-chromeos-test/chromeos6-row4-rack16-host20/platform_PrinterPpds/debug/platform_PrinterPpds.DEBUG

11/25 06:02:34.819 INFO |platform_PrinterPp:0247| hplip-3.18.3-hp-LJ-Class3.ppd.gz: FAIL: Document's digest does not match

This ppd is tracked in issue 905738.

I am closing this bug and having issue 905738 to track progress on hplip-3.18.3-hp-LJ-Class3

Sign in to add a comment