Marcus Denker

failing tests not related

The test FluidClassDefinitionPrinterTest>>#testChronologyConstants fails because the order of the variables somehow changed.. but only when printing the class definition for the fluid case, the other printouts (non-fluid) sort the class...

but if I download the build artefact, the test fails

fixed by merging https://github.com/pharo-project/pharo/pull/11485

un-fixed by revertion

failing tests not related

failing tests not related

I think I found the problem: Class>>#classSideCompilerClass is wrongly defined. It has to be: ``` classSideCompilerClass "Redefine this method if you want to customize the compiler class for class-side methods"...

ah, I think we do not need to test compilation itself, just check that the method returns the right compiler if we have a class where it is changed.

There are places where we do *not* have a class in hand, or, where it just makes no sense to use the compiler of the class (self class). The notion...