1▶name: Internal Compiler Error
2description: Create a report for an internal compiler error (ICE) in Clippy.
3labels: ["C-bug", "I-ICE"]
· · ·
2▶description: Create a report for an internal compiler error (ICE) in Clippy.
3labels: ["C-bug", "I-ICE"]
4body:
· · ·
5 - type: markdown
6 attributes:
7▶ value: Thank you for finding an Internal Compiler Error! 🧊
8 - type: textarea
9 id: problem
· · ·
31 render: text
32 - type: textarea
33▶ id: error
34 attributes:
35 label: Error output
· · ·
35▶ label: Error output
36 description: >
37 Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in
6 url: https://github.com/rust-lang/stdarch/issues
7 about: Please direct issues about Rust's support for vendor intrinsics to core::arch
8▶ - name: Internal Compiler Error
9 url: https://github.com/rust-lang/rust/issues
10 about: Please report ICEs to the rustc repository
23 python3 -m pip install beautifulsoup4
24 ./ci/build-all-targets.sh
25▶ - name: Upload build errors
26 # We don't want to skip this step on failure
27 if: always()
· · ·
37 if: failure() || cancelled()
38 steps:
39▶ # Download our build error logs
40 - name: Download build errors
41 uses: actions/download-artifact@v8
· · ·
40▶ - name: Download build errors
41 uses: actions/download-artifact@v8
42 with:
· · ·
53 ls failures
54 ~/.local/bin/zulip-send --user $ZULIP_BOT_EMAIL --api-key $ZULIP_API_TOKEN --site https://rust-lang.zulipchat.com \
55▶ --stream miri --subject "Sysroot Build Errors ($(date -u +%Y-%m))" \
56 --message 'It would appear that the [Miri sysroots cron job build]('"https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID"') failed to build these targets:
57 '"$(ls failures)"'
31 # Allowed Failures
32 # Actions doesn't yet support explicitly marking matrix legs as allowed failures
33▶ # https://github.community/t5/GitHub-Actions/continue-on-error-allow-failure-UI-indication/td-p/37033
34 # https://github.community/t5/GitHub-Actions/Why-a-matrix-step-will-be-canceled-if-another-one-failed/td-p/30920
35 # Instead, leverage `continue-on-error`
· · ·
35▶ # Instead, leverage `continue-on-error`
36 # https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error
37 #
· · ·
36▶ # https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error
37 #
38 # Failing due to breaking changes in rustfmt 2.0 where empty
· · ·
78 TARGET: x86_64-unknown-linux-gnu
79 run: ./ci/integration.sh
80▶ continue-on-error: ${{ matrix.allow-failure == true }}
81
1▶name: Internal Compiler Error (for use by automated tooling)
2description: For now, you'll want to use the other ICE template, as GitHub forms have strict limits on the size of fields so backtraces cannot be pasted directly.
3labels: ["C-bug", "I-ICE", "T-compiler"]
· · ·
7 attributes:
8 value: |
9▶ Thank you for finding an Internal Compiler Error! 🧊
10
11 If possible, try to provide a minimal verifiable example.
· · ·
58 id: output
59 attributes:
60▶ label: Current error output
61 description: Please provide the `rustc` output you see
62 placeholder: output
40 WAITING_ON_BORS=$(echo "$JSON" | jq '.labels[] | any(.name == "S-waiting-on-bors"; .)')
41
42▶ # Exit with error if open and S-waiting-on-bors
43 if [[ "$STATE" == "OPEN" && "$WAITING_ON_BORS" == "true" ]]; then
44 exit 1
· · ·
127 id: edit
128 # Don't fail job if we need to open new PR
129▶ continue-on-error: true
130 env:
131 GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
· · ·
132 run: |
133▶ # Exit with error if PR is closed
134 STATE=$(gh pr view cargo_update --repo $GITHUB_REPOSITORY --json state --jq '.state')
135 if [[ "$STATE" != "OPEN" ]]; then
50 name: build-${{ github.sha }}
51 path: target/build.json
52▶ if-no-files-found: error
53
54 other_metrics:
· · ·
83 name: ${{ matrix.names }}-${{ github.sha }}
84 path: target/${{ matrix.names }}.json
85▶ if-no-files-found: error
86
87 generate_final_metrics:
86 call_found=$(objdump -dj .text tests/hello-world/target/release/hello_world | grep -c "call .*mylib.*my_func" ) ||:
87 if [ $call_found -gt 0 ]; then
88▶ echo "ERROR: call my_func found in asm"
89 echo "Test is done with LTO enabled, hence inlining should occur across crates"
90 exit 1
· · ·
101 call_found=$(objdump -dj .text tests/cross_lang_lto/target/release/cross_lang_lto | grep -c "call .*my_add" ) ||:
102 if [ $call_found -gt 0 ]; then
103▶ echo "ERROR: call my_add found in asm"
104 echo "Test is done with cross-language LTO enabled, hence inlining should occur across object files"
105 exit 1
93 SCCACHE_REGION: us-west-1
94 CACHE_DOMAIN: ci-caches.rust-lang.org
95▶ continue-on-error: ${{ matrix.continue_on_error || false }}
96 strategy:
97 # If the user starts multiple jobs in a try build, let them all finish.
· · ·
140 # Actions build on its own, so a hint in the log message is needed to
141 # point it in the right direction.
142▶ - name: configure the PR in which the error message will be posted
143 run: echo "[CI_PR_NUMBER=$num]"
144 env:
· · ·
272 # adding the condition is helpful as this way CI will not silently skip
273 # deploying artifacts from a dist builder if the variables are misconfigured,
274▶ # erroring about invalid credentials instead.
275 if: github.event_name == 'push' || env.DEPLOY == '1' || env.DEPLOY_ALT == '1'
276
· · ·
278 # This step is not critical, and if some I/O problem happens, we don't want
279 # to cancel the build.
280▶ continue-on-error: true
281 run: |
282 if [ -f build/metrics.json ]; then
· · ·
300 # This step is not critical, and if some I/O problem happens, we don't want
301 # to cancel the build.
302▶ continue-on-error: true
303 if: needs.calculate_matrix.outputs.run_type != 'pr'
304 env:
98 # There were no changes detected by Lintcheck
99 # - If a comment exists from a previous run that did detect changes, edit it (--edit-last)
100▶ # - If no comment exists do not create one, the `gh` command exits with an error which
101 # `|| true` ignores
102 gh pr comment "$PR" --body "No changes for ${{ github.event.workflow_run.head_sha }}" --edit-last || true
196 # - mips-unknown-linux-gnu
197 # - mips64-unknown-linux-gnuabi64
198▶ # Lots of errors in QEMU and no real hardware to test on. Not clear if it's QEMU or bad codegen.
199 # - powerpc64-unknown-linux-gnu
200 target_feature: [default]
· · ·
201 include:
202 - { target: powerpc64le-unknown-linux-gnu, target_feature: "+vsx" }
203▶ # Fails due to QEMU floating point errors, probably handling subnormals incorrectly.
204 # This target is somewhat redundant, since ppc64le has altivec as well.
205 # - { target: powerpc-unknown-linux-gnu, target_feature: "+altivec" }
108# PR CI jobs will be automatically registered as Auto CI jobs or overridden. When
109# automatically registered, the PR CI job configuration will be copied as an
110▶# Auto CI job but with `continue_on_error` overridden to `false` (to fail-fast).
111# When overridden, `citool` will check for equivalence between the PR and CI job
112# of the same name modulo `continue_on_error` and `env`.
· · ·
112▶# of the same name modulo `continue_on_error` and `env`.
113pr:
114 - name: pr-check-1
· · ·
117 <<: *job-linux-4c
118 - name: tidy
119▶ continue_on_error: true
120 free_disk: false
121 env:
· · ·
170# definition.
171#
172▶# Auto jobs may not specify `continue_on_error: true`, and thus will fail-fast.
173#
174# Unless explicitly overridden, PR CI jobs will be automatically registered as
· · ·
353 - name: optional-x86_64-gnu-parallel-frontend
354 # This test can be flaky, so do not cancel CI if it fails, for now.
355▶ continue_on_error: true
356 <<: *job-linux-4c
357