Skip to content

Conversation

Darksonn
Copy link
Contributor

See #7653

This will undo #7652

@Darksonn Darksonn added the A-ci Area: The continuous integration setup label Oct 13, 2025
@ADD-SP
Copy link
Member

ADD-SP commented Oct 13, 2025

I pushed a commit to see if this fix the test failure.

@Darksonn
Copy link
Contributor Author

I don't really understand where this failure comes from. Using an int is the new format, and this should be on the 2025-10-12 nightly, right?

Run cargo nextest run -Zbuild-std --target target-specs/i686-unknown-linux-gnu.json -p tokio --features $TOKIO_STABLE_FEATURES,taskdump
  error: error deserializing custom target JSON for `i686-unknown-linux-gnu`
    ╭─[47:28]
 46 │   ],
 47 │   "target-pointer-width": 32
    ·                            ▲
    ·                            ╰── invalid type: integer `32`, expected a string
 48 │ }
    ╰────

@ADD-SP
Copy link
Member

ADD-SP commented Oct 13, 2025

Emm, this looks strange, the rust-lang/rust#144443 is still there.

@ADD-SP
Copy link
Member

ADD-SP commented Oct 13, 2025

Switching back to cargo test instead of cargo nextest will fix this issue.

Run cargo nextest run -Zbuild-std --target target-specs/i686-unknown-linux-gnu.json -p tokio --features $TOKIO_STABLE_FEATURES,taskdump
  error: error deserializing custom target JSON for `i686-unknown-linux-gnu`
    ╭─[47:28]
 46 │   ],
 47 │   "target-pointer-width": 32
    ·                            ▲
    ·                            ╰── invalid type: integer `32`, expected a string
 48 │ }
    ╰────

@ADD-SP
Copy link
Member

ADD-SP commented Oct 13, 2025

Revert 96647b5 because of a suspicious miscompilation, see #7671 (comment).

@Darksonn Darksonn force-pushed the nightly-2025-10-12 branch 2 times, most recently from c13f424 to bf24380 Compare October 13, 2025 14:48
@Darksonn
Copy link
Contributor Author

I wonder if this mismatch is due to nextest?

@Darksonn
Copy link
Contributor Author

Let's update non-docs checks separately.

@Darksonn Darksonn requested a review from ADD-SP October 13, 2025 15:39
@Darksonn
Copy link
Contributor Author

They were really quick to fix the nextest bug, so let's do the update after all: nextest-rs/nextest#2653

Thanks! @sunshowers

@Darksonn
Copy link
Contributor Author

@taiki-e Do you know why install-action is still installing v0.9.105 when v0.9.106 has been available on github releases for some time?

@taiki-e
Copy link
Member

taiki-e commented Oct 14, 2025

I'm out for work, so I currently can't create the release.

I plan to go home in 2 hours, but there is an update in the main branch, so you can also use it. (The update work is automated, so the main branch is generally up-to-date or up to three hours late, but the owner's involvement is required to create a release.)

@taiki-e
Copy link
Member

taiki-e commented Oct 14, 2025

Created the new release of install-action which contains the latest version of nextest.

@Darksonn
Copy link
Contributor Author

Thanks!

@Darksonn Darksonn merged commit ee313b4 into master Oct 14, 2025
87 checks passed
@Darksonn Darksonn deleted the nightly-2025-10-12 branch October 14, 2025 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-ci Area: The continuous integration setup

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants