Skip to content

Conversation

@github-actions
Copy link

There were a few issues with ARM workflows:

  • not all jobs were run in ARM tests - we do not want to run mysql
    of course, but other tests should be fine to run on ARM
  • some conditions were not updated (we have to somehow duplicate
    amd and arm job definition because we run out of composite
    workflows - so sometimes conditions are not synced)
  • most importantly - we uploaded prek cache in build-info job, but
    that job only run on AMD, not on ARM so the ARM cache was really
    an AMD one (and it caused unterminated strings in doctoc installation

It's not possible to upload same artifact twice in the same job and
since we use prek in several jobs we should make sure that the cache
is only uploaded once per job. This was the reason why it was initially
uploaded in build-info job (and save-cache was set to false elsewhere).
With this PR, we have save-cache in 3 places:

  • basic checks
  • static CI-image bound checks
  • in octopin (Python 3.11)

Basic checks and static checks are mutually exclusive (controlled by
basic-checks-only flag) - so we can safely upload cache in both.

In all other places we only install prek with cache, but we do not
save the cache as artifact.
(cherry picked from commit 59089cd)

Co-authored-by: Jarek Potiuk jarek@potiuk.com

There were a few issues with ARM workflows:

* not all jobs were run in ARM tests - we do not want to run mysql
  of course, but other tests should be fine to run on ARM
* some conditions were not updated (we have to somehow duplicate
  amd and arm job definition because we run out of composite
  workflows - so sometimes conditions are not synced)
* most importantly - we uploaded prek cache in build-info job, but
  that job only run on AMD, not on ARM so the ARM cache was really
  an AMD one (and it caused unterminated strings in doctoc installation

It's not possible to upload same artifact twice in the same job and
since we use prek in several jobs we should make sure that the cache
is only uploaded once per job. This was the reason why it was initially
uploaded in build-info job (and save-cache was set to false elsewhere).
With this PR, we have save-cache in 3 places:

* basic checks
* static CI-image bound checks
* in octopin (Python 3.11)

Basic checks and static checks are mutually exclusive (controlled by
basic-checks-only flag) - so we can safely upload cache in both.

In all other places we only install prek with cache, but we do not
save the cache as artifact.
(cherry picked from commit 59089cd)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Oct 19, 2025
@potiuk potiuk marked this pull request as ready for review October 19, 2025 20:11
@potiuk potiuk merged commit 20e4ace into v3-1-test Oct 19, 2025
5 checks passed
@potiuk potiuk deleted the backport-59089cd-v3-1-test branch October 19, 2025 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant