https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #15 from Jasem Mutlaq ---
Everything passed, except this:
XFAIL : KStarsUiTests::initialConditionsTest() Initial KStars clock is set
from system local time, not geolocation, and is untestable for now.
Loc:
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #14 from TallFurryMan ---
Jasem, could you confirm you adjusted the relevant test to verify your change?
Tests/kstars_ui/test_ekos.cpp, in TestEkos::testSimulatorProfile, line 134.
I don't see this in your changelog.
--
You are
https://bugs.kde.org/show_bug.cgi?id=398192
Jasem Mutlaq changed:
What|Removed |Added
Version Fixed In||3.4.2
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=398192
TallFurryMan changed:
What|Removed |Added
Version|2.9.8 |3.4.0
--- Comment #12 from TallFurryMan ---
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #11 from TallFurryMan ---
Reproduced on my live (not current) system, confirming test is OK:
^C[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
0xb7f5bd09 in
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #10 from TallFurryMan ---
When the issue is reproduced, this is the stack from the event clicking the
"stop" button:
1 __GI___pthread_timedjoin_ex
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #9 from TallFurryMan ---
Refining the test, it appears the issue may source from the intrication of
signals between gadgets. The code is re-entring the event loop at various
places, and if the INDI server is still busy deleting properties,
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #8 from Jasem Mutlaq ---
I've seen this before but couldn't figure out the root cause :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #7 from TallFurryMan ---
In my test, INDI client is still creating properties after 20 seconds, so I'll
investigate further before calling the test proper:
1 syscall
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #6 from TallFurryMan ---
I need to make very sure the test is spotting the right problem.
I'll then push a differential with said test for reference.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #5 from TallFurryMan ---
Reproduced using indi 1.7.9, and indi git tip. Call is stuck with the following
stack:
1 __GI___pthread_timedjoin_ex
https://bugs.kde.org/show_bug.cgi?id=398192
Jasem Mutlaq changed:
What|Removed |Added
CC||mutla...@ikarustech.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #3 from TallFurryMan ---
Yes, confirmed again.
I just wrote a test to validate this and can reliably reproduce the issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398192
TallFurryMan changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=398192
mountainai...@outlook.com changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=398192
mountainai...@outlook.com changed:
What|Removed |Added
CC||mountainai...@outlook.com
--
You
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #1 from Jasem Mutlaq ---
I believe this issue is due to a problem shutting down the thread in BaseClient
at times. Seen this issue before, but it is rare. Does it get stuck on
pthread_join?
--
You are receiving this mail because:
You are
17 matches
Mail list logo
