On 18 December 2012 02:11, David T. Lewis <lewis at mail.msen.com> wrote:
> On Mon, Dec 17, 2012 at 06:08:03PM -0800, glenpaling wrote:
>> Frank, I downloaded the SqueakTrunk #64 build artifacts directly from
>> http://www.squeakci.org/job/SqueakTrunk/lastBuild/?. Test have no Monticello
>> failures just:
>>
>> 3272 run, 3250 passes, 18 expected failures, 4 failures, 0 errors, 0
>> unexpected passes
>>
>> LocaleTest>>#testLocaleChanged
>> SocketTest>>#testSocketReuse
>> SocketTest>>#testUDP
>> WeakSetInspectorTest>>#testSymbolTableM6812
>>
>
> I think these Monticello failures are some kind of intermittent junk related
> to mock classes created as part of the tests. I do not know the cause, but
> I'm pretty sure it is not something to worry about with respect to validating
> the upcoming release.

I agree with respect both to the failures above and the raft of
failures reported earlier in the thread.

I _suspect_ that the raft of failures are because MCTestCase >>
tearDown fails to reset the mock package/s state, _possibly_ because
the AuthorInitials are not set by default.

frank

> Dave
>
>