Skip to content

[google_maps_flutter] Android integration test crashing in CI: glCreateShader failed #130712

Open

Description

@stuartmorgan-g

I'm seeing flaky failures with the maps integration tests recently; example runs:

The report is:

Test run failed to complete. Instrumentation run failed due to Process crashed.
 Fatal exception
Fatal AndroidRuntime Exception detected.
     FATAL EXCEPTION: GL-Map
Process: io.flutter.plugins.googlemapsexample, PID: 23876
ers: glCreateShader failed with return value 0and GL error code 0
GL info log: 
<no info log>
Shader vert source: 
<unused source>
	at eor.b(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:3)
	at eor.a(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:1)
	at epn.<init>(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:2)
	at epo.<init>(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:1)
	at efd.e(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:17)
	at eom.run(:com.google.android.gms.policy_maps_core_dynamite@[email protected]:35)

It's possible this is a regression on the maps side rather than a plugin issue? Filing for tracking and further investigation.

Activity

  1. added
    a: tests"flutter test", flutter_test, or one of our tests
    platform-androidAndroid applications specifically
    p: mapsGoogle Maps plugin
    packageflutter/packages repository. See also p: labels.
    c: flakeTests that sometimes, but not always, incorrectly pass
    team-androidOwned by Android platform team
    fyi-ecosystemFor the attention of Ecosystem team
    on Jul 17, 2023
  2. added
    P2Important issues not at the top of the work list
    triaged-androidTriaged by Android platform team
    on Aug 24, 2023
  3. stuartmorgan-g commented on Oct 10, 2023

    @stuartmorgan-g
    ContributorAuthor

    This just happened again, on both the initial run and the re-run, so this is still a relatively common flake.

  4. ditman commented on Mar 29, 2024

    @ditman
    Member

    I've seen this again, while attempting to roll flutter-stable-packages:

    Both crashes mention the same test:

    ┌─────────┬────────────────────────┬─────────────────────┐
    │ OUTCOME │    TEST_AXIS_VALUE     │     TEST_DETAILS    │
    ├─────────┼────────────────────────┼─────────────────────┤
    │ Failed  │ panther-33-en-portrait │ Application crashed │
    └─────────┴────────────────────────┴─────────────────────┘
    Test failure for example/integration_test/latest_renderer_test.dart after 2 attempts
    

    With the same "trace" as in OP.

    (Seems to be passing in a 3rd retry)

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

    P2Important issues not at the top of the work lista: tests"flutter test", flutter_test, or one of our testsc: flakeTests that sometimes, but not always, incorrectly passp: mapsGoogle Maps pluginpackageflutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions