Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

DeleteAndQuitTest fails for fennecProduction build type #5406

Closed
pocmo opened this issue Sep 18, 2019 · 9 comments
Closed

DeleteAndQuitTest fails for fennecProduction build type #5406

pocmo opened this issue Sep 18, 2019 · 9 comments
Labels
eng:automation Build automation, Continuous integration, .. P2 Upcoming release wontfix

Comments

@pocmo
Copy link
Contributor

pocmo commented Sep 18, 2019

DeleteAndQuitTest is failing for the fennecProduction build type:
https://tools.taskcluster.net/groups/NUDVpqIwShOoOy05eeyNBw

SUITE: org.mozilla.fenix.utils.DeleteAndQuitTest
  TEST: delete everything and quit
    [Robolectric] org.mozilla.fenix.utils.DeleteAndQuitTest.delete everything and quit: sdk=28; resources=LEGACY
    [Robolectric] NOTICE: legacy resources mode is deprecated; see http://robolectric.org/migrating/#migrating-to-40
    I/AssetManager: no overlays.list file found
    I/MonitoringInstr: Instrumentation started!
    I/MonitoringInstr: Setting context classloader to 'org.robolectric.internal.AndroidSandbox$SdkSandboxClassLoader@136627fc', Original: 'org.robolectric.internal.AndroidSandbox$SdkSandboxClassLoader@136627fc'
  FAILURE

java.lang.AssertionError: Verification failed: call 3 of 7: Engine(#331).clearData(eq(mozilla.components.concept.engine.Engine$BrowsingData@c0), null(), eq(lambda {}), eq(lambda {}))). No matching calls found.

Calls to same method:
1) Engine(#331).clearData(mozilla.components.concept.engine.Engine$BrowsingData@6, null, lambda {}, lambda {})
2) Engine(#331).clearData(mozilla.components.concept.engine.Engine$BrowsingData@21, null, lambda {}, lambda {})
3) Engine(#331).clearData(mozilla.components.concept.engine.Engine$BrowsingData@10, null, lambda {}, lambda {})

Stack traces:

┆Issue is synchronized with this Jira Task

@pocmo
Copy link
Contributor Author

pocmo commented Sep 18, 2019

CC @ekager @NotWoods You both seem to have worked on that test.

@sblatz
Copy link
Contributor

sblatz commented Sep 18, 2019

This one seems to be an intermittent failure. I've had it pass/fail for me on my taskcluster after re-running a few times.

@pocmo
Copy link
Contributor Author

pocmo commented Sep 19, 2019

Is it really intermittent for the fennecProduction build variant though? We haven't had a nightly build of that in three days and it's starting to block our ability to test migration. :)

@ekager
Copy link
Contributor

ekager commented Sep 19, 2019

And today it's failing on
https://tools.taskcluster.net/groups/Szio0zDxTWiJ6sJIYkWULw/tasks/GxJU1i6jQvOSYdMvw73ZOA/runs/0/logs/public%2Flogs%2Flive.log


SUITE: org.mozilla.fenix.utils.DeleteAndQuitTest
  TEST: delete everything and quit
    [Robolectric] org.mozilla.fenix.utils.DeleteAndQuitTest.delete everything and quit: sdk=28; resources=LEGACY
    [Robolectric] NOTICE: legacy resources mode is deprecated; see http://robolectric.org/migrating/#migrating-to-40
    I/AssetManager: no overlays.list file found
    I/MonitoringInstr: Instrumentation started!
    I/MonitoringInstr: Setting context classloader to 'org.robolectric.internal.AndroidSandbox$SdkSandboxClassLoader@70ed0407', Original: 'org.robolectric.internal.AndroidSandbox$SdkSandboxClassLoader@70ed0407'
  FAILURE

java.lang.AssertionError: Verification failed: call 7 of 7: HomeActivity(#266).finish()) was not called.

Calls to same mock:
1) HomeActivity(#266).getApplicationContext()
2) HomeActivity(#266).getApplicationContext()
3) HomeActivity(#266).getApplicationContext()
4) HomeActivity(#266).getApplicationContext()
5) HomeActivity(#266).getApplicationContext()
6) HomeActivity(#266).getApplicationContext()
7) HomeActivity(#266).getApplicationContext()

@ekager
Copy link
Contributor

ekager commented Sep 19, 2019

Any idea why FennecProduction builds would run differently here?

@ekager
Copy link
Contributor

ekager commented Sep 19, 2019

I also can't reproduce this locally when running testGeckoBetaFennecProductionUnitTest 🤔
Can anyone see this fail locally ?

@pocmo
Copy link
Contributor Author

pocmo commented Sep 20, 2019

Just saw that taskcluster runs test instead of the test for the flavor version (@mitchhentges That's probably an optimization we should do to reduce the time this runs).

The full command taskcluster runs:
./gradlew --no-daemon -PversionName=\"Signed-as-Fennec Nightly 190919 18:00\" clean test assembleFennecProduction

I wonder if we can reproduce this with that (maybe without the clean to save some time). Since this runs the tests multiple times for different flavors, maybe that breaks because of a previous run?

@mitchhentges
Copy link
Contributor

I've created #5454 to do that optimization

@boek boek closed this as completed Dec 28, 2019
@boek boek reopened this Dec 28, 2019
@boek boek added eng:automation Build automation, Continuous integration, .. P2 Upcoming release labels Dec 28, 2019
@stale
Copy link

stale bot commented Feb 5, 2021

See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 5, 2021
@stale stale bot closed this as completed Feb 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
eng:automation Build automation, Continuous integration, .. P2 Upcoming release wontfix
Projects
None yet
Development

No branches or pull requests

5 participants