CI: use free runners for 3 fast windows jobs

[MarcoIeni]

I noticed that some windows jobs running on large runners are significantly faster than the rest of the auto build.

Here's some data based on the latest 97 auto builds:

• Average of these jobs:
  • dist-i686-mingw: 88 minutes
  • dist-x86_64-mingw: 86 minutes
  • dist-x86_64-msvc-alt: 81 minutes
• Minimum duration of the auto builds: 136 minutes (2h 16 min).
• Average duration of the auto build: 155 minutes (2h 35 min).

In this PR I switch these jobs from large runners to free runners, to see if we can save some resources.

Imo if the try builds don't take longer than the average duration of the auto build we could merge this PR.

try-job: dist-i686-msvc
try-job: dist-i686-mingw
try-job: dist-x86_64-mingw
try-job: dist-x86_64-msvc-alt

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[MarcoIeni]

@bors try

[bors]

⌛ Trying commit 59915ef with merge 1d5e9fc...

[MarcoIeni]

I realized is also worth testing dist-i686-msvc. I'll do it in another pr maybe

[jieyouxu]

@MarcoIeni btw for whatever reason a few dist-* jobs also run tests which are not run by default in try-jobs (they need DIST_TRY_BUILD=1 set), though it should matter that much for overall time.

there's a DIST_TRY_BUILD env var in the jobs, comment that for your try build and it'll run the opt-dist tests

I haven't bothered to check if the ones you're running here have such tests.

EDIT: I messed up the order, it's actually DIST_TRY_BUILD=1 unset

[MarcoIeni]

Ok, thanks for looking into this!
What I'm trying to do here is check how long these jobs will take in the auto build.
Do you think I need to change something in my approach?

If I need to set that environment variable, how do I do it? By editing the workflow file maybe?

[jieyouxu]

Ok, thanks for looking into this! What I'm trying to do here is check how long these jobs will take in the auto build. Do you think I need to change something in my approach?

If I need to set that environment variable, how do I do it?

I'm not sure if these specific set of dist-* jobs have (post opt-dist) tests. If you need to unset that env var (if the dist-* jobs do have extra tests), you would comment DIST_TRY_BUILD=1 out like faa347a.

(I mixed up, it should be unsetting that env var, not set)
EDIT: yes, by editing jobs.yml AFAIK

[bors]

☀️ Try build successful - checks-actions
Build commit: 1d5e9fc (1d5e9fc55459143d612ac42e8caa1d4ebf0aabcd)

[MarcoIeni]

Here's the result of the try job

Imo they are all acceptable except for dist-aarch64-msvc which I will revert now.
I'll substitute it with dist-i686-msvc instead.

I edited the pr description to change bors try.

[MarcoIeni]

@bors try

[bors]

⌛ Trying commit 7ea21e5 with merge 4420845...

[MarcoIeni]

The job dist-i686-msvc is running for too long, so I don't want to move it to free runners.

I will push a commit where I remove dist-i686-msvc.

However the other jobs look good

[MarcoIeni]

@Mark-Simulacrum I think we could merge this PR and monitor how these jobs perform in the auto builds in the next week. What do you think?

[Mark-Simulacrum]

I'm fine with that, r=me

[MarcoIeni]

Force pushed, let me know if I need to do something else 👍

EDIT: Kobzol told me I can approve this with bors, I'll do it in the next comment.

[MarcoIeni]

@bors r=Mark-Simulacrum

[bors]

📌 Commit 183599f has been approved by Mark-Simulacrum

It is now in the queue for this repository.