Skip to content

Devicelab bots should always upload full attached device log #84000

Closed

Description

@dnfield

For example, it should start adb logcat or idevicesyslog and dump that to something in the env['FLUTTER_LOGS_DIR'].

We should be able to do this from the test harness itself. This will catch issues where we either incorrectly filter logs, or find that we're unable to make sense of the logs from a tooling perspective.

Activity

  1. added
    P1High-priority issues at the top of the work list
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    team-infraOwned by Infrastructure team
    on Jun 4, 2021
  2. self-assigned this
    on Jun 4, 2021
  3. dnfield commented on Jun 4, 2021

    @dnfield
    ContributorAuthor

    @jmagman - I'd like to make flutter log work on iPhone's without observatory/lldb. From a local experiment, it looks like idevicesyslog works with an iOS 14.4.2 phone. Do you know what's up?

    flutter logs works for me locally if I remove

    // syslog is not written on iOS 13+.
    if (_majorSdkVersion >= minimumUniversalLoggingSdkVersion) {
    return;
    }

  4. jmagman commented on Jun 4, 2021

    @jmagman
    Member

    For example, it should start adb logcat or idevicesyslog and dump that to something in the env['FLUTTER_LOGS_DIR'].

    The FLUTTER_LOGS_DIR logic is in:

    Directory get dumpDirectory {

    Currently used like:

    await inDirectory(resultBundleTemp, () {
    final String zipPath = path.join(hostAgent.dumpDirectory.path,
    'module_test_ios-objc-${DateTime.now().toLocal().toIso8601String()}.zip');

    @jmagman - I'd like to make flutter log work on iPhone's without observatory/lldb. From a local experiment, it looks like idevicesyslog works with an iOS 14.4.2 phone. Do you know what's up?

    flutter logs works for me locally if I remove

    // syslog is not written on iOS 13+.
    if (_majorSdkVersion >= minimumUniversalLoggingSdkVersion) {
    return;
    }

    It would be awesome to get flutter logs working again #44199. However, we shouldn't remove the lldb attaching/log parsing that was added to workaround the loss of those logs since it let us remove all the mDNS port discovery reliance for run and drive (see #66399 for details). Using idevicesyslog again for logs and attach would be great.

  5. dnfield commented on Jun 4, 2021

    @dnfield
    ContributorAuthor

    I'm not sure if using HostAgent is the right pattern for this, mainly because I want this to be done for all commands on CI, and optionally when doing a local run (we should't fill up dev machines with logs they can easily get themselves).

    WDYT?

  6. github-actions commented on Jul 31, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  7. locked as resolved and limited conversation to collaborators on Jul 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.c: flakeTests that sometimes, but not always, incorrectly passinfra: device doctorInfrastructure "device doctor" problemsteam-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions