On Sat, Nov 17, 2018 at 9:31 PM Albert Astals Cid wrote:
>
> El diumenge, 11 de novembre de 2018, a les 11:29:51 CET, Albert Astals Cid va
> escriure:
> > El diumenge, 11 de novembre de 2018, a les 6:51:39 CET, Ben Cooksley va
> > escriure:
> > > On Thu, Nov 8, 2018 at 8:15 PM Ben Cooksley wrot
El diumenge, 11 de novembre de 2018, a les 11:29:51 CET, Albert Astals Cid va
escriure:
> El diumenge, 11 de novembre de 2018, a les 6:51:39 CET, Ben Cooksley va
> escriure:
> > On Thu, Nov 8, 2018 at 8:15 PM Ben Cooksley wrote:
> > >
> > > On Sat, Nov 3, 2018 at 4:41 PM Ben Cooksley wrote:
> >
On Sat, Nov 17, 2018 at 4:30 AM David Edmundson
wrote:
>
>
> Don't thank me yet, I locked up one of the build jobs, sorry.
> https://build.kde.org/job/Applications/job/konsole/job/kf5-qt5%20SUSEQt5.9/380/console
Diagnostic output available from D-Bus:
jenkins@6934489e2599:~> qdbus org.kde.konsol
Don't thank me yet, I locked up one of the build jobs, sorry.
https://build.kde.org/job/Applications/job/konsole/job/kf5-qt5%20SUSEQt5.9/380/console
>Pipeline kf5-qt5 SUSEQt5.9
Output isn't too helpful, though I am surprised to see
kf5.kinit.klauncher in the logs when I'm supposedly invoking the
On Fri, Nov 16, 2018 at 11:04 PM David Edmundson
wrote:
>
> A running KJob would not show in a backtrace.
>
> Update at https://phabricator.kde.org/D16919
Ah I see. Thanks for taking a look into that.
Cheers,
Ben
A running KJob would not show in a backtrace.
Update at https://phabricator.kde.org/D16919
On Wed, Nov 14, 2018 at 8:17 AM Ben Cooksley wrote:
>
> On Tue, Nov 13, 2018 at 2:25 PM David Edmundson
> 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 provid
On Tue, Nov 13, 2018 at 2:25 PM David Edmundson
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
I don't think application CI jobs run with workspace available. I also
can't think of anything that's been merged in workspace.
---
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, bu
On Mon, Nov 12, 2018 at 10:52:17PM +1300, Ben Cooksley wrote:
> In this instance I hoped someone would know of a behaviour change they
> introduced around D-Bus or application shutdown stuff, particularly
> given the time window i'd provided.
>
> >
> > I imagine the majority of people on this list
On Mon, Nov 12, 2018 at 7:27 AM David Edmundson
wrote:
>
> I ran the test locally which passed, then left it for someone else as:
> - I can't reproduce locally.
> - There are absolutely no logs on build.k.o to give a clue.
> - I have no access to build.k.o to do anything (AFAIK).
> - Even the
I ran the test locally which passed, then left it for someone else as:
- I can't reproduce locally.
- There are absolutely no logs on build.k.o to give a clue.
- I have no access to build.k.o to do anything (AFAIK).
- Even the phab ticket cited in the commit that disables the test is not
access
Hi,
> Ping?
>> >
>> > Anyone got any idea why this behaviour has regressed?
>>
>> The complete lack of response to this issue (and any mail to this
>> mailing list i've noticed, I highly suspect everyone just filters it
>> into a corner in their mail client and doesn't read it at all) is
>> reall
El diumenge, 11 de novembre de 2018, a les 6:51:39 CET, Ben Cooksley va
escriure:
> On Thu, Nov 8, 2018 at 8:15 PM Ben Cooksley wrote:
> >
> > On Sat, Nov 3, 2018 at 4:41 PM Ben Cooksley wrote:
> > >
> > > Hi all,
> > >
> > > Following commits made to Frameworks somewhere in the October 21 to
>
On Thu, Nov 8, 2018 at 8:15 PM Ben Cooksley wrote:
>
> On Sat, Nov 3, 2018 at 4:41 PM Ben Cooksley wrote:
> >
> > Hi all,
> >
> > Following commits made to Frameworks somewhere in the October 21 to
> > October 28 time frame, the unit tests of Konsole on the CI system have
> > started to hang foll
On Sat, Nov 3, 2018 at 4:41 PM Ben Cooksley wrote:
>
> Hi all,
>
> Following commits made to Frameworks somewhere in the October 21 to
> October 28 time frame, the unit tests of Konsole on the CI system have
> started to hang following completion.
>
> This hang is occurring due to a behaviour of C
Hi all,
Following commits made to Frameworks somewhere in the October 21 to
October 28 time frame, the unit tests of Konsole on the CI system have
started to hang following completion.
This hang is occurring due to a behaviour of CTest, where it will wait
(indefinitely) following the conclusion o
17 matches
Mail list logo
