[flutter_tools] fix null check in crash reporter#80382
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
This broke in 8ddc27e which is unfortunately in the latest RC so we'll need to cherry pick. |
|
for testing, can we add a method that always throws with |
|
I added a flag to update-packages, since that is really only a command for contributors and is already hidden. This allows us to simulate a crash with as few differences as possible between the test environment and IRL. |
|
Actual output is missing the |
|
Ahh, the oops is stdout |
|
err, maybe its a terminal versus no terminal thing |
|
g3 failure seems unrelated so I'll land on green. |
The crash reporter is currently broken, it will crash while trying to report a crash. We need a test for this. Perhaps some way to force the flutter_tool to produce a crash report?
Fixes #80383