Bugs not reproducible on master


(Alex Hoppen) #1

I’m currently crawling bugs.swift.org for bugs to fix and regularly encounter bugs which I cannot reproduce on master anymore. What’s the standard protocol for them? Close them with resolution "Can’t Reproduce" or "Done" or just add a comment and let the reporter close it?

– Alex


(Daniel Dunbar) #2

I’m currently crawling bugs.swift.org for bugs to fix and regularly encounter bugs which I cannot reproduce on master anymore. What’s the standard protocol for them? Close them with resolution "Can’t Reproduce" or "Done" or just add a comment and let the reporter close it?

I suggest reporting that the bug doesn't reproduce with <insert swiftc version here>. setting the state to "Can't Reproduce" and resolved, and send back to the reporter to close it (or re-open if they think something is missed).

- Daniel

···

On Jul 13, 2016, at 6:16 AM, Alex Hoppen via swift-dev <swift-dev@swift.org> wrote:

– Alex
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev


(Robert Widmann) #3

Can't speak for everybody else, but I leave them a comment letting them know, try to find a pull request or commit that would have fixed it and close it if I can find one. Otherwise, a lot of times IBM's exhaustive catalogue of Swift releases on bluemix can usually reproduce tricky SRs.

~Robert Widmann

2016/07/13 6:16、Alex Hoppen via swift-dev <swift-dev@swift.org> のメッセージ:

···

I’m currently crawling bugs.swift.org for bugs to fix and regularly encounter bugs which I cannot reproduce on master anymore. What’s the standard protocol for them? Close them with resolution "Can’t Reproduce" or "Done" or just add a comment and let the reporter close it?

– Alex
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev