Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 2 users
Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 730067
issue 734690
issue 726481



Sign in to add a comment
Result collection tries to copy out a single file for 1 hour
Project Member Reported by pprabhu@chromium.org, Jun 23 Back to list
Really: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/124701020-chromeos-test/chromeos4-row9-jetstream-host5/debug/

Twice in that run, so that's a test running for 2+ hours because of the two rsync calls:

06/22 19:52:45.108 DEBUG|             utils:0212| Running 'rsync -l  --timeout=1800 --rsh='/usr/bin/ssh -a -x   -o ControlPath=/tmp/_autotmp_ZGcIS4ssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22' -az --no-o --no-g root@chromeos4-row9-jetstream-host5:"/usr/local/autotest/results/default/" "/usr/local/autotest/results/124701020-chromeos-test/chromeos4-row9-jetstream-host5"'
06/22 20:53:38.577 WARNI|      abstract_ssh:0380| rsync status 255, retrying
06/22 20:53:38.594 DEBUG|      abstract_ssh:0346| get_file. source: ['/usr/local/autotest/results/default/'], dest: /usr/local/autotest/results/124701020-chromeos-test/chromeos4-row9-jetstream-host5, delete_dest: False,preserve_perm: True, preserve_symlinks:True
06/22 20:53:38.594 INFO |      abstract_ssh:0795| Master ssh connection to chromeos4-row9-jetstream-host5 is down.

06/22 20:55:01.166 DEBUG|             utils:0212| Running 'rsync -l  --timeout=1800 --rsh='/usr/bin/ssh -a -x   -o ControlPath=/tmp/_autotmp_kg4G3Fssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22' -az --no-o --no-g root@chromeos4-row9-jetstream-host5:"/usr/local/autotest/results/default/" "/usr/local/autotest/results/124701020-chromeos-test/chromeos4-row9-jetstream-host5"'
06/22 21:01:53.494 INFO |          autoserv:0687| Results placed in /usr/local/autotest/results/124701020-chromeos-test/chromeos4-row9-jetstream-host5
06/22 21:01:53.517 DEBUG|          autoserv:0695| autoserv is running in drone cros-autotest-shard4.hot.corp.google.com.
 
Blocking: 726481 730067
Blocking: 734690
Labels: cq-annot
Status: Unconfirmed
Need more examples to convince us that this happens often enough.
If so, This goes Pri-1.
Issue 755080 has been merged into this issue.
Labels: -Pri-3 Pri-1
Status: Untriaged
Collecting evidence for this bug is costly -- someone has to go dig into aborted server jobs which is hard.
This is bad enough that it needs to be P1. We have two instances of this collected here.

Sending it to weekly triage queue to be assigned to somebody.
Is the following build yet another instance of this issue?

https://luci-milo.appspot.com/buildbot/chromeos/banjo-release/1387
Sign in to add a comment