public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Oleg Vasilev <oleg.vasilev@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for runner: add --list-all and --blacklist
Date: Fri, 14 Jun 2019 13:43:24 -0000	[thread overview]
Message-ID: <20190614134324.19703.4273@emeril.freedesktop.org> (raw)
In-Reply-To: <20190614132429.22384-1-oleg.vasilev@intel.com>

== Series Details ==

Series: runner: add --list-all and --blacklist
URL   : https://patchwork.freedesktop.org/series/62106/
State : failure

== Summary ==

IGT patchset build failed on latest successful build
c7b717f0126374a02fc86de5eb5fb1f3e7b3335b lib/ehl: Add EHL PCI IDs to match table

                        A file containing a list of tests to run
  -o, --overwrite       If the results-path already exists, delete it
  --ignore-missing      Ignored but accepted, for piglit compatibility

 Incompatible options:
  -m, --multiple-mode   Run multiple subtests in the same binary execution.
                        If a testlist file is given, consecutive subtests are
                        run in the same execution if they are from the same
                        binary. Note that in that case relative ordering of the
                        subtest execution is dictated by the test binary, not
                        the testlist
  --inactivity-timeout <seconds>
                        Kill the running test after <seconds> of inactivity in
                        the test's stdout, stderr, or dmesg
  --overall-timeout <seconds>
                        Don't execute more tests after <seconds> has elapsed
  --use-watchdog        Use hardware watchdog for lethal enforcement of the
                        above timeout. Killing the test process is still
                        attempted at timeout trigger.
  --dmesg-warn-level <level>
                        Messages with log level equal or lower (more serious)
                        to the given one will override the test result to
                        dmesg-warn/dmesg-fail, assuming they go through filtering.
                        Defaults to 4 (KERN_WARNING).
  --piglit-style-dmesg  Filter dmesg like piglit does. Piglit considers matches
                        against a short filter list to mean the test result
                        should be changed to dmesg-warn/dmesg-fail. Without
                        this option everything except matches against a
                        (longer) filter list means the test result should
                        change. KERN_NOTICE dmesg level is treated as warn,
                        unless overridden with --dmesg-warn-level.
  -b, --blacklist FILENAME
                        Exclude all test matching to regexes from FILENAME
                        (can be used more than once)
  -L, --list-all        List all matching subtests instead of running
  [test_root]           Directory that contains the IGT tests. The environment
                        variable IGT_TEST_ROOT will be used if set, overriding
                        this option if given.
Cannot open /home/cidrm/igt-gpu-tools/build/tmpdirAFULv5/test-list.txt
Warning: Adjusting oom score failed.
Warning: Adjusting oom score failed.
Warning: Adjusting oom score failed.
Warning: Adjusting oom score failed.
Warning: Adjusting oom score failed.
-------

Full log written to /home/cidrm/igt-gpu-tools/build/meson-logs/testlog.txt
FAILED: meson-test 
/usr/bin/python3 -u /usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.

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

  reply	other threads:[~2019-06-14 13:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 13:24 [igt-dev] [PATCH] runner: add --list-all and --blacklist Oleg Vasilev
2019-06-14 13:43 ` Patchwork [this message]
2019-06-14 14:28 ` Petri Latvala
2019-06-17 11:49 ` [igt-dev] [PATCH v2] " Oleg Vasilev
2019-06-17 12:41   ` Petri Latvala
2019-06-17 13:41   ` [igt-dev] [PATCH v3] " Oleg Vasilev
2019-06-18  8:11     ` Petri Latvala
2019-06-18  9:07       ` [igt-dev] [PATCH v4] " Oleg Vasilev
2019-06-18  9:26         ` Petri Latvala
2019-06-17 14:14 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: add --list-all and --blacklist (rev2) Patchwork
2019-06-17 15:31 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: add --list-all and --blacklist (rev3) Patchwork
2019-06-17 23:23 ` [igt-dev] ✓ Fi.CI.IGT: success for runner: add --list-all and --blacklist (rev2) Patchwork
2019-06-18  2:11 ` [igt-dev] ✓ Fi.CI.IGT: success for runner: add --list-all and --blacklist (rev3) Patchwork
2019-06-18  9:36 ` [igt-dev] ✗ Fi.CI.BAT: failure for runner: add --list-all and --blacklist (rev4) Patchwork
2019-06-18  9:41   ` Petri Latvala
2019-06-18 10:39 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-06-18 20:05 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190614134324.19703.4273@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=oleg.vasilev@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