public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Carlos Santa <carlos.santa@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_watchdog: Initial set of tests for GPU watchdog (rev3)
Date: Mon, 15 Apr 2019 18:32:23 -0000	[thread overview]
Message-ID: <20190415183223.30486.28685@emeril.freedesktop.org> (raw)
In-Reply-To: <20190415182251.22427-1-carlos.santa@intel.com>

== Series Details ==

Series: tests/gem_watchdog: Initial set of tests for GPU watchdog (rev3)
URL   : https://patchwork.freedesktop.org/series/50041/
State : failure

== Summary ==

IGT patchset build failed on latest successful build
ff28c28cd1e5a8ca219d9795e508c80221b9cf26 tests: Add kms_plane_cursor tests

[334/453] Linking target tests/gem_softpin.
[335/453] Linking target tests/gem_spin_batch.
[336/453] Linking target tests/gem_stolen.
[337/453] Linking target tests/gem_threaded_access_tiled.
[338/453] Linking target tests/gem_storedw_batches_loop.
[339/453] Linking target tests/gem_storedw_loop.
[340/453] Linking target tests/gem_sync.
[341/453] Linking target tests/gem_streaming_writes.
[342/453] Linking target tests/gem_tiled_blits.
[343/453] Linking target tests/gem_tiled_partial_pwrite_pread.
[344/453] Linking target tests/gem_tiled_fence_blits.
[345/453] Linking target tests/gem_tiled_pread_basic.
[346/453] Linking target tests/gem_tiled_swapping.
[347/453] Linking target tests/gem_tiled_pread_pwrite.
[348/453] Linking target tests/gem_unfence_active_buffers.
[349/453] Linking target tests/gem_tiled_wb.
[350/453] Linking target tests/gem_write_read_ring_switch.
[351/453] Linking target tests/gem_tiled_wc.
[352/453] Linking target tests/gem_tiling_max_stride.
[353/453] Compiling C object 'tests/tests@@gem_watchdog@exe/i915_gem_watchdog.c.o'.
FAILED: tests/tests@@gem_watchdog@exe/i915_gem_watchdog.c.o 
ccache cc -Itests/tests@@gem_watchdog@exe -Itests -I../tests -I../include/drm-uapi -Ilib -I../lib -I../lib/stubs/syscalls -I. -I../ -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/opt/igt/include -I/opt/igt/include/libdrm -I/usr/include/x86_64-linux-gnu -I/usr/include -I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/home/cidrm/kernel_headers/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu11 -O0 -g -D_GNU_SOURCE -include config.h -Wbad-function-cast -Wdeclaration-after-statement -Wformat=2 -Wimplicit-fallthrough=0 -Wlogical-op -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wuninitialized -Wunused -Wno-clobbered -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-pointer-arith -Wno-sign-compare -Wno-type-limits -Wno-unused-parameter -Wno-unused-result -Werror=address -Werror=array-bounds -Werror=implicit -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=pointer-to-int-cast -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -pthread  -MD -MQ 'tests/tests@@gem_watchdog@exe/i915_gem_watchdog.c.o' -MF 'tests/tests@@gem_watchdog@exe/i915_gem_watchdog.c.o.d' -o 'tests/tests@@gem_watchdog@exe/i915_gem_watchdog.c.o' -c ../tests/i915/gem_watchdog.c
../tests/i915/gem_watchdog.c: In function ‘gpu_watchdog_long_batch_2_contexts’:
../tests/i915/gem_watchdog.c:283:53: error: ‘SYS_gettid’ undeclared (first use in this function); did you mean ‘gettid’?
   bb_factory(fd, ctx, -1, batch_timeout_ms, syscall(SYS_gettid));
                                                     ^~~~~~~~~~
                                                     gettid
../tests/i915/gem_watchdog.c:283:53: note: each undeclared identifier is reported only once for each function it appears in
../tests/i915/gem_watchdog.c:276:13: warning: unused variable ‘j’ [-Wunused-variable]
  int i = 0, j=0;
             ^
../tests/i915/gem_watchdog.c: In function ‘gpu_watchodg_hang_long_batch_single_engine’:
../tests/i915/gem_watchdog.c:341:52: error: ‘SYS_gettid’ undeclared (first use in this function); did you mean ‘gettid’?
  bb_factory(fd, ctx, -1, batch_timeout_ms, syscall(SYS_gettid));
                                                    ^~~~~~~~~~
                                                    gettid
../tests/i915/gem_watchdog.c: In function ‘no_gpu_hang_long_batch_all_engines’:
../tests/i915/gem_watchdog.c:378:54: error: ‘SYS_gettid’ undeclared (first use in this function); did you mean ‘gettid’?
  bb_factory(fd, ctx, prio, batch_timeout_ms, syscall(SYS_gettid));
                                                      ^~~~~~~~~~
                                                      gettid
../tests/i915/gem_watchdog.c: In function ‘__real_main386’:
../tests/i915/gem_watchdog.c:391:15: warning: variable ‘engines’ set but not used [-Wunused-but-set-variable]
  unsigned int engines[16];
               ^~~~~~~
At top level:
../tests/i915/gem_watchdog.c:81:13: warning: ‘check_error_state’ defined but not used [-Wunused-function]
 static bool check_error_state(int fd)
             ^~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.

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

      parent reply	other threads:[~2019-04-15 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 18:22 [igt-dev] [RFC] IGT GPU watchdog Carlos Santa
2019-04-15 18:22 ` [igt-dev] [RFC] tests/gem_watchdog: Initial set of tests for " Carlos Santa
2019-04-15 21:50   ` Antonio Argenziano
2019-04-16  2:02     ` Carlos Santa
2019-04-16 20:16       ` Antonio Argenziano
2019-04-16 20:21         ` Chris Wilson
2019-04-16 20:29           ` Antonio Argenziano
2019-04-15 18:32 ` Patchwork [this message]

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=20190415183223.30486.28685@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=carlos.santa@intel.com \
    --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