Skip to content

chore: remove aarch64-pc-windows-msvc #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 1, 2025
Merged

Conversation

ynqa
Copy link
Owner

@ynqa ynqa commented Apr 1, 2025

Since I encountered the following errors on building for the target aarch64-pc-windows-msvc. (Do you know about the error @jnichols0?)

Therefore, on release of v0.6.0, aarch64-pc-windows-msvc target is canceled

@ynqa ynqa merged commit 389c331 into main Apr 1, 2025
7 checks passed
@ynqa ynqa deleted the remove-aarch64-pc-windows-msvc branch April 1, 2025 13:26
@jnichols0
Copy link
Contributor

@ynqa, apologies, it is working locally for me via dist build -t aarch64-pc-windows-msvc. Could you point me to the errors you saw?

@ynqa
Copy link
Owner Author

ynqa commented Apr 2, 2025

@jnichols0 No worry :)

The error did not occur in my local environment; it happened in an actual GitHub Actions run:

excerpt
Run # Actually do builds and make zips and whatnot
  # Actually do builds and make zips and whatnot
  dist build --tag=v0.6.0 --print=linkage --output-format=json --artifacts=local --target=aarch64-pc-windows-msvc > dist-manifest.json
  echo "dist ran successfully"
  shell: sh -e {0}
  env:
    GH_TOKEN: ***
    BUILD_MANIFEST_NAME: target/distrib/aarch64-pc-windows-msvc-dist-manifest.json

  × We encountered an issue trying to read your workspace
  ├─▶   × `cargo metadata` execution failed
  │   
  ╰─▶ `cargo metadata` exited with an error:     Updating crates.io index
       Downloading crates ...
        Downloaded anstream v0.6.13
        Downloaded foreign-types-shared v0.3.1
        Downloaded derive_builder_macro v0.20.2
        Downloaded libredox v0.1.3
        Downloaded num-conv v0.1.0
        Downloaded lock_api v0.4.11
        Downloaded miniz_oxide v0.7.4
        Downloaded darling_core v0.20.10
        Downloaded windows-targets v0.48.5
        Downloaded thiserror-impl v1.0.64
        Downloaded windows-targets v0.52.6
        Downloaded tokio-stream v0.1.17
        Downloaded weezl v0.1.8
        Downloaded zerocopy-derive v0.7.32
        Downloaded serde v1.0.219
        Downloaded toml_edit v0.22.24
        Downloaded rayon-core v1.12.1
        Downloaded zerocopy v0.7.32
        Downloaded winnow v0.7.4
        Downloaded serde_json v1.0.140
        Downloaded jpeg-decoder v0.3.1
        Downloaded x11rb v0.13.1
        Downloaded regex v1.10.4
        Downloaded objc2-foundation v0.2.2
        Downloaded unicode-width v0.2.0
        Downloaded libc v0.2.169
        Downloaded syn v2.0.95
        Downloaded rayon v1.10.0
        Downloaded regex-syntax v0.8.3
        Downloaded linux-raw-sys v0.4.14
        Downloaded rustix v0.38.34
        Downloaded either v1.15.0
        Downloaded windows_x86_64_gnullvm v0.52.6
        Downloaded windows_aarch64_gnullvm v0.48.5
        Downloaded windows_x86_64_gnullvm v0.48.5
      error: failed to parse manifest at `/usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/promkit-
      widgets-0.1.0/Cargo.toml`
      
      Caused by:
        feature `edition2024` is required
      
        The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this
      version of Cargo (1.83.0 (5ffbef321 2024-10-29)).
        Consider trying a newer version of Cargo (this may require the nightly release).
        See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about
      the status of this feature.
      

Error: Process completed with exit code 255.

@jnichols0
Copy link
Contributor

I see, it needs rust 1.85 but is being built with 1.83. I assumed that rustup would install the latest version in the CI pipeline but I guess it didn't.

@ynqa
Copy link
Owner Author

ynqa commented Apr 8, 2025

it needs rust 1.85 but is being built with 1.83

@jnichols0 Thank you for looking into it. I'll dig a bit deeper myself 🫡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants