public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] runner/resultgen: Handle empty outputs
Date: Fri, 11 Oct 2019 15:26:46 +0300	[thread overview]
Message-ID: <20191011122646.jto3zerpppx5bpyj@ahiler-desk1.fi.intel.com> (raw)
In-Reply-To: <20191011115255.15720-1-petri.latvala@intel.com>

On Fri, Oct 11, 2019 at 02:52:55PM +0300, Petri Latvala wrote:
> If an output (out.txt or err.txt) is completely empty, we handle the
> parsing just fine as is, but we end up assuming that if journal says
> we have a subtest, that subtest printed that it started. We have one
> case where out.txt was empty and all other files were intact (ran out
> of disk?)

It doesn't look like there was a space issue. CI would mark the node as
offline way before that - we won't start executing anything if there's
not at least 1GB of space free. The offending machine (shard-snb2) has
around 80GB free as of now.

I'll couldn't get apport to work, so I have switched over
systemd-coredump on the reporting machine and I'll keep an eye for any
runner coredumps.

This may account for some of the missing "notrun"s :-)

> All other paths that expect certain texts handle failures finding them
> properly apart from subtest result processing, which happily passed
> along a NULL pointer as a string to json. After handling that case,
> the processing of said weird case proceeded fine and produced correct
> results.
> 
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-10-11 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 11:52 [igt-dev] [PATCH i-g-t] runner/resultgen: Handle empty outputs Petri Latvala
2019-10-11 12:26 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-10-11 12:26 ` Arkadiusz Hiler [this message]
2019-10-11 13:00 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-10-11 18:27 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191011122646.jto3zerpppx5bpyj@ahiler-desk1.fi.intel.com \
    --to=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox