Skip to content
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

fix: doc-test failures #12055

Merged
merged 3 commits into from
May 4, 2023
Merged

fix: doc-test failures #12055

merged 3 commits into from
May 4, 2023

Conversation

heisen-li
Copy link
Contributor

What does this PR try to resolve?

When I read the source code, I found that the Registry::new_handle document test failed and seemed to be missing parameters;

There is no change in this PR.

@rustbot
Copy link
Collaborator

rustbot commented Apr 28, 2023

r? @epage

(rustbot has picked a reviewer for you, use r? to override)

@rustbot rustbot added A-interacts-with-crates.io Area: interaction with registries S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 28, 2023
Copy link
Member

@weihanglo weihanglo left a comment

Choose a reason for hiding this comment

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

Thanks for this.

Could you also fix failing doctests for other crates in this PR? I can see at least cargo-test-support is failing as well.

@rustbot rustbot added the A-testing-cargo-itself Area: cargo's tests label May 4, 2023
@heisen-li heisen-li force-pushed the crates-io-doc-test branch from 2cda053 to 30f4b17 Compare May 4, 2023 03:13
@heisen-li heisen-li force-pushed the crates-io-doc-test branch from 30f4b17 to ea0d487 Compare May 4, 2023 03:17
@heisen-li
Copy link
Contributor Author

Thank you very much for your guidance.

I modified the documentation test case in cargo-test-support.

Other crates did not find errors.

@weihanglo weihanglo changed the title fix Registry::new_handle doc-test failed fix: doc-test failures May 4, 2023
Copy link
Member

@weihanglo weihanglo left a comment

Choose a reason for hiding this comment

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

Thanks! Only some bits of tiny issues left.

crates/cargo-test-support/src/install.rs Outdated Show resolved Hide resolved
crates/cargo-test-support/src/registry.rs Outdated Show resolved Hide resolved
@weihanglo weihanglo added S-waiting-on-author Status: The marked PR is awaiting some action (such as code changes) from the PR author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 4, 2023
@heisen-li heisen-li force-pushed the crates-io-doc-test branch from df7b432 to ff7ff7d Compare May 4, 2023 08:26
@weihanglo
Copy link
Member

Thanks!

@bors r+

@bors
Copy link
Contributor

bors commented May 4, 2023

📌 Commit ff7ff7d has been approved by weihanglo

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: The marked PR is awaiting some action (such as code changes) from the PR author. labels May 4, 2023
@bors
Copy link
Contributor

bors commented May 4, 2023

⌛ Testing commit ff7ff7d with merge 0ced62b...

bors added a commit that referenced this pull request May 4, 2023
fix:  doc-test failures

### What does this PR try to resolve?

When I read the source code, I found that the `Registry::new_handle` document test failed and seemed to be missing parameters;

There is no change in this [PR](https://github.com/rust-lang/cargo/pull/10592/files#diff-12973056cf99e8de997011a8738a6740a7dfd06142a73f122f3b35218db37351).
@bors
Copy link
Contributor

bors commented May 4, 2023

💥 Test timed out

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels May 4, 2023
@ehuss
Copy link
Contributor

ehuss commented May 4, 2023

@bors retry

macos stable builder is running extremely slow.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 4, 2023
@bors
Copy link
Contributor

bors commented May 4, 2023

⌛ Testing commit ff7ff7d with merge 33c6410...

@bors
Copy link
Contributor

bors commented May 4, 2023

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing 33c6410 to master...

@bors bors merged commit 33c6410 into rust-lang:master May 4, 2023
@heisen-li heisen-li deleted the crates-io-doc-test branch May 5, 2023 01:12
bors added a commit to rust-lang-ci/rust that referenced this pull request May 5, 2023
Update cargo

10 commits in ac84010322a31f4a581dafe26258aa4ac8dea9cd..569b648b5831ae8a515e90c80843a5287c3304ef
2023-05-02 13:41:16 +0000 to 2023-05-05 15:49:44 +0000
- xtask-unpublished: output a markdown table (rust-lang/cargo#12085)
- fix: hack around `libsysroot` instead of `libtest` (rust-lang/cargo#12088)
- Optimize usage under rustup. (rust-lang/cargo#11917)
- Update lock to normalize `home` dep (rust-lang/cargo#12084)
- fix:  doc-test failures (rust-lang/cargo#12055)
- feat(cargo-metadata): add `workspace_default_members` (rust-lang/cargo#11978)
- doc: clarify implications of `cargo-yank` (rust-lang/cargo#11862)
- chore: Use `[workspace.dependencies]` (rust-lang/cargo#12057)
- support for shallow clones and fetches with `gitoxide` (rust-lang/cargo#11840)
- Build by PackageIdSpec, not name, to avoid ambiguity (rust-lang/cargo#12015)

r? `@ghost`
@ehuss ehuss added this to the 1.71.0 milestone May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-interacts-with-crates.io Area: interaction with registries A-testing-cargo-itself Area: cargo's tests S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants