https://bugs.kde.org/show_bug.cgi?id=469255
--- Comment #11 from kloczek <kloczko.tom...@gmail.com> ---
(In reply to Nate Graham from comment #10)
> I'm a bug triager, not a KWin developers. I triaged this bug as "not a bug
> because it's a question about a local development setup".
How do you know that this is not a bug?
Did you never saw test suite failing on one system and be perfectly fine on
another one even if they have been assembled using the same binary packages
caused by actual bug in tested code?
> The purpose of bug
> triaging is to make sure that bug reports are reporting actual bugs, so we
> don't waste developers' time when they go looking through bug reports by
> making them wade through things that they can't work on.
>
> I typically run tests with a bash alias:
>
> function ktest {
> REPO=$( basename $( git rev-parse --show-toplevel ) )
> BUILD_DIR=~/kde/build/$REPO
> make --no-print-directory -C $BUILD_DIR test
> }
>
> When I'm in the source dir, I run `ktest` and it runs the tests from the
> build dir without me having to go there manually.
Is that ststem assembled out of Debian or some rpm based duistrinution?
Can you show me at least list of packages installed in that CI system?
--
You are receiving this mail because:
You are watching all bug changes.
