what I meant to say about the error message: the message is new, but the fact that we
couldn't set thread names on Windows hasn't changed :)
On 2/25/25 5:09 PM, Marcus Müller wrote:
Hi Chris,
I introduced that log message, because, well, we haven't implemented the feature to set
user thread names on Windows. That's always been the case, and hasn't changed.
Now, your three test case failures do worry me. Could you maybe attach the
outputs of
ctest -R wavfile_test --output-on-failure
ctest -R interleave_test --output-on-failure
?
Thank you for reporting things like these,
Marcus
On 2/24/25 6:53 PM, Chris Gorman wrote:
Hello All,
I'm in the process of updating the msys2 / mingw64 implementation of
gnuradio to 3.10.12.0 and have run into a problem with threading. Two
tests fail[1] and one times out[2] while running the test suite. When
run on their own, all three tests return 0 and appear to run properly,
but for a thread error. I also get this error when running
gnuradio-companion.exe. For each test case, and grc, I get multiple
lines of:
"thread :error: function set_thread_name(gr_thread_t, string) not
implemented on this platform"
My experience with threading is minimal and I feel uneasy proceeding
with the update, given the error. If someone with more experience
could let me know their opinion on whether or not the thread error is
a cause for concern, I would appreciate it.
Thanks in advance,
Chris
[1] qa_wavfile_test.bat and qa_interleave_test.bat
[2] qa_mute_test.bat
