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 issue 17340 - isNumeric!bool should not be true #5343

Merged
merged 1 commit into from Apr 27, 2017

Conversation

tsbockman
Copy link
Contributor

@JackStouffer
Copy link
Member

Regression fixes should go onto stable so they get included in the next point release.

Please use the Github UI (the button next to the PR title) to change the base branch and then manually rebase the changes onto the right commit.

@tsbockman tsbockman changed the base branch from master to stable April 22, 2017 14:59
@tsbockman
Copy link
Contributor Author

Please use the Github UI (the button next to the PR title) to change the base branch

Done...

manually rebase the changes onto the right commit.

What is "the right commit"? How do I do this?

@schveiguy
Copy link
Member

@tsbockman I generally have to look up the directions when doing this: https://wiki.dlang.org/Starting_as_a_Contributor#Stable_Branch

@schveiguy
Copy link
Member

The changes seem quite simple, maybe just checkout the stable branch and recreate it might take less time.

@dlang-bot
Copy link
Contributor

dlang-bot commented Apr 22, 2017

Fix Bugzilla Description
17340 [REG 2.074.0] isNumeric!bool should not be true

@tsbockman
Copy link
Contributor Author

tsbockman commented Apr 22, 2017

@JackStouffer @schveiguy Thanks. I think I've got the branch sorted out now.

@schveiguy
Copy link
Member

ping @wilzbach dlang bot seems to have erred here. I think when the branch was targeting stable, but included all the fixes from master, it confused the hell out of the bot and it put some unrelated bug links. But it hasn't put the correct link here (fix 17340). I'm concerned about merging this might post to wrong bug report.

Copy link
Member

@schveiguy schveiguy left a comment

Choose a reason for hiding this comment

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

LGTM

@schveiguy
Copy link
Member

Hm... auto tester I think doesn't like that the PR moved from master to stable (https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=3&pullid=5343). Something's not right. @braddr?

@JackStouffer
Copy link
Member

@schveiguy The bug report the bot says it will close is already closed, so it should be fine.

Also, I had the same issue with another PR that I switched to stable. After I added the auto merge tag and the auto tester prioritized it, it was tested eventually.

@schveiguy
Copy link
Member

@JackStouffer What's odd is that the auto tester is testing against master. And they are new runs, so it hasn't picked up that it needs to test against stable since the retargeting occurred. I don't know if it will switch automatically.

@quickfur
Copy link
Member

Autotester seems completely confused. I'm gonna try closing and reopening this PR to see if that helps. Apologies in advance if that screws things up.

@quickfur quickfur closed this Apr 27, 2017
@quickfur quickfur reopened this Apr 27, 2017
@quickfur
Copy link
Member

Auto-merge toggled on

@quickfur
Copy link
Member

OK, that seems to have kicked some sense into the autotester. Let's hope it goes through this time.

@schveiguy
Copy link
Member

hah! dlang bot edited its comment when you reopened, very slick.

@schveiguy
Copy link
Member

Removed the auto merge label since the auto tester is going to merge it.

@quickfur quickfur merged commit ef025a6 into dlang:stable Apr 27, 2017
@tsbockman
Copy link
Contributor Author

Auto-merge toggled on

Great. Thanks!

@tsbockman tsbockman deleted the is_bool_numeric branch April 27, 2017 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
5 participants