Skip to content

Mac mac_unopt is flaky #185908

Open
5 of 6 issues completed
Open

Activity

  1. added
    fyi-macosFor the attention of macOS platform team
    fyi-infraFor the attention of Infrastructure team
    on May 1, 2026
  2. jmagman commented on May 1, 2026

    @jmagman
    Member

    Infra error mounting the iOS simulator runtime:
    https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8683177437043962081/+/u/install_runtimes__2_/verify_and_mount_runtime_ios-26-2_17c52/stdout

    D: 6D54DD6C-A8B6-4867-AE00-CD196B8F706A iOS (26.2 - 23C54) (Unusable - Other Failure: Error Domain=SimDiskImageErrorDomain Code=5 "Duplicate of F453DC3A-213C-448A-B827-ED9CDB77D825" UserInfo={NSLocalizedDescription=Duplicate of F453DC3A-213C-448A-B827-ED9CDB77D825, unusableErrorDetail=})
    
  3. jmagman commented on May 1, 2026

    @jmagman
    Member

    Likely many are timeouts from the Xcode 26 install cache propagating.

  4. jmagman commented on May 1, 2026

    @jmagman
    Member

    Confusingly, the actually failing test here https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/967460/infra
    is showing up as an infra failure because it's trying to run again (to deflake?) and the second run hits the 1hr timeout.

    Failure is:

    00:00 �[32m+1�[0m�[31m -1�[0m: reorder uniforms �[1m�[31m[E]�[0m�[0m
    
      ext.ui.window.reinitializeShader: (-32000) Server error
      Asset 'test_reorder_uniforms_1777667370155.frag.iplr' not found
      #0      FragmentProgram._reinitializeShader (dart:ui/painting.dart:5487:7)
      #1      _reinitializeShader (dart:ui/natives.dart:66:21)
      #2      _RootZone.runBinary (dart:async/zone.dart:967:54)
      #3      _RootZone.bindBinaryCallback.<anonymous closure> (dart:async/zone.dart:923:33)
      #4      _runExtension (dart:developer-patch/developer.dart:113:23)
    
    
      package:vm_service/src/vm_service.dart 278:34                  new _OutstandingRequest
      package:vm_service/src/vm_service.dart 1960:25                 VmService._call.<fn>
      package:vm_service/src/vm_service.dart 1972:8                  VmService._call
      package:vm_service/src/vm_service.dart 1911:14                 VmService.callServiceExtension
      flutter/testing/dart/vm_service/shader_reload_test.dart 33:53  _performReload
      ===== asynchronous gap ===========================
      flutter/testing/dart/vm_service/shader_reload_test.dart 88:7   main.<fn>
      ===== asynchronous gap ===========================
      package:test_api/src/backend/declarer.dart 253:15              Declarer.test.<fn>.<fn>
      ===== asynchronous gap ===========================
      package:test_api/src/backend/declarer.dart 250:11              Declarer.test.<fn>
      ===== asynchronous gap ===========================
      package:test_api/src/backend/invoker.dart 318:9                Invoker._waitForOutstandingCallbacks.<fn>
    

    https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8682975853707086849/+/u/test:_Host_Tests_for_host_debug_unopt_arm64/stdout

  5. saurabh-mirajkar commented on May 4, 2026

    @saurabh-mirajkar
    Contributor

    Thanks for the detailed report. Labeling and routing to team-infra for further investigation.

  6. added
    platform-macosBuilding on or for macOS specifically
    team-infraOwned by Infrastructure team
    c: flakeTests that sometimes, but not always, incorrectly pass
    and removed
    in triagePresently being triaged by the triage team
    on May 4, 2026
  7. flutter-triage-bot commented on May 4, 2026

    @flutter-triage-bot

    The fyi-infra label is redundant with the team-infra label.

  8. 7 remaining items

  9. flutter-triage-bot commented on Nov 10, 2026

    @flutter-triage-bot

    This issue is marked P1 but has had no recent status updates.

    The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

    Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work listc: flakeTests that sometimes, but not always, incorrectly passplatform-macosBuilding on or for macOS specificallyteam-engineOwned by Engine team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions