Intermittent UI test failure - openNewPrivateTabTest

Open
#1,923 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, kotlin
Domain
mobile, testing-qa

Research direction

Start with the openNewPrivateTabTest failure and the linked Firebase Test Run, then trace the stack through Folder.java, Launcher.java, and ModelWriter.java. Reproduce the intermittent failure and determine the relevant workspace-item mismatch; done means the test no longer fails with this launcher-loader exception.

Written by the indexing model from the issue text.

Description

eng:disabled-test eng:intermittent-test eng:ui-test
Firebase Test Run:

https://treeherder.mozilla.org/logviewer?job_id=381041516&repo=reference-browser

Stacktrace:
java.lang.RuntimeException: item: WorkspaceItemInfo(id=9 type=APP container=5 targetComponent=ComponentInfo{com.google.android.apps.maps/com.google.android.maps.MapsActivity} screen=0 cell(0,1) span(1,1) minSpan(1,1) rank=3 user=UserHandle{0} title=Maps)modelItem: WorkspaceItemInfo(id=9 type=APP container=5 targetComponent=ComponentInfo{com.google.android.apps.maps/com.google.android.maps.MapsActivity} screen=0 cell(0,1) span(1,1) minSpan(1,1) rank=3 user=UserHandle{0} title=Maps)Error: ItemInfo passed to checkItemInfo doesn't match original

       FATAL EXCEPTION: launcher-loader
Process: com.android.launcher3, PID: 1974
java.lang.RuntimeException: item: WorkspaceItemInfo(id=9 type=APP container=5 targetComponent=ComponentInfo{com.google.android.apps.maps/com.google.android.maps.MapsActivity} screen=0 cell(0,1) span(1,1) minSpan(1,1) rank=3 user=UserHandle{0} title=Maps)modelItem: WorkspaceItemInfo(id=9 type=APP container=5 targetComponent=ComponentInfo{com.google.android.apps.maps/com.google.android.maps.MapsActivity} screen=0 cell(0,1) span(1,1) minSpan(1,1) rank=3 user=UserHandle{0} title=Maps)Error: ItemInfo passed to checkItemInfo doesn't match original
	at com.android.launcher3.model.ModelWriter$UpdateItemBaseRunnable.<init>(ModelWriter.java:419)
	at com.android.launcher3.model.ModelWriter$UpdateItemsRunnable.<init>(ModelWriter.java:388)
	at com.android.launcher3.model.ModelWriter.moveItemsInDatabase(ModelWriter.java:187)
	at com.android.launcher3.folder.Folder.updateItemLocationsInDatabaseBatch(Folder.java:1000)
	at com.android.launcher3.folder.Folder.bind(Folder.java:422)
	at com.android.launcher3.folder.FolderIcon.inflateFolderAndIcon(FolderIcon.java:174)
	at com.android.launcher3.Launcher.bindItems(Launcher.java:2100)
	at com.android.launcher3.model.BaseLoaderResults$WorkspaceBinder.lambda$bindWorkspaceItems$5(BaseLoaderResults.java:241)
	at com.android.launcher3.model.-$$Lambda$BaseLoaderResults$WorkspaceBinder$u3fVFEA_dzybIfdOdmLuq72EG4o.execute(Unknown Source:6)
	at com.android.launcher3.model.BaseLoaderResults$WorkspaceBinder.lambda$executeCallbacksTask$8$BaseLoaderResults$WorkspaceBinder(BaseLoaderResults.java:267)
	at com.android.launcher3.model.-$$Lambda$BaseLoaderResults$WorkspaceBinder$DoJdszY9e4_DUwoU7ASsVyUHvxU.run(Unknown Source:4)
	at android.os.Handler.handleCallback(Handler.java:938)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:223)
	at android.app.ActivityThread.main(ActivityThread.java:7656)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Build:

https://github.com/mozilla-mobile/reference-browser/commit/c190eb23794b31c4c1f9cad04c5adf5a8357cbb5

Dominant language
Kotlin
Stars
668
Forks
198
Avg merge
8h 47m
Merged PRs (30d)
53

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla-mobile/reference-browser

All issues in mozilla-mobile/reference-browser

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.