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

x/build: test whether Go core changes break external tools and debuggers #18144

Open
Sajmani opened this Issue Dec 1, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@Sajmani
Contributor

Sajmani commented Dec 1, 2016

Changes to the Go core (compiler output, libraries, x/tools) can break tools and debuggers that build on them, such as gocode (@nsf), Delve (@derekparker), and Backtrace's ptrace (@abelmathew). While those tool authors can test for breakages against tip, it might be useful for us to know when CLs submitted to the Go core break tools that are important to the Go community. We should work with the authors to ensure the tools are fixed for each new Go release.

@bradfitz suggested we may be able to extend the builders to help with this testing.

@bradfitz bradfitz changed the title from test whether Go core changes break external tools and debuggers to x/build: test whether Go core changes break external tools and debuggers Dec 1, 2016

@bradfitz bradfitz added the Builders label Dec 1, 2016

@bradfitz bradfitz added this to the Unreleased milestone Dec 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment