markus mohrhard 2018-10-26 - the document foundation · 2018-11-06 · cppcheck static analysis...
TRANSCRIPT
1Data for LibreOffice developers
Data for LibreOffice developerss
Markus Mohrhard2018-10-26
2Data for LibreOffice developers
Topic
Huge projectA lot of data to make life of a developer easierWhere do I find these information?How do I use them?LimitationsIdeas
3Data for LibreOffice developers
Current data
4Data for LibreOffice developers
Devcentral
Devcentral.libreoffice.org
5Data for LibreOffice developers
devcentral
6Data for LibreOffice developers
devcentral
Links to many resources for developers
Work in progressNeeds more workNeeds a web developer
Bookmark this page!
7Data for LibreOffice developers
gerrit
Gerrit.libreoffice.org
8Data for LibreOffice developers
gerrit
9Data for LibreOffice developers
gerrit
Same name for two thingsMain git repository
Contains nearly all TDF repositories
Review platformNo commit access => Push to reviewRelease branches, e.g. libreoffice-5-1
All open commits
10Data for LibreOffice developers
jenkins
ci.libreoffice.org
11Data for LibreOffice developers
jenkins
12Data for LibreOffice developers
jenkins
All automated builds
Website with overview
Also contains gerrit verification builds
Logs for builds, ...
13Data for LibreOffice developers
Tinderboxes
tinderbox.libreoffice.org
14Data for LibreOffice developers
Tinderboxes
15Data for LibreOffice developers
Tinderboxes
Part of the CI infrastructure
Build LibreOffice on different platform & configuration
Website + mail when broken
16Data for LibreOffice developers
Coverity
Scan.coverity.com
17Data for LibreOffice developers
Coverity
18Data for LibreOffice developers
Coverity
Static analysis
Not hosted by TDF
Free for us, 2 runs a week
Mail to the developer list with new reports
~0 open issues
19Data for LibreOffice developers
cppcheck
http://dev-builds.libreoffice.org/cppcheck_reports/master/
20Data for LibreOffice developers
cppcheck
21Data for LibreOffice developers
cppcheck
Static analysisOpen source toolRuns on a TDF server weeklyMail to developer list + websiteMany open issues
Many false positivesRead reports with care
22Data for LibreOffice developers
Performance testing
perf.libreoffice.org
23Data for LibreOffice developers
Perf.libreoffice.org
24Data for LibreOffice developers
Perf.libreoffice.org
Automated performance testingRun on TDF CI infrastructureNo mails, only websiteSmall fluctuations in runs
Only look at huge spikesOwn code, always needs new web developers
Talk to Norbert or me
25Data for LibreOffice developers
Crash testing & Validation testing
dev-builds.libreoffice.org/crashtest/
26Data for LibreOffice developers
Crash testing & Validation testing
27Data for LibreOffice developers
Crash testing & Validation testing
Run on huge TDF serverRuns every few daysMail to developer list and archive on dev-www.libreoffice.org
Only csv files and log files~0 open crashes~30k open validation errors
Many duplicatesAllows to add assert to import/export code and see which docs hit it
28Data for LibreOffice developers
Lcov
Lcov.libreoffice.org
29Data for LibreOffice developers
lcov
30Data for LibreOffice developers
lcov
Generates reports about test coverageRuns weekly on TDF serverMail to developer list + websiteCurrently brokenUseful if you want to add tests
Check which features are not covered yet
31Data for LibreOffice developers
UBSAN
ci.libreoffice.org/job/lo_ubsan/
32Data for LibreOffice developers
UBSAN
33Data for LibreOffice developers
UBSAN
Undefined Behavior SanitizerRuns as part of CIOnly jenkins, no mailsFinds coding errorsMonitored by Stephan Bergmann
Similar to Asan (Address Sanitizer) and Lsan (Leak Sanitizer)Find other coding errors
1LibreOffice Presentation Template (Community)
Crash reporter
http://crashreport.libreoffice.org/stats/
2LibreOffice Presentation Template (Community)
Crash reporter
3LibreOffice Presentation Template (Community)
Crash report
4LibreOffice Presentation Template (Community)
Crash report
Collects report of crashed LibreOffice instances from usersAggregates the reports based on backtracesReferenced to and from bug reports
If you like to improve your detective skills and fix crashes
34Data for LibreOffice developers
All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License (unless otherwise specified). "LibreOffice" and "The Document Foundation" are registered trademarks. Their respective logos and icons are subject to international copyright laws. The use of these therefore is subject to the trademark policy.
Thank you …
… for listening!… for supporting LibreOffice!