From: Lyude <lyude@redhat.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>, Daniel Vetter <daniel@ffwll.ch>
Subject: [igt-dev] [PATCH i-g-t v3 1/9] lib/tests: Fix test failures with meson 0.50.0
Date: Wed, 24 Apr 2019 16:20:25 -0400 [thread overview]
Message-ID: <20190424202033.7601-2-lyude@redhat.com> (raw)
In-Reply-To: <20190424202033.7601-1-lyude@redhat.com>
From: Lyude Paul <lyude@redhat.com>
Since meson 0.50.0, unit tests which return the GNU standard return code
99 will fail, regardless of whether or not should_fail:true is passed to
test(). Unfortunately, our standard error code (IGT_EXIT_FAILURE) is
also 99.
So, fix this by changing our standard error code to 98.
Signed-off-by: Lyude Paul <lyude@redhat.com>
---
lib/igt_core.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/igt_core.h b/lib/igt_core.h
index 47ffd9e7..44634e0f 100644
--- a/lib/igt_core.h
+++ b/lib/igt_core.h
@@ -119,7 +119,7 @@ extern char *igt_frame_dump_path;
*
* Exit status indicating a test failure
*/
-#define IGT_EXIT_FAILURE 99
+#define IGT_EXIT_FAILURE 98
bool __igt_fixture(void);
void __igt_fixture_complete(void);
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-24 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 20:20 [igt-dev] [PATCH i-g-t v3 0/9] Fixes from updating igt packaging in Fedora Lyude
2019-04-24 20:20 ` Lyude [this message]
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 2/9] Use gettid() wrapper everywhere Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 3/9] lib/aux: Typecast gettid() as pid_t Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 4/9] meson: Don't redefine gettid if the C library provides it Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 5/9] meson: Add .so versioning Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 6/9] meson: Don't allow building with NDEBUG, ever Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 7/9] lib/igt_core: Just use igt_can_fail() in __igt_run_subtest() Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 8/9] Use pkgconfig() macros with dnf in Fedora Dockerfile Lyude
2019-04-24 20:20 ` [igt-dev] [PATCH i-g-t v3 9/9] Update Dockerfile.fedora to Fedora 29 Lyude
2019-04-24 21:14 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixes from updating igt packaging in Fedora (rev2) Patchwork
2019-04-25 10:12 ` [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=20190424202033.7601-2-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=daniel@ffwll.ch \
--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