rust-lang / rust-lang/rust

doctest panics on android

Open
#147,590 18 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-bug I-ICE O-android O-termux T-compiler T-rustdoc
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

The panic happens when i run cargo test after the regular test when starting doc tests

Code

see https://github.com/franklaranja/ratatui-garnish/

Meta

This happens on android (termux) tests ok on github. I can only run stable on android

rustc 1.90.0 (1159e78c4 2025-09-14) (built from a source tarball)
binary: rustc
commit-hash: 1159e78c4747b02ef996e55082b704c09b970588
commit-date: 2025-09-14
host: aarch64-linux-android
release: 1.90.0
LLVM version: 20.1.8

Error output

Doc-tests ratatui_garnish

thread 'rustc' panicked at /home/runner/.termux-build/rust/src/compiler/rustc_data_structures/src/sync/worker_local.rs:28:51:
Unable to verify registry association
stack backtrace:
   0:       0x7a8a46b4f4 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hc3639b3aa7cfc006
   1:       0x7a8a4e7bd8 - core::fmt::write::h9abcbe2e3b8912c5
   2:       0x7a8a496948 - <unknown>
   3:       0x7a8a46b3a8 - <unknown>
   4:       0x7a8a49c5e0 - <unknown>
   5:       0x7a8a49c438 - std::panicking::default_hook::h6d511e236e3ee8d0
   6:       0x7a87434868 - <unknown>
   7:       0x7a8a49d008 - std::panicking::rust_panic_with_hook::hb74822548ee3fb9b
   8:       0x7a8a46bfa8 - <unknown>
   9:       0x7a8a46b9d4 - <unknown>
  10:       0x7a8a49ca4c - __rustc[5affb39ba3b5f18]::rust_begin_unwind
  11:       0x7a8a4e640c - core::panicking::panic_fmt::h085f52b3d2bd7b4f
  12:       0x7a89e17474 - rustc_data_structures[6ea44ddc89345541]::outline::<<rustc_data_structures[6ea44ddc89345541]::sync::worker_local::RegistryId>::verify::{closure#1}, usize>
  13:       0x564c962264 - <unknown>
  14:       0x564c9304b0 - <unknown>
  15:       0x564c6c8ba4 - <unknown>
  16:       0x564c6800a0 - <unknown>
  17:       0x564c6cf61c - <unknown>
  18:       0x7a8a4862f4 - <unknown>
  19:       0x7a8abc3a70 - _ZL15__pthread_startPv
  20:       0x7a8ab646e8 - __start_thread

error: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-rustdoc&template=ice.md

note: rustc 1.90.0 (1159e78c4 2025-09-14) (built from a source tarball) running on aarch64-linux-android

note: compiler flags: --crate-type lib -C embed-bitcode=no

query stack during panic:
end of query stack
error: doctest failed, to rerun pass `--doc`

with backtrace set same output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with cargo test on aarch64-linux-android in Termux, after the regular tests complete and doctests start. Begin with rustc_data_structures/src/sync/worker_local.rs at the RegistryId verification panic and the reported rustdoc/doctest path. Done means the Android doctests complete without the compiler panic while the existing tests continue to pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
compilers, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.