rust-lang / rust-lang/socket2

Reenable Hurd CI

Open
#539 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
870
Forks
305
PR merge metrics
No merged PRs in 30d

Description

Currently broken:

  error[E0609]: no field `st_fsid` on type `&stat64`
     --> /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/os/hurd/fs.rs:301:36
      |
  301 |         self.as_inner().as_inner().st_fsid as u64
      |                                    ^^^^^^^ unknown field
      |
  help: a field with a similar name exists
      |
  301 |         self.as_inner().as_inner().st_uid as u64
      |                                    ~~~~~~
  
  For more information about this error, try `rustc --explain E0609`.
  error: could not compile `std` (lib) due to 1 previous error
error: process didn't exit successfully: `/home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/cargo check -Z build-std=std,panic_abort --target i686-unknown-hurd-gnu --manifest-path Cargo.toml --no-default-features` (exit status: 101)

Seems like an issue with Rust's std lib.

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

Start by reproducing the failure with the reported cargo check command for the i686-unknown-hurd-gnu target and inspect the Hurd standard-library error shown in the issue. Trace the repository's Hurd CI configuration and determine what must change for that check to pass. Done means the Hurd CI job is enabled again and completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ci-cd, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.