public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] runner/resultgen: Provide output when test output is completely empty
Date: Wed, 19 Feb 2020 15:27:58 +0200	[thread overview]
Message-ID: <20200219132758.GT25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <158211860207.8112.2166645472651306406@skylake-alporthouse-com>

On Wed, Feb 19, 2020 at 01:23:22PM +0000, Chris Wilson wrote:
> Quoting Petri Latvala (2020-02-19 12:19:40)
> > If a machine is hard-hanging or otherwise rebooted at the correct
> > time, intermediary output files get created but nothing ever gets
> > written to them. That yields results that are completely empty and
> > hard to categorize or even sometimes detect automatically. Handle this
> > corner case explicitly with a custom text explaining what might have
> > happened to prod result analysis towards fixing the real issue instead
> > of wondering if test result processing is faulty.
> > 
> > The race for getting empty files is easier to hit than it seems. The
> > files get created by the runner before calling exec(), and there's
> > plenty of time to hit a really hard crash.
> 
> Speaking of which, it would not be terrible if igt_runner periodically
> called sync() everytime it decided there were new logs to preserve.
> We should also probably remove/reduce the writeback delay.


Does calling sync() sync more than fsyncdata()?


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-02-19 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 12:19 [igt-dev] [PATCH i-g-t] runner/resultgen: Provide output when test output is completely empty Petri Latvala
2020-02-19 12:40 ` Arkadiusz Hiler
2020-02-19 13:20 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-19 13:23 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-02-19 13:27   ` Petri Latvala [this message]
2020-02-19 13:33     ` Chris Wilson
2020-02-19 13:45       ` Petri Latvala
2020-02-19 13:46         ` Chris Wilson
2020-02-19 13:50           ` Chris Wilson
2020-02-19 13:56             ` Petri Latvala
2020-02-19 13:59               ` Chris Wilson
2020-02-19 14:03                 ` Petri Latvala
2020-02-21  3:33 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=20200219132758.GT25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    /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