Yes, could be.

I just triggered a manual CI build for Zinc HTTP Components and it now also fails, while it succeeded yesterday (there were no code changes).

So there definitely is a problem.

Anyone else seeing problems CI building their projects for Pharo 10 ?

> On 22 Feb 2022, at 11:16, Marcus Denker <marcus.denker@inria.fr> wrote:
>
>
>
>> On 22 Feb 2022, at 11:03, Sven Van Caekenberghe <sven@stfx.eu> wrote:
>>
>> Hi,
>>
>> I just tried to enable Pharo64-10 (not Pharo64-10.0 but that is probably another issue) in a GitHub Action CI using SmalltalkCI.
>>
>> https://github.com/svenvc/ston/blob/master/.github/workflows/CI.yml
>> https://github.com/svenvc/ston/runs/5286121566?check_suite_focus=true
>>
>> This fails with
>>
>> NotFound: [ :cl | cl isPlatformCompatible ] not found in OrderedCollection
>> OrderedCollection(Collection)>>errorNotFound:
>> [self errorNotFound: aBlock] in OrderedCollection(Collection)>>detect: in Block: [self errorNotFound: aBlock]
>> OrderedCollection(Collection)>>detect:ifFound:ifNone:
>> OrderedCollection(Collection)>>detect:ifNone:
>> OrderedCollection(Collection)>>detect:
>> SmalltalkCI class>>platformClass
>> ...
>>
>> Does anyone have any idea ?
>> I seem to remember there were some issue with Metacello attributes, but maybe that is not related.
>>
>
> maybe isPlatformCompatible checks the attributes? These where updated to be pharo10, not pharo9:
>
> New try at removing Pharo 9 metacello attributes #10819
>�� �� �� ��https://github.com/pharo-project/pharo/pull/10819
>
>
>�� �� �� ��Marcus