Skip to content

linux glibc add user_fpsimd_struct struct #2607

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
May 28, 2022

Conversation

devnexen
Copy link
Contributor

No description provided.

@rust-highfive
Copy link

r? @Amanieu

(rust-highfive has picked a reviewer for you, use r? to override)

@Amanieu
Copy link
Member

Amanieu commented Jan 3, 2022

@bors r+

@bors
Copy link
Contributor

bors commented Jan 3, 2022

📌 Commit 14b1b93 has been approved by Amanieu

bors added a commit that referenced this pull request Jan 3, 2022
linux glibc add user_fpsimd_struct struct
@bors
Copy link
Contributor

bors commented Jan 3, 2022

⌛ Testing commit 14b1b93 with merge cca3524...

@bors
Copy link
Contributor

bors commented Jan 3, 2022

💥 Test timed out

@Amanieu
Copy link
Member

Amanieu commented Jan 3, 2022

@bors retry

@bors
Copy link
Contributor

bors commented Jan 4, 2022

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

  1. git checkout user_fpsimd_struct_arm64 (switch to your branch)
  2. git fetch upstream master (retrieve the latest master)
  3. git rebase upstream/master -p (rebase on top of it)
  4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
  5. git push self user_fpsimd_struct_arm64 --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message
Auto-merging libc-test/build.rs
CONFLICT (content): Merge conflict in libc-test/build.rs
Automatic merge failed; fix conflicts and then commit the result.

@bors
Copy link
Contributor

bors commented Jan 4, 2022

☔ The latest upstream changes (presumably #2606) made this pull request unmergeable. Please resolve the merge conflicts.

@devnexen devnexen force-pushed the user_fpsimd_struct_arm64 branch from 14b1b93 to a00785a Compare January 4, 2022 00:23
@JohnTitor
Copy link
Member

@bors r=Amanieu

@bors
Copy link
Contributor

bors commented May 28, 2022

📌 Commit a00785a has been approved by Amanieu

@bors
Copy link
Contributor

bors commented May 28, 2022

⌛ Testing commit a00785a with merge 37783e9...

bors added a commit that referenced this pull request May 28, 2022
linux glibc add user_fpsimd_struct struct
@bors
Copy link
Contributor

bors commented May 28, 2022

💔 Test failed - checks-actions

@JohnTitor
Copy link
Member

@bors retry timeout

@bors
Copy link
Contributor

bors commented May 28, 2022

⌛ Testing commit a00785a with merge 51d07d5...

@bors
Copy link
Contributor

bors commented May 28, 2022

☀️ Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 51d07d5 to master...

@bors bors merged commit 51d07d5 into rust-lang:master May 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants