Why is latest CI build still GCC 13.2 and not 14.2?

[TommyMurphyTM1234]

The PR to bump the toolchain to GCC 14.2 was merged a few weeks ago:

• Bump gcc into 14.2 release version. #1531

but the latest CI build of the toolchain is still GCC 13.2:

• https://github.com/riscv-collab/riscv-gnu-toolchain/releases

Why?

[TommyMurphyTM1234]

Something to do with this perhaps?

https://github.com/riscv-collab/riscv-gnu-toolchain/actions/runs/11206503521/job/31147348631

Run curl -sL https://api.github.com/repos/$GITHUB_REPOSITORY/commits | jq -r '[.[]][0]' > $HOME/commit.json
Latest Repository activity : [1](https://github.com/riscv-collab/riscv-gnu-toolchain/actions/runs/11206503521/job/31147348631#step:2:1)727319790 Jiawei https://github.com/riscv-collab/riscv-gnu-toolchain/commit/795267df36fcf1269f2bd596ac42e0e91ad9cfd3
Repository active last 261 hours ago
Error:  Repository not updated : event<schedule> not allowed to modify stale repository
Error: Process completed with exit code 1.

[cmuellner]

Thanks for bringing this up! I noticed the request from @szedani, but illness kept me from moving this thing forward.

In essence, the reason why the CI builds fail is that Ubuntu 20.04 LTS is too old to build a recent version of QEMU.

[TommyMurphyTM1234]

Thanks @cmuellner - hope you're feeling better now/soon!

I just saw your comment here:

• Bump gcc into 14.2 release version. #1531 (comment)

[cmuellner]

The proposed fix is to drop Ubuntu 20.04 (see #1570).

[TommyMurphyTM1234]

The proposed fix is to drop Ubuntu 20.04 (see #1570).

Thanks @cmuellner - I had actually seen that but failed to join the dots... :-)

[TommyMurphyTM1234]

When does a "release" job get triggered?
It doesn't seem to have happened even though the PR in question was merged yesterday:

• CI: Drop Ubuntu 20.04 and add Ubuntu 24.04 #1570

[cmuellner]

The PR was merged today, not yesterday.

The nightly release is defined here: https://github.com/riscv-collab/riscv-gnu-toolchain/blob/master/.github/workflows/nightly-release.yaml
The relevant part is:

on:
  schedule:
    - cron:  '0 0 * * ?'

Cron columns are minute, hour, day-of-month, month-of-year, day-of-week.
So, the action is triggered at midnight (likely 00:00 UTC) on any day of the month, any month of the year, and any day of the week.

[TommyMurphyTM1234]

Thanks @cmuellner. 👍
Timezone issues confused me - I'm in Ireland and according to GitHub the PR was merged yesterday for me. :-)

[cmuellner]

Here in Austria the PR page states "kito-cheng merged commit cbd3989 into riscv-collab:master 5 hours ago". And when I hover over the "5 hours ago" the hover text says "Oct 10, 2024, 11:42 AM GMT+2".

[TommyMurphyTM1234]

Here in Austria the PR page states "kito-cheng merged commit cbd3989 into riscv-collab:master 5 hours ago". And when I hover over the "5 hours ago" the hover text says "Oct 10, 2024, 11:42 AM GMT+2".

Sorry - my mistake. I glanced at the PR and misread this as "committed" and assumed that it was the merging of the PR.

[TommyMurphyTM1234]

Should be fixed by this:

• CI: Drop Ubuntu 20.04 and add Ubuntu 24.04 #1570

[TommyMurphyTM1234]

Should be fixed by this:

• CI: Drop Ubuntu 20.04 and add Ubuntu 24.04 #1570

Still not addressed:

• CI: Use merge time for activity check #1582 (comment)

[TommyMurphyTM1234]

See also...

• Nightly release CI action is broken #1591

[TommyMurphyTM1234]

Closing this since it's effectively already covered here:

• Nightly release CI action is broken #1591

And also by various work in progress PRs.

• Update build workflow #1608
• Add Submodule Caching to Toolchain Generation #1607
• CI/CD: Switch from gzip to XZ for archive compression #1606
• Use Shallow Submodule Init to Reduce Clone Times #1605
• Free up space in GitHub Actions Runners for remaining jobs #1601