Skip to content

Handle gdb command failure gracefully in compiletest - #48488

Merged
bors merged 1 commit into
rust-lang:masterfrom
varkor:handle-gdb-error-compiletest
Feb 28, 2018
Merged

Handle gdb command failure gracefully in compiletest#48488
bors merged 1 commit into
rust-lang:masterfrom
varkor:handle-gdb-error-compiletest

Conversation

@varkor

Copy link
Copy Markdown
Contributor

Previously, if the gdb command was available, but threw an error, compiletest would panic. This is obviously not good. Now, gdb is treated as missing if calling gdb --version does not output anything on stdout.

Previously, if the gdb command was available, but threw an error, compiletest would panic. This is obviously not good. Now, gdb is treated as missing if calling `gdb --version` does not output anything on stdout.
@rust-highfive

Copy link
Copy Markdown
Contributor

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfiverust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 23, 2018
@michaelwoerister

Copy link
Copy Markdown
Member

Thanks, @varkor!

@bors r+

@bors

bors commented Feb 26, 2018

Copy link
Copy Markdown
Collaborator

📌 Commit 70db41c has been approved by michaelwoerister

@borsbors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 26, 2018
kennytm added a commit to kennytm/rust that referenced this pull request Feb 27, 2018
…, r=michaelwoerister
Handle gdb command failure gracefully in compiletest
Previously, if the gdb command was available, but threw an error, compiletest would panic. This is obviously not good. Now, gdb is treated as missing if calling `gdb --version` does not output anything on stdout.
@kennytmkennytm mentioned this pull request Feb 27, 2018
kennytm added a commit to kennytm/rust that referenced this pull request Feb 28, 2018
…, r=michaelwoerister
Handle gdb command failure gracefully in compiletest
Previously, if the gdb command was available, but threw an error, compiletest would panic. This is obviously not good. Now, gdb is treated as missing if calling `gdb --version` does not output anything on stdout.
@kennytmkennytm mentioned this pull request Feb 28, 2018
bors added a commit that referenced this pull request Feb 28, 2018
Rollup of 15 pull requests
- Successful merges: #48266, #48321, #48365, #48381, #48450, #48473, #48479, #48484, #48488, #48497, #48541, #48548, #48558, #48560, #48565
- Failed merges:
@bors
bors merged commit 70db41c into rust-lang:masterFeb 28, 2018
@varkor
varkor deleted the handle-gdb-error-compiletest branch February 28, 2018 14:28
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@varkor@rust-highfive@michaelwoerister@bors@aturon