Skip to content

Revert "[benchmark] Report Quantiles from Benchmark_O and a TON of Gardening" #19322

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
Sep 14, 2018

Conversation

benlangmuir
Copy link
Contributor

@benlangmuir benlangmuir merged commit a87dfb5 into master Sep 14, 2018
@palimondo
Copy link
Contributor

palimondo commented Sep 14, 2018

Oh my. I have a fix for that test, which wasn't updated to match last commit properly. What is the procedure for getting #19097 back in again with that fix?

@palimondo
Copy link
Contributor

@benlangmuir Do I revert the revert and add a commit which fixes the test?

@benlangmuir
Copy link
Contributor Author

@palimondo that would work, although it will squash all your commits into one and you'll need to update the commit message to not just say "revert: revert: ...". Alternatively you could create a new PR from the branch you used for #19097 but cherry-pick your new fix on top.

@palimondo
Copy link
Contributor

@benlangmuir I'm not sure I follow completely. What would be the best way to have a good history?
I've added the fix into that branch from #19097. Do I now rebase that on top of master and push again?

@benlangmuir
Copy link
Contributor Author

Once the branch is in the state you want, I think you just create a new PR for it.

@palimondo
Copy link
Contributor

It's showing only the fix commit and nothing else: https://github.com/apple/swift/compare/master...palimondo:fluctuation-of-the-pupil?expand=1

@benlangmuir
Copy link
Contributor Author

Ah, that's unhelpful. Maybe git is confused because your commits are already in the branch history. Maybe reverting the revert is the way to go. Sorry for leading you astray in that case. I guess we can always find the history by looking at what was merged in with the original PR.

@palimondo
Copy link
Contributor

palimondo commented Sep 14, 2018

I think I got it. I've cherrypicked all changes from that branch including the fix onto another branch forked from master. I'll redo the description from the original PR and ping you from new PR.

@shahmishal shahmishal deleted the revert-19097-fluctuation-of-the-pupil branch May 13, 2022 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants