ci: move dist-x86_64-linux job to codebuild

[marcoieni]

Related to rust-lang/infra-team#188
This job was already in codebuild, but in #141388 we moved it back to GitHub Actions to do the rust-lang-ci migration easily.
This PR moves it back to codebuild. It also moves the try job.
r? @Kobzol

[marcoieni]

@bors try

[bors]

⌛ Trying commit dc18763 with merge 9961326...

[bors]

💔 Test failed - checks-actions

[marcoieni]

@bors try

[bors]

⌛ Trying commit dc18763 with merge 51e8053...

[Kobzol]

Did you configure the environment for both try and auto branches on Codebuild?

[bors]

☀️ Try build successful - checks-actions
Build commit: 51e8053 (51e80539c8286ac8c15a5d05294031d3dca32598)

[marcoieni]

I didn't have to configure branches as far as I remember

[marcoieni]

@rustbot ready

[Kobzol]

Ok, let's try.

@bors r+ rollup=never

[bors]

📌 Commit dc18763 has been approved by Kobzol

It is now in the queue for this repository.

[bors]

⌛ Testing commit dc18763 with merge d1ee190...

[marcoieni]

I manually canceled this job because the runner wasn't starting

[bors]

💔 Test failed - checks-actions

[marcoieni]

maybe this was due to the github incident. 🤔

[bors]

📌 Commit 1e7c437 has been approved by Kobzol

It is now in the queue for this repository.

[jieyouxu]

@bors p=6 (ahead of rollups)

[bors]

⌛ Testing commit 1e7c437 with merge e2adb60...

[alex]

The dist-x86_64-linux job doesn't appear to be starting

[marcoieni]

yes, you are right, I canceled the workflow. I'll have a look tomorrow

[bors]

💔 Test failed - checks-actions

[marcoieni]

rust-lang/simpleinfra#720 probably fixed the issue.
Jakub, can approve this PR at your name tomorrow morning if I don't see other 400s from the webhook dashboard?

[Kobzol]

Sure, feel free to r=me.

[marcoieni]

I haven't seen that error anymore. Let's try again

@bors r+

[bors]

💡 This pull request was already approved, no need to approve it again.

• This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.
• There's another pull request that is currently being tested, blocking this pull request: [do not merge] CI experiments #112049

[bors]

📌 Commit 1e7c437 has been approved by marcoieni

It is now in the queue for this repository.

[marcoieni]

@bors r=Kobzol

[bors]

💡 This pull request was already approved, no need to approve it again.

• There's another pull request that is currently being tested, blocking this pull request: [do not merge] CI experiments #112049

[bors]

📌 Commit 1e7c437 has been approved by Kobzol

It is now in the queue for this repository.

[marcoieni]

I forgot to r=Kobzol initially.

[bors]

⌛ Testing commit 1e7c437 with merge 77101fe...

[marcoieni]

the job started 🥳

[bors]

☀️ Test successful - checks-actions
Approved by: Kobzol
Pushing 77101fe to master...

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing cb678b9 (parent) -> 77101fe (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 77101febcc9662a076ff43887497cd5b30674d93 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. dist-apple-various: 5980.3s -> 7273.4s (21.6%)
2. x86_64-apple-1: 8585.4s -> 6886.6s (-19.8%)
3. aarch64-gnu: 6702.0s -> 7927.2s (18.3%)
4. aarch64-gnu-debug: 4098.8s -> 4784.3s (16.7%)
5. x86_64-apple-2: 4171.1s -> 4791.8s (14.9%)
6. dist-x86_64-apple: 8073.6s -> 8899.7s (10.2%)
7. dist-x86_64-netbsd: 4802.8s -> 5243.4s (9.2%)
8. dist-x86_64-linux: 5479.7s -> 4981.2s (-9.1%)
9. aarch64-apple: 4579.1s -> 4964.7s (8.4%)
10. dist-i586-gnu-i586-i686-musl: 5538.9s -> 5136.9s (-7.3%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (77101fe): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.2%	[-0.6%, -0.1%]	6
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary 1.9%, secondary 3.2%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	6.1%	[6.1%, 6.1%]	1
Regressions ❌ (secondary)	8.5%	[8.5%, 8.5%]	1
Improvements ✅ (primary)	-2.2%	[-2.2%, -2.2%]	1
Improvements ✅ (secondary)	-2.0%	[-2.0%, -2.0%]	1
All ❌✅ (primary)	1.9%	[-2.2%, 6.1%]	2

Cycles

Results (secondary -2.0%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.0%	[-2.3%, -1.8%]	2
All ❌✅ (primary)	-	-	0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 778.889s -> 777.676s (-0.16%)
Artifact size: 368.42 MiB -> 368.53 MiB (0.03%)