Skip to content

Make stable hashing names consistent (part 2) #205221

Make stable hashing names consistent (part 2)

Make stable hashing names consistent (part 2) #205221

Triggered via pull request May 4, 2026 23:02
Status Success
Total duration 1h 22m 40s
Artifacts 1

ci.yml

on: pull_request
Calculate job matrix
35s
Calculate job matrix
Matrix: job
publish toolstate
0s
publish toolstate
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 6 warnings
PR - x86_64-gnu-tools
unexpected closing delimiter: `}`
PR - x86_64-gnu-tools
this file contains an unclosed delimiter
PR - x86_64-gnu-tools
unexpected `if` in the condition expression
PR - x86_64-gnu-tools
unexpected closing delimiter: `}`
PR - x86_64-gnu-tools
lifetimes cannot start with a number
PR - x86_64-gnu-tools
this file contains an unclosed delimiter
PR - x86_64-gnu-tools
missing type for `static` item
PR - x86_64-gnu-tools
mismatched closing delimiter: `}`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `server`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `client`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `appservice-api-s`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `appservice-api-c`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `foo-method`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `foo-method`

Artifacts

Produced during runtime
Name Size Digest
doc-156124-c3e5b3e8
21.7 MB
sha256:f20f05a399ee6394ff10a9bbe6f409f428da5be0e5738d25db5489e313baea6f