Re: [Inkscape-devel] win32 build broken test-stubs.cpp
by Bob Jamison
Jasper, hi,
Well, I think (and this happens a lot) that this is the old symptom where
the files which are compiled for win32 and those in the unix
Automake files are not always in sync.
So a person building on Linux or OSX might never see the problem.
bob
On 5/8/2009 3:26 AM, Jasper van de Gronde wrote:
>
> This makes me wonder if we can't set up some machine to regularly do
> these tests (and the rendering tests as well while we're at it).
> Running all the tests once a day (the unit tests take about a minute,
> excluding build time) would already be an enormous improvement.
Mozilla does this, with the results being automatically updated on their
web site. Would be a good idea.
bob
14 years, 4 months
Re: [Inkscape-devel] win32 build broken test-stubs.cpp
by Jasper van de Gronde
Jasper van de Gronde wrote:
> Bob Jamison wrote:
>> That was a good find, Adib! :)
>>
>> Yes, adding test-stubs.cpp to the 'excludes' list does fix the
>> build.
>>
>>
>> But someone needs to look at test-stubs.cpp and get it back into
>> sync with the current fields in Preferences. Or take it out, I guess.
>
> Perhaps the person who actually broke the tests? I know it can be a
> pain, but people (and frankly that includes me) really should run these
> tests more often. At the moment the tests even CRASH for me...
Correction, after a build clean it doesn't crash anymore. Currently 14
out of 160 tests fail on my system.
> This makes me wonder if we can't set up some machine to regularly do
> these tests (and the rendering tests as well while we're at it). Running
> all the tests once a day (the unit tests take about a minute, excluding
> build time) would already be an enormous improvement.
>
> If we want it a little fancier it could try and pinpoint the exact
> revisions which caused the problem and possibly even notify the
> developers mailing list (and/or the individual developers involved).
>
14 years, 4 months
Re: [Inkscape-devel] Deactivate knotholder?
by Josh Andler
I seem to recall that Max had added it a while back relating to the Geometry
Tool.
On May 6, 2009 5:38 AM, <J.B.C.Engelen@...1578...> wrote:
> -----Original Message----- > From: Steren [mailto:
steren.giannini@...400...] > Sent: Thursday, Ap...
Sorry for the delayed reply.
I do not know where this checkbox came from; hopefully we can find it in
the svn logs.
-Johan
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ Inkscape-devel mailing list
Inkscape-devel@...2193...
14 years, 4 months
Deactivate knotholder?
by bulia byak
What is the purpose of this checkbox in LPE parameters? Does it work
at all? I tried it with Knot, but checking it does not remove the knot
on the intersection.
I propose to remove it because it does not seem to serve a useful
function, and because it uses the absolutely technical term
"knotholder" which users have no idea about.
--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org
14 years, 4 months
Re: [Inkscape-devel] win32 build broken test-stubs.cpp
by Bob Jamison
That was a good find, Adib! :)
Yes, adding test-stubs.cpp to the 'excludes' list does fix the
build.
But someone needs to look at test-stubs.cpp and get it back into
sync with the current fields in Preferences. Or take it out, I guess.
bob (ishmal)
-----Original Message-----
>From: the Adib <theadib@...1439...>
>Sent: May 5, 2009 4:08 AM
>To: Inkscape <inkscape-devel(a)lists.sourceforge.net>
>Subject: [Inkscape-devel] win32 build broken test-stubs.cpp
>
>Hello,
>
>the win32 build is broken and I don't know why.
>The file that blocks the build is test-stubs.cpp. AS this probably
>belongs to testing code I commented this out of build.xml. pls see the
>patch below.
>
>HTH, Adib.
>---
>
>D:\projekte\inkscape\inkscape_trunk>svn diff
>Index: build.xml
>===================================================================
>--- build.xml (revision 21287)
>+++ build.xml (working copy)
>@@ -299,6 +299,7 @@
> <exclude name="bonobo/.*"/>
> <exclude name="deptool.cpp"/>
> <!--<exclude name="test-main.cpp"/>-->
>+ <exclude name="test-stubs.cpp"/>
> <!--<exclude name="test-src.cpp"/>-->
> <exclude name="display/test-display.cpp"/>
> <exclude name="display/testnr.cpp"/>
>@@ -419,6 +420,7 @@
> <!-- CxxTest -->
> <exclude name="test-main.o"/>
> <exclude name="test-src.o"/>
>+ <exclude name="test-stubs.o"/>
> <exclude name="display/test-display.o"/>
> <exclude name="helper/test-helper.o"/>
> <exclude name="libnr/nr-compose-reference.o"/>
>@@ -577,6 +579,7 @@
> <fileset dir="${build}">
> <include name="obj/test-main.o"/>
> <include name="obj/test-src.o"/>
>+ <include name="obj/test-stubs.o"/>
> <include name="obj/display/test-display.o"/>
> <include name="obj/helper/test-helper.o"/>
> <include name="obj/libnr/nr-compose-reference.o"/>
>
>------------------------------------------------------------------------------
>The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>production scanning environment may not be a perfect world - but thanks to
>Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
>Series Scanner you'll get full speed at 300 dpi even with all image
>processing features enabled. http://p.sf.net/sfu/kodak-com
>_______________________________________________
>Inkscape-devel mailing list
>Inkscape-devel(a)lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/inkscape-devel
14 years, 4 months
win32 build broken test-stubs.cpp
by the Adib
Hello,
the win32 build is broken and I don't know why.
The file that blocks the build is test-stubs.cpp. AS this probably
belongs to testing code I commented this out of build.xml. pls see the
patch below.
HTH, Adib.
---
D:\projekte\inkscape\inkscape_trunk>svn diff
Index: build.xml
===================================================================
--- build.xml (revision 21287)
+++ build.xml (working copy)
@@ -299,6 +299,7 @@
<exclude name="bonobo/.*"/>
<exclude name="deptool.cpp"/>
<!--<exclude name="test-main.cpp"/>-->
+ <exclude name="test-stubs.cpp"/>
<!--<exclude name="test-src.cpp"/>-->
<exclude name="display/test-display.cpp"/>
<exclude name="display/testnr.cpp"/>
@@ -419,6 +420,7 @@
<!-- CxxTest -->
<exclude name="test-main.o"/>
<exclude name="test-src.o"/>
+ <exclude name="test-stubs.o"/>
<exclude name="display/test-display.o"/>
<exclude name="helper/test-helper.o"/>
<exclude name="libnr/nr-compose-reference.o"/>
@@ -577,6 +579,7 @@
<fileset dir="${build}">
<include name="obj/test-main.o"/>
<include name="obj/test-src.o"/>
+ <include name="obj/test-stubs.o"/>
<include name="obj/display/test-display.o"/>
<include name="obj/helper/test-helper.o"/>
<include name="obj/libnr/nr-compose-reference.o"/>
14 years, 4 months
PLEASE ACTUALLY CHECK BEFORE YOU LEAP!!!
by Jon A. Cruz
Krzysztof, PLEASE ACTUALLY READ AND TEST CODE BEFORE JUMPING TO
CONCLUSIONS!!!
In regards to bug #367752,
I DID ADDRESS THAT "CRITICAL" POINT IN THE CODE, AND COMMENTED ON IT!!!
IT *WAS* TESTED!!!
Please do *NOT* flip someone else's bugs away from fixed unless you
ACTUALLY OBSERVE IT IS BROKEN!!!!
Please review the comments attached to the bug.
CAREFULLY REVIEW SVN REVISION #21281
Again.. PLEASE ACTUALLY COME AND TALK WITH THE OTHER DEVELOPERS.
DON"T JUST GUESS BLIND!
14 years, 4 months
Bug Hunt for 0.47
by Joshua A. Andler
Hey All,
As with other things, why fix what isn't broken? This release' bug hunt
is a combination of the last two bug hunts in terms of functionality and
scoring. Again, this is liberally recycling bryce's announcements. ;)
Traditionally, we specify a point target for us to reach, and award us
points based on the severity of the bug: 3, 6, 9, or 12 points for low,
medium, high, and critical. This releases goal is again 500 points.
We only give points for true bug fixes - not bugs simply closed due to
being dupes, invalid, works-for-me, or whatnot. As with the last
release, we won't count fixes to the website, translations, docs, and so
on, we'll award points only for true code-level bug fixes.
While our Frost goal is to close 500 points worth of *any* bug, when we
get to Freeze our goal will be to have 0 Critical bugs, so efforts
put into closing Crits will be doubly good!
As with 0.45's bug hunt, we do want to encourage work on old bugs. So,
points will be doubled for any bugs fixed that have been open for a year
or more.
Bug Hunt Goal: 500 points
Current: 0 points
Low: 3 - 6 pts
Med: 6 - 12 pts
High: 9 - 18 pts
Critical: 12 - 24 pts
We especially need testers (and bug fixers) for Windows and OSX. We have
a tendency to have a number of platform specific bugs, so all the help
we can get would be appreciated.
If you are a Windows or OSX user, you too can be a big help, simply by
browsing the bug tracker and see if you can reproduce the bug, and then
add a comment on the bug one way or the other. No technical experience
required. :-)
I will be posting scoring as we have in the past. Note that the
"current" score above is actually incorrect as a few bugs have been
fixed since the Frost began. The first scoreboard will be posted by
mid-week and will include all fixes since Frost began.
Cheers,
Josh
14 years, 4 months
