[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: Regression in Frameworks - DBus Hangs
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2018-11-16 8:26:14
Message-ID: CA+XidOH0U9_QVM-xt5bqf4PbgzjRn+rPSW_5s29Jo+vk9ioP0g () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 14, 2018 at 8:17 AM Ben Cooksley <bcooksley@kde.org> wrote:
> 
> On Tue, Nov 13, 2018 at 2:25 PM David Edmundson
> <david@davidedmundson.co.uk> wrote:
> > 
> > I don't think application CI jobs run with workspace available. I also can't \
> > think of anything that's been merged in workspace.
> 
> That's correct. CI Jobs are only provided with the things they depend on.
> 
> > 
> > ---
> > quitOnLastWindowClosed is also blocked if a QEventLoopLocker is placed on the \
> > main application. 
> > All KJobs do this and a Kjob existing and hanging seems plausible, but that's a \
> > lot harder to grep for.
> 
> Would it show in a backtrace perhaps?
> 
> > 
> > All stdout/stderr of our newly spawned konsole should be forwarded to the test.
> > @Ben is that available?
> > Ideally with QT_LOGGING_RULES=*.debug=true
> 
> The CI system sets QT_LOGGING_RULES=*.debug=true globally prior to
> executing tests [1], so that should definitely be the case, so i'd say
> the test is silencing the messages :(
> 
> Kurt, any ideas here on what would be the best way to get at the
> output from the Konsole process launched by the test?

Ping?

> 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> [1]: https://cgit.kde.org/sysadmin/ci-tooling.git/tree/helpers/run-tests.py#n94
> 
> Thanks,
> Ben

Cheers,
Ben


[prev in list] [next in list] [prev in thread] [next in thread]