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 23875 23880 #15172
fix Issue 23875 23880 #15172
Conversation
Thanks for your pull request, @WalterBright! Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#15172" |
b5ac24f
to
1f34cd0
Compare
Bug fixes should target stable please. |
I fixed the conflict for you @WalterBright . @ibuclaw we have been merging importC fixed in master up until now. |
Thanks! |
Why was this merged despite failing tests?
Edit: nevermind, Azure was green on this PR |
Why was it green? |
I don't know why it was green in this PR, after it was merged, it turned red: https://github.com/dlang/dmd/runs/13256496507 |
Is there memory corruption or something? Either that or it only passed
because of cache issues or something like that (some of the pipelines are
susceptible to being too clever and caching stuff incorrectly)
…On Fri, May 5, 2023 at 9:48 PM Dennis ***@***.***> wrote:
I don't know why it was green in this PR, after it was merged, it turned
red: https://github.com/dlang/dmd/runs/13256496507
—
Reply to this email directly, view it on GitHub
<#15172 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLI75FCEC5HMJMMZ3YXXODXEVRTFANCNFSM6AAAAAAXT34PTM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
No description provided.