Inkscape_trunk_scan-build - Build # 72 - Unstable!
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 72 - Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/72/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi Johan,
I like seeing this working as designed (notifying -devel only for regressions). Is it possible to have Jenkins print out what the regression was (or provide a link to the errors) in the emails?
Bryce
On Mon, Apr 27, 2015 at 02:11:27PM -0700, Jenkins (build tester) wrote:
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 72 - Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/72/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 28-4-2015 15:45, Bryce Harrington wrote:
Hi Johan,
I like seeing this working as designed (notifying -devel only for regressions).
You have to manually adjust the threshold for mailing about regressions like this. As you can see from the graph of scan-build number of bugs, it is a slowly decreasing count. Every time the count decreases, one should manually reduce the threshold for flagging the build as unstable. You can do this on the "Inkscape_trunk_scan-build" task configuration page.
Is it possible to have Jenkins print out what the regression was (or provide a link to the errors) in the emails?
Bryce
On Mon, Apr 27, 2015 at 02:11:27PM -0700, Jenkins (build tester) wrote:
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 72 - Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/72/clangScanBuildB...
The link points to the list of potential bugs found, in red you can see the new-found issues: both in libuemf, lines 6578 and 6585. Scan-build is correct here: not a bug, but pretty horrible code if you ask me.
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
If you find these lines too patronizing, you can remove it from the "Inkscape_trunk_scan-build" task configuration.
cheers, Johan
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 73 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/73/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 74 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/74/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 75 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/75/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 76 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/76/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 77 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/77/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 78 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/78/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 79 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/79/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 80 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/80/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 81 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/81/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
Hi developers, Clang scanbuild found a potential bug in recently committed code.
Inkscape_trunk_scan-build - Build # 82 - Still Unstable.
See here which bugs were found (new in red): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/82/clangScanBuildB...
It is paramount to keep our codebase clean with as little compiler warnings as possible, so we can swiftly eradicate newly introduced bugs, to keep Inkscape stable and prevent lengthy dragging bug hunts before releases.
Your friend, Jenkins http://jenkins.inkscape.org
participants (3)
-
Bryce Harrington -
Jenkins (build tester) -
Johan Engelen