[Pharo-project] We should run + fix the tests in 1.1
stephane.ducasse at inria.fr
Fri Feb 26 12:54:22 EST 2010
Thanks Thanks Thanks Thanks
This is important that we streamlined the process and fix everything until it works smootly.
Your help and feedback are really cool and important
On Feb 26, 2010, at 5:42 PM, Yanni Chiu wrote:
> Mariano Martinez Peck wrote:
>> I thought we killed all those tests that brings a popup and wait for a
>> user response.
>> Yanni can you tell us which are those tests ?
> There are some tests that I filtered out, and don't run, because they
> stopped the build. That was a few weeks ago. You can see which ones, by
> looking at:
> where you'll find:
> runClasses: (
> TestCase withAllSubclasses reject: [:cls |
> ((cls category asString beginsWith: 'Tests-Traits')
> or: [cls name = 'ImageSegmentTestExport'])
> or: [cls name = 'MCPackageTest']
> named: 'AllTestCases'
> At some point, I'll run these disabled tests to see how they're behaving
> The latest problem, from a few days ago, was that Object>>displayExtent
> was deprecated (maybe it wasn't called displayExtent, but something like
> that). I eventually added:
> Preferences disable: #raiseDeprecatedWarnings.
> so the build would continue in a headless image.
> Prior to that, the Author name was no longer automatically set for
> SUnit. That was solved with:
> Author fullName: 'builder'.
> And before that, some updates caused a dialog to pop up (maybe it was
> the deprecation dialog, I can't remember). That was solved with:
> [Utilities updateFromServer] valueSuppressingAllMessages
> It seems that something always happens. Just have to fix them as they
> come along, or hope that everyone runs a headless build and sees the
> problem and fixes it right away.
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev