[Vm-dev] We *MUST* move the pharos build jobs to another workflow

Eliot Miranda eliot.miranda at gmail.com
Sun Nov 6 01:43:08 UTC 2022

Do you realize that each pharo build builds 6 separate third-party
libraries, and one of these builds acvtually takes neartly *9 minutes*??

grep 'configure: creating ./config.status'
~/Downloads/logs_1273/12_pharo.stack.spur\ for\ macos64x64\ \(ASSERT\).txt
2022-11-05T02:07:32.7844070Z configure: creating ./config.status
2022-11-05T02:07:53.8309190Z configure: creating ./config.status
2022-11-05T02:08:35.1150920Z configure: creating ./config.status
2022-11-05T02:09:01.5592860Z configure: creating ./config.status
2022-11-05T02:10:21.7823030Z configure: creating ./config.status
2022-11-05T02:19:04.2409860Z configure: creating ./config.status

We are wasting electricity, contributing to the climate problem, blinding
ourselves with crap no one uses (I can't see if the Squeak VM builds ar
e OK cuz they get cancelled when the f***ing pharoi build fails), for what

On Sat, Nov 5, 2022 at 6:34 PM Eliot Miranda <eliot.miranda at gmail.com>

> Can we *PLEASE* either move the pharo builds to another workflow or delete
> them altogether?
> _,,,^..^,,,_
> best, Eliot

best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20221105/850ad03d/attachment.html>

More information about the Vm-dev mailing list