Skip to content

Added the machine's architecture to macos doctor results.#65978

Merged
fluttergithubbot merged 2 commits into
flutter:masterfrom
gaaclarke:doctor-architecture
Sep 17, 2020
Merged

Added the machine's architecture to macos doctor results.#65978
fluttergithubbot merged 2 commits into
flutter:masterfrom
gaaclarke:doctor-architecture

Conversation

@gaaclarke

Copy link
Copy Markdown
Member

Description

Now that apple supports multiple architectures I added the architecture to the flutter doctor output to help us track down bugs related to architecture.

Related Issues

#65976

Tests

none

Checklist

Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I signed the CLA.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I updated/added relevant documentation (doc comments with ///).
  • All existing and new tests are passing.
  • The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read Handling breaking changes.

@flutter-dashboard flutter-dashboard Bot added the tool Affects the "flutter" command-line tool. See also t: labels. label Sep 16, 2020
@flutter-dashboard

Copy link
Copy Markdown

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.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@jonahwilliams jonahwilliams left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change seems reasonable, tests pls

@jonahwilliams jonahwilliams left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests for this class are in https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/general.shard/base/os_test.dart

You can use the FakePlatform/FakeProcessManager to set things up to be consistent across platforms:

@jmagman jmagman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to be a bigger change, piping through a new TargetPlatform everywhere

Really, this shouldn't be hardcoded:

Future<TargetPlatform> get targetPlatform async => TargetPlatform.darwin_x64;

@jmagman

jmagman commented Sep 16, 2020

Copy link
Copy Markdown
Member

Oh I see, this isn't for a target device, it's for this output:

[✓] Flutter (Channel unknown, 1.22.0-10.0.pre.212, on Mac OS X 10.15.5 19F101, locale en-US)

@jmagman jmagman dismissed their stale review September 16, 2020 22:57

because I want to?

@jonahwilliams jonahwilliams left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Labels

tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants