On Tue, Nov 13, 2018 at 2:25 PM David Edmundson <da...@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? > > > > > > [1]: https://cgit.kde.org/sysadmin/ci-tooling.git/tree/helpers/run-tests.py#n94 Thanks, Ben
