Remove broken dilos apt repo

[ehuss]

CI is currently down because apt is unable to access the repo at dilos.org. It is failing inside the fortanix install script which tries to run apt-get with the error:

5.679 E: Failed to fetch https://apt.dilos.org/dilos/dists/dilos2/InRelease  403  Forbidden [IP: 116.202.240.188 443]

These lines in the Dockerfile were added when Solaris builds were merged into dist-various-2 in #45001. However, Solaris builds were split off in #138699. In that PR, these lines adding the dilos repository weren't removed.

AFAICT, these are no longer necessary.

[rustbot]

r? @marcoieni

rustbot has assigned @marcoieni.
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

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: infra-ci
• infra-ci expanded to Kobzol, Mark-Simulacrum, jdno, jieyouxu, marcoieni
• Random selection from Mark-Simulacrum, jdno, jieyouxu, marcoieni

[ehuss]

@bors treeclosed=100

[rust-bors]

Tree closed for PRs with priority less than 100.

[Mark-Simulacrum]

@bors r+

Should we kick off a try build or raise priority of this?

[rust-bors]

📌 Commit e795c2e has been approved by Mark-Simulacrum

It is now in the queue for this repository.

🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

[Mark-Simulacrum]

@bors p=110

[rust-bors]

☀️ Test successful - CI
Approved by: Mark-Simulacrum
Duration: 4h 7m 53s
Pushing be326a9 to main...

[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 3514361 (parent) -> be326a9 (this PR)

Test differences

Show 2 test diffs

2 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard be326a93323e9b929525b9298f43883ac66b3b2d --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-x86_64-llvm-mingw: 2h 1m -> 1h 30m (-25.6%)
2. x86_64-mingw-1: 2h 52m -> 2h 14m (-22.2%)
3. pr-check-1: 35m 42s -> 27m 48s (-22.1%)
4. dist-x86_64-apple: 1h 56m -> 2h 22m (+22.0%)
5. dist-riscv64-linux: 1h 12m -> 1h 28m (+21.4%)
6. dist-x86_64-solaris: 1h 37m -> 1h 17m (-20.9%)
7. x86_64-mingw-2: 2h 13m -> 2h 37m (+17.9%)
8. dist-android: 28m 45s -> 23m 58s (-16.6%)
9. dist-ohos-armv7: 1h 13m -> 1h 1m (-16.3%)
10. x86_64-gnu-llvm-21: 1h 21m -> 1h 8m (-15.7%)

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.

[Kobzol]

Let's try reopening the tree.

@bors treeopen

[rust-bors]

Tree is now open for merging.

[rust-timer]

Finished benchmarking commit (be326a9): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

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

Max RSS (memory usage)

Results (secondary -2.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.7%	[-2.7%, -2.7%]	1
All ❌✅ (primary)	-	-	0

Cycles

Results (primary 2.3%, secondary 2.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 513.812s -> 511.489s (-0.45%)
Artifact size: 398.43 MiB -> 400.43 MiB (0.50%)

[ehuss]

Approving this for beta. I've asked @weihanglo to include it in #156625.