Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
C
CI Tooling
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
2
Merge Requests
2
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Sysadmin
CI Tooling
Commits
e9d907bf
Commit
e9d907bf
authored
Mar 05, 2019
by
Ben Cooksley
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
For Akonadi ensure we apply a different QT_MESSAGE_PATTERN to make the log output more usable
CCMAIL: faure@kde.org
parent
fccc4a4a
Pipeline
#1269
skipped with stage
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
0 deletions
+6
-0
helpers/run-tests.py
helpers/run-tests.py
+6
-0
No files found.
helpers/run-tests.py
View file @
e9d907bf
...
...
@@ -101,6 +101,12 @@ buildEnvironment['MESA_DEBUG'] = '1'
# We also want CMake to be noisy when tests fail
buildEnvironment
[
'CTEST_OUTPUT_ON_FAILURE'
]
=
'1'
# Akonadi specific
# Due to Akonadi being heavily multi-process we need to use a different message log format for Qt
# (Otherwise the log isn't really usable)
if
arguments
.
project
==
'akonadi'
:
buildEnvironment
[
'QT_MESSAGE_PATTERN'
]
=
'%{appname}(%{pid})/%{category} %{function}: %{message}'
# Cleanup the builder if needed
if
sys
.
platform
==
'freebsd12'
:
subprocess
.
call
(
"killall -9 dbus-daemon kded5 kioslave klauncher kdeinit5 kiod openbox Xvfb"
,
shell
=
True
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment