Build problem (continuous integration)

[demoitem]

I'm not really up to speed with the continuous integration but I think
there is a small problem with the script. I have upgraded cm3cg with
the addition of extra IR instructions and with that updated m3cg.h to
a new version (following precedent). Therefore cm3cg should be shipped
early on in the build to avoid version mismatch.
Can someone fix the build script?

[VictorMiasnikov]

} there is a small problem with the script

Yes, it is

} Can someone fix the build script?

I have some ideas. I has been implement someone.

In short: script is good, but we should upgrade *distrib* and *boot* in Releases

P.S.

A-la:

      release:
        default: https://github.com/VictorMiasnikov/cm3/releases/download/d5.11.9-ZZYYXX-20221017_13-20
        required: false
        type: string
      bootstrap:
        default: cm3-boot-AMD64_LINUX-None.tar.xz
        required: false
        type: string

[VictorMiasnikov]

It looks like my idea is "worked" idea:

https://github.com/VictorMiasnikov/cm3/actions/runs/3265830615

[VictorMiasnikov]

"More green jobs" ( near 99/100) variant:
https://github.com/VictorMiasnikov/cm3/actions/runs/3274227685

[VictorMiasnikov]

(...)

[VictorMiasnikov]

(...)

[VictorMiasnikov]

(...)

[VictorMiasnikov]

( Psevdo-reposted post)

demoitem}
demoitem} This whole CI thing might need examination. I get they are testing
demoitem} on all architectures but as far as I can tell they are only using the C
demoitem} backend whereas they should be testing other backends as well.
demoitem} Also which branches do they test? Surely not all branches. How
demoitem} would one get them to test a particular branch? And while we are at it,
demoitem} I think a bit of judicious pruning of some of those github branches would be
demoitem} beneficial.
demoitem}

[VictorMiasnikov]

(...)

[VictorMiasnikov]

(...)

[VictorMiasnikov]

(...)

[VictorMiasnikov]

demoitem}
demoitem} This whole CI thing might need examination. I get they are testing
demoitem} on all architectures but as far as I can tell they are only using the C
demoitem} backend whereas they should be testing other backends as well.
demoitem} Also which branches do they test? Surely not all branches. How
demoitem} would one get them to test a particular branch? And while we are at it,
demoitem} I think a bit of judicious pruning of some of those github branches would be
demoitem} beneficial.
demoitem}

demoitem} This whole CI thing might need examination.

May be / "Why not?"

demoitem} only using the C backend

This has fixed.

I can prepare PR

demoitem} How would one get them to test a particular branch?

I already do testing "by G. Actions CI/CD" of "a particular branch", i.e. non-master branch

demoitem} Also which branches do they test? Surely not all branches.

It look like "tests are run for new commit on all branches".

( I will be delete this msg. and repost it)