From: Fathi Boudra <fathi.boudra@linaro.org>
To: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Emilio López" <emilio.lopez@collabora.co.uk>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Fathi Boudra" <fathi.boudra@linaro.org>
Subject: [PATCH 1/1] selftests: sync: add config fragment for testing sync framework
Date: Fri, 5 May 2017 08:05:50 +0300 [thread overview]
Message-ID: <20170505050550.30102-1-fathi.boudra@linaro.org> (raw)
Unless the software synchronization objects (CONFIG_SW_SYNC) is enabled,
the sync test will fail:
Additional Information:
Running tests in sync
========================================
[RUN] Testing sync framework
[RUN] Executing test_alloc_timeline
[ERROR] Failure allocating timeline
[RUN] Executing test_alloc_fence
[ERROR] Failure allocating timeline
[RUN] Executing test_alloc_fence_negative
[ERROR] Failure allocating timeline
[RUN] Executing test_fence_one_timeline_wait
[ERROR] Failure allocating timeline
[RUN] Executing test_fence_one_timeline_merge
[ERROR] Failure allocating fences
[RUN] Executing test_fence_merge_same_fence
[ERROR] Failure allocating timeline
[RUN] Executing test_fence_multi_timeline_wait
[ERROR] Failure merging fence from various timelines
[RUN] Executing test_stress_two_threads_shared_timeline
[ERROR] Failure allocating timeline
[RUN] Executing test_consumer_stress_multi_producer_single_consumer
[ERROR] Failure merging fences
[ERROR] Failure creating fence
[ERROR] Failure creating fence
[ERROR] Failure creating fence
[ERROR] Failure creating fence
[ERROR] Failure creating fence
[RUN] Executing test_merge_stress_random_merge
[ERROR] Failure creating fence
[FAIL] sync errors: 10
selftests: sync_test [FAIL]
Add a config fragment with the relevant configuration required in order to
run the sync test.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
---
tools/testing/selftests/sync/config | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 tools/testing/selftests/sync/config
diff --git a/tools/testing/selftests/sync/config b/tools/testing/selftests/sync/config
new file mode 100644
index 000000000000..1ab7e8130db2
--- /dev/null
+++ b/tools/testing/selftests/sync/config
@@ -0,0 +1,4 @@
+CONFIG_STAGING=y
+CONFIG_ANDROID=y
+CONFIG_SYNC=y
+CONFIG_SW_SYNC=y
--
2.11.0
next reply other threads:[~2017-05-05 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 5:05 Fathi Boudra [this message]
2017-05-11 4:52 ` Michael Ellerman
2017-05-11 6:29 ` Fathi Boudra
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=20170505050550.30102-1-fathi.boudra@linaro.org \
--to=fathi.boudra@linaro.org \
--cc=emilio.lopez@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sumit.semwal@linaro.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
all inboxes | Powered by JetHome®