StéphaneDucasse

Noury I was wondering if we should not do something else: introduce a runWithProgress: because with your changes any runWith: is impacted.

Here is typical use ``` reportForFolder: parent startingFrom: file | reporter checker validator | reporter := self new. checker := MicReferenceChecker new. checker fileSystem: parent. checker checkProject: file. reporter addResults:...

is the way ``` StOpenFileOrDirectoryPresenter new title: 'Select a change file'; defaultFolder: FileLocator image parent asFileReference; openModal ```

I revisited some tests of MicRawBlockTest and they look ok so I have time to investigate more this case.

I think that the refactoring is black listing Object.

We have [osx-64 / Tests-osx-64 / MacOSX64.ClassParser.Tests.OCClassBuilderTest.testCreateNormalClassWithTraitComposition](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/misc%252Fbump-iceberg/1/testReport/junit/MacOSX64.ClassParser.Tests/OCClassBuilderTest/osx_64___Tests_osx_64___testCreateNormalClassWithTraitComposition/) [osx-64 / Tests-osx-64 / MacOSX64.NewTools.Debugger.Tests.StDebuggerInspectorTest.testUpdateLayoutForContextsWithAssertionFailure](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/misc%252Fbump-iceberg/1/testReport/junit/MacOSX64.NewTools.Debugger.Tests/StDebuggerInspectorTest/osx_64___Tests_osx_64___testUpdateLayoutForContextsWithAssertionFailure/) [osx-64 / Tests-osx-64 / MacOSX64.NewTools.Debugger.Tests.StDebuggerTest.testUpdateLayoutForContextsIfAssertionFailure](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/misc%252Fbump-iceberg/1/testReport/junit/MacOSX64.NewTools.Debugger.Tests/StDebuggerTest/osx_64___Tests_osx_64___testUpdateLayoutForContextsIfAssertionFailure/) [osx-64 / Tests-osx-64 / MacOSX64.ReleaseTests.ReleaseTest.testNoShadowedVariablesInMethods](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/misc%252Fbump-iceberg/1/testReport/junit/MacOSX64.ReleaseTests/ReleaseTest/osx_64___Tests_osx_64___testNoShadowedVariablesInMethods/) [osx-64 / Tests-osx-64 / MacOSX64.ReleaseTests.ReleaseTest.testThatThereAreNoSelectorsRemainingThatAreSentButNotImplemented](https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/misc%252Fbump-iceberg/1/testReport/junit/MacOSX64.ReleaseTests/ReleaseTest/osx_64___Tests_osx_64___testThatThereAreNoSelectorsRemainingThatAreSentButNotImplemented/) [unix-64 / Tests-unix-64...

I imagine that this is unrelated now this is a bit sad to have a non green build for P13

produces  

The checker should report the figures that are not referenced.

should be easy to do and a simple scenario for the extensibility.