From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "Yu, Mingli" <mingli.yu@windriver.com>, lttng-dev@lists.lttng.org
Subject: Re: tests/regression/tools/clear/test_ust fails occacionally
Date: Tue, 22 Jul 2025 09:58:20 -0400 [thread overview]
Message-ID: <545d23d6-c9fe-4428-96c6-9a323e2d333b@efficios.com> (raw)
In-Reply-To: <d3c56122-9c05-42fa-9d76-b32aa5f7a6fb@windriver.com>
Hi Mingli,
sorry I missed these messages last week.
What version of babeltrace are you using when running the tests?
What distribution + version are you using?
There is a fix for hangs that may occur during the test, which is
included in stable-2.14 -
https://github.com/lttng/lttng-tools/commit/55d3f5e528059267f44fb24b179b992bf2b0cfa6
I've been working on replacing the test. I'd be curious to know if you
also see intermittent failures with the new version (e.g., is it a
detail in the test harness, or is the issue elsewhere).
https://review.lttng.org/c/lttng-tools/+/14959
thanks,
kienan
On 7/16/25 10:27 PM, Yu, Mingli wrote:
> The more detail around the error as below.
>
>
> [warning] [Context] Cannot open_trace of format lttng-live at path
> net://localhost/host/qemux86-64/ggpndHBBanTXM3EY.
> [warning] [Context] cannot open trace "net://localhost/host/qemux86-64/
> ggpndHBBanTXM3EY" for reading.
> [error] opening trace "net://localhost/host/qemux86-64/ggpndHBBanTXM3EY"
> for reading.
>
> [error] none of the specified trace paths could be opened.
>
> # Wait for viewer to exit
> not ok 486 - Babeltrace succeeds
> FAIL: tools/clear/test_ust 486 - Babeltrace succeeds
> # Failed test 'Babeltrace succeeds'
> # in ./tools/clear/test_ust:test_ust_streaming_live_viewer() at line 324.
>
>
> Thanks,
> Mingli
>
> On 7/14/25 17:37, Yu, Mingli via lttng-dev wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the sender
>> and know the content is safe.
>>
>> Hi,
>>
>> The lttng-tools test fails as below, is there anyone meet the same issue
>> and how to fix this? Thanks!
>>
>>
>> FAIL: tools/clear/test_ust 486 - Babeltrace succeeds
>> [snip]
>> FAIL: tools/clear/test_ust 706 - Babeltrace succeeds
>> [snip]
>> FAIL: tools/clear/test_ust
>> [snip]
>> # Wait for viewer to exit
>> not ok 486 - Babeltrace succeeds
>> FAIL: tools/clear/test_ust 486 - Babeltrace succeeds
>> # Failed test 'Babeltrace succeeds'
>> # in ./tools/clear/test_ust:test_ust_streaming_live_viewer() at line
>> 324.
>> [snip]
>> # Wait for viewer to exit
>> not ok 706 - Babeltrace succeeds
>> FAIL: tools/clear/test_ust 706 - Babeltrace succeeds
>> # Failed test 'Babeltrace succeeds'
>> # in ./tools/clear/test_ust:test_ust_streaming_live_viewer() at line
>> 324.
>>
>>
>> Thanks,
>> Mingli
prev parent reply other threads:[~2025-07-22 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 9:37 Yu, Mingli via lttng-dev
2025-07-17 2:10 ` Yu, Mingli via lttng-dev
2025-07-17 2:17 ` Fwd: " Yu, Mingli via lttng-dev
2025-07-17 2:27 ` Yu, Mingli via lttng-dev
2025-07-22 13:58 ` Kienan Stewart via lttng-dev [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=545d23d6-c9fe-4428-96c6-9a323e2d333b@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.com \
--cc=mingli.yu@windriver.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