Skip to content

Dart processes not exiting in flutter/engine are hard to debug on CI #143021

@matanlurey

Description

@matanlurey

Type of Request

feature request

Infrastructure Environment

I'm not sure.

What is happening?

Example: flutter/engine@c6e7b5b.

I inherited a tool (a Dart script called android_integration_tests.dart), that has a bug where it never terminates on CI. I'm still not sure why, but figuring out that the problem was never terminating on CI (since it does terminate locally) was really hard to debug.

@keyonghan and @christopherfujino asked me to file something:

Looks like the OS info is available in the beginning: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/1936229/overview
but not collected when timing out.
Yeah, could you help file a bug to track OS info in the end?

I thought I landed a recipe change to do this (log OS info after a time out). Let me look it up, and see if I just missed some edge case.
never mind, I guess I just did that for devicelab tests: https://flutter.googlesource.com/recipes/+/24cc8a0d05ff25f461d4aac5e48cc6f726d93627%5E!/#F8

Steps to reproduce

No response

Expected results

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listteam-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions