https://bugs.kde.org/show_bug.cgi?id=455533
Igor Kushnir <igor...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |ASSIGNED
Ever confirmed|0 |1
Assignee|kdevelop-bugs-n...@kde.org |igor...@gmail.com
--- Comment #10 from Igor Kushnir <igor...@gmail.com> ---
(In reply to Sigbjorn from comment #9)
> (In reply to Igor Kushnir from comment #7)
> > The test suite code is somewhat messy and buggy. I have started fixing it
> > more than a year ago, but sadly postponed that work in favor of other
> > fixes/improvements. If you want to try and fix this issue, I could share my
> > WIP changes. If not, try disabling KDevelop's Unit Test View plugin as a
> > workaround.
>
> Hi, thanks for responding.
> As pr my latest investigation, it seems that if there is a duplicate
> test-case within the suite, that triggers the error.
> I guess there is an assumption somewhere that they are unique, but not
> enforced/handled, so it surfaces as a crash during
> destruction of the test-suite structures.
>
> For this there is a workaround, that is, ensure there is no duplicate
> test-cases enlisted in tests.
Thanks for the investigation. I'll take a look at this duplicate issue when I
resume work on test suite fixing.
> However, the cmake/integration exports the test-case names, that might be
> duplicates.
> Creating a minimal cmake doctest example, with two test-suites, and within
> each of them, repeats the crash, at the same spot.
Could you attach a sample project that triggers the crash?
--
You are receiving this mail because:
You are watching all bug changes.
