I did not experience regressions. Note that I was unable to do make -k check
because it failed on r48518 as well (maybe because of my build environment;
cygwin) but I have done make run-test on critical assemblies and compared
the results. There were no change in passed and failed test count and test
numbers.
I have little experience in regression tracking. If you are more experienced
I would appreciate if you could give me some hints and commands that help
regression tracking.
I have never tested or compiled r48519 because it is the update of mcs tree
only. r48520 is the update of mono tree. If you use r48519 it may result in
errors. I checked out mcs and mono separatedly and I was unable to make svn
to commit them in a single command. If you know the solution please let me
know.
Unless I mistyped something the version patch should not have any effects
that result in regressions because I did not (wanted to) modify code
behaviour.
Could you please send me (or to the list if you want) some test results
pointing out the regressions?
Kornél
----- Original Message -----
From: "Sebastien Pouliot" <[EMAIL PROTECTED]>
To: "Kornél Pál" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Friday, August 19, 2005 3:26 PM
Subject: Re: [Mono-dev] corlib version and #if symbol questions
On Thu, 2005-18-08 at 22:17 +0200, Kornél Pál wrote:
Thanks for the information. The patch is now in SVN.
I've noticed. Sadly r48519 resulted in 31 regressions in the default
profile (NET_1_0) and a little more in the NET_2_0 profile.
Please do run the unit tests _and_ ensure that no regressions occurs
before committing anything (small or big) into SVN.
--
Sebastien
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list
