Skip to content

ci: Pin an older nextest version #3088

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
Jan 3, 2025
Merged

ci: Pin an older nextest version #3088

merged 1 commit into from
Jan 3, 2025

Conversation

flub
Copy link
Contributor

@flub flub commented Jan 3, 2025

Description

We get very weird errors from nextest, I suspect this is a regression.
This version is 3 months old, which is probably something nice to try.

This does not yet do this everywhere, e.g. windows still installs the
latest. But this is enough to see if it helps.

Breaking Changes

Notes & open questions

Change checklist

  • Self-review.
  • Documentation updates following the style guide, if relevant.
  • Tests if relevant.
  • All breaking changes documented.

We get very weird errors from nextest, I suspect this is a regression.
This version is 3 months old, which is probably something nice to try.

This does not yet do this everywhere, e.g. windows still installs the
latest.  But this is enough to see if it helps.
@flub flub requested review from Arqu and a team January 3, 2025 08:28
Copy link

github-actions bot commented Jan 3, 2025

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3088/docs/iroh/

Last updated: 2025-01-03T08:29:32Z

Copy link

github-actions bot commented Jan 3, 2025

Netsim report & logs for this PR have been generated and is available at: LOGS
This report will remain available for 3 days.

Last updated for commit: 7fe3dee

Copy link
Collaborator

@Arqu Arqu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have a link / example of the regression?

@flub
Copy link
Contributor Author

flub commented Jan 3, 2025

Do you have a link / example of the regression?

Every other flaky run in the last month results in FAILEXEC. I looked into the code of nextest and strongly suspect a regression there. If proven right it will be worth to at least report this, ideally figure out their bug (because I suspect this is not easy to reproduce).

@flub flub added this pull request to the merge queue Jan 3, 2025
Merged via the queue into main with commit 8873190 Jan 3, 2025
26 checks passed
@Arqu
Copy link
Collaborator

Arqu commented Jan 3, 2025

Ah ok, I wasn't sure which problem you were referring to. Yeah we need more info there.

@dignifiedquire dignifiedquire deleted the flub/nextest-version-pin branch January 3, 2025 11:15
@matheus23
Copy link
Member

😭 And now let's copy this PR into all other repos 🥲

@Arqu
Copy link
Collaborator

Arqu commented Jan 4, 2025

Wait are we happy with this solution, did it work?

@matheus23
Copy link
Member

Hard to know for sure. But so far this solution hasn't failed (succeeded 3 times).

flub pushed a commit to n0-computer/iroh-docs that referenced this pull request Jan 10, 2025
## Description

<!-- A summary of what this pull request achieves and a rough list of
changes. -->
Nextest seems to have some issues with file descriptors in the latest
version. This pins nextest to a 3 month old version so we get reliable
flaky test runs again.

## Breaking Changes

<!-- Optional, if there are any breaking changes document them,
including how to migrate older code. -->

## Notes & open questions

<!-- Any notes, remarks or open questions you have to make about the PR.
-->
Related PR: n0-computer/iroh#3088

## Change checklist

- [x] Self-review.
- ~~[ ] Documentation updates following the [style
guide](https://rust-lang.github.io/rfcs/1574-more-api-documentation-conventions.html#appendix-a-full-conventions-text),
if relevant.~~
- ~~[ ] Tests if relevant.~~
- ~~[ ] All breaking changes documented.~~
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants