From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>,
Petri Latvala <petri.latvala@intel.com>,
Martin Peres <martin.peres@linux.intel.com>
Subject: [igt-dev] [PATCH i-g-t] tests/tools_test: Print the starting cwd
Date: Mon, 14 Jan 2019 14:42:53 +0200 [thread overview]
Message-ID: <20190114124253.26937-1-petri.latvala@intel.com> (raw)
Occasionally in CI tools_test goes looking for tools binaries in /bin,
instead of /opt/igt/bin where they should be. Print out the cwd before
the chdir() dance to figure out what's going on.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
Cc: Martin Peres <martin.peres@linux.intel.com>
---
tests/tools_test.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/tools_test.c b/tests/tools_test.c
index 88a6ae96..de574fa8 100644
--- a/tests/tools_test.c
+++ b/tests/tools_test.c
@@ -82,6 +82,10 @@ igt_main
igt_fixture {
char *path;
+ path = get_current_dir_name();
+ igt_info("Looking for tools, cwd is %s\n", path);
+ free(path);
+
igt_require_f(chdir_to_tools_dir(),
"Unable to determine the tools directory, expecting them in $cwd/" TOOLS " or $path/" TOOLS "\n");
path = get_current_dir_name();
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-01-14 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 12:42 Petri Latvala [this message]
2019-01-14 13:24 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/tools_test: Print the starting cwd Patchwork
2019-01-14 19:11 ` [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=20190114124253.26937-1-petri.latvala@intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@linux.intel.com \
--cc=tomi.p.sarvela@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