From: Patchwork <patchwork@emeril.freedesktop.org>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/2] meson: Bump meson version requirement to 0.46.0
Date: Tue, 19 Feb 2019 11:10:22 -0000 [thread overview]
Message-ID: <20190219111022.5011.8507@emeril.freedesktop.org> (raw)
In-Reply-To: <20190219105143.27824-1-arkadiusz.hiler@intel.com>
== Series Details ==
Series: series starting with [i-g-t,1/2] meson: Bump meson version requirement to 0.46.0
URL : https://patchwork.freedesktop.org/series/56891/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
368e76156f752e6ed6ac32ed9f400567aef7d3fc runner: Exit with 2 when overall timeout exceeded
The Meson build system
Version: 0.45.1
Source dir: /home/cidrm/igt-gpu-tools
Build dir: /home/cidrm/igt-gpu-tools/build
Build type: native build
meson.build:1:0: ERROR: Meson version is 0.45.1 but project requires >=0.46.0.
A full log can be found at /home/cidrm/igt-gpu-tools/build/meson-logs/meson-log.txt
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-19 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 10:51 [igt-dev] [PATCH i-g-t 1/2] meson: Bump meson version requirement to 0.46.0 Arkadiusz Hiler
2019-02-19 10:51 ` [igt-dev] [PATCH i-g-t 2/2] benchmarks/meson: Stop renaming benchmarks Arkadiusz Hiler
2019-02-19 11:03 ` Chris Wilson
2019-02-19 11:10 ` Patchwork [this message]
2019-02-19 12:07 ` [igt-dev] [PATCH i-g-t 1/2] meson: Bump meson version requirement to 0.46.0 Daniel Vetter
2019-02-19 13:27 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] meson: Bump meson version requirement to 0.46.0 (rev2) Patchwork
2019-02-19 16:30 ` [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=20190219111022.5011.8507@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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