Skip to content

Fix expected output in build-std test #14353

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

Closed

Conversation

justahero
Copy link
Contributor

A recent nightly update caused one of the build-test tests (basic) to fail, due to changed output. A few CI builds failed for this reason, for example here or here.

This change updates the expected stdout output to include the missing line.

@rustbot
Copy link
Collaborator

rustbot commented Aug 5, 2024

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 5, 2024
@@ -114,6 +114,7 @@ fn basic() {
// Importantly, this should not say [UPDATING]
// There have been multiple bugs where every build triggers and update.
.with_stderr_data(str![[r#"
[UPDATING] crates.io index
Copy link
Member

Choose a reason for hiding this comment

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

Looked a few lines above

        // Importantly, this should not say [UPDATING]
        // There have been multiple bugs where every build triggers and update.

Before proceeding, we may want to figure out what has changed and if it is safe to update index.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good call

Copy link
Member

Choose a reason for hiding this comment

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

Perhaps rust-lang/rust#128534, though I may not have time looking into it today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants