New issue
Advanced search Search tips

Issue 700058 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 660481
issue 731558



Sign in to add a comment

kitchen-butler: not all logs are uploaded

Project Member Reported by no...@chromium.org, Mar 9 2017

Issue description

in the task lgo of https://chromium-swarm-dev.appspot.com/task?id=34ca0e65b247d610&refresh=10&show_raw=1
the last step is 
substep: <
  step: <
    name: "Failure reason"
    status: SUCCESS
    started: <
      seconds: 1489036406
      nanos: 69999872
    >
    ended: <
      seconds: 1489036406
      nanos: 69999872
    >
    other_links: <
      label: "reason"
      logdog_stream: <
        name: "steps/Failure_reason/0/logs/reason/0"
      >
    >
  >
>

but the final proto uploaded to logdog does not contain that step:
https://1579-d8d5ab3-tainted-nodir-dot-luci-milo-dev.appspot.com/logdog/build/infra-experimental/swarm/chromium-swarm-dev.appspot.com/34ca0e65b247d611/+/annotations

note that there are some errors in the task log that seem to indicate that there was a problem sending pubsub messages.

[I 2017-03-08 21:13:26] Exiting serve loop.                         {"namedPipePath":"/b/s/w/irUhI6wq/tmp/ld.sock", "totalConnections":0}
[I 2017-03-08 21:13:26] Message output has closed                   {"stats":"{SentBytes:3161870 SentMessages:724 DiscardedMessages:0 Errors:0}"}
[E 2017-03-08 21:13:26] Annotated error stack:
original error: return code: 1

Not sure why it is INFO, and not ERROR or at least WARNING.


Also kitchen should have infra-failed.

This is a blocker for linux_chromium_rel_ng ( bug 660481 )
 

Comment 1 by no...@chromium.org, Mar 9 2017

 Issue 700052  has been merged into this issue.

Comment 2 by no...@chromium.org, Mar 9 2017

the final step "Failure reason" started at 1489036406 which is 09:13:26 PDT and the "Exiting serve loop" happened at that time too, so probably this is not because sending out logs stopped prematurely.
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 9 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/f387f575245fa41ec7c9315b6a76bd323287ee75

commit f387f575245fa41ec7c9315b6a76bd323287ee75
Author: Nodir Turakulov <nodir@google.com>
Date: Thu Mar 09 18:38:31 2017

Project Member

Comment 4 by bugdroid1@chromium.org, Mar 9 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/f387f575245fa41ec7c9315b6a76bd323287ee75

commit f387f575245fa41ec7c9315b6a76bd323287ee75
Author: Nodir Turakulov <nodir@google.com>
Date: Thu Mar 09 18:38:31 2017

Comment 5 by no...@chromium.org, Mar 9 2017

Status: Fixed (was: Untriaged)

Comment 6 by no...@chromium.org, Jun 9 2017

Blocking: 731558

Sign in to add a comment