Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Ignore annotation from SnackbarHostTest (#66) #359

Closed

Conversation

MohitMandalia
Copy link
Contributor

@MohitMandalia MohitMandalia commented Jul 10, 2022

WHAT

Remove Ignore annotation from SnackbarHostTest

WHY

As the test snackbarHost_returnedResult is not failing @Ignore annotation should be removed

HOW

  • Remove @ignore annotation from snackbarHost_returnedResult() and SnackbarHostTest

Checklist 📋

  • [] Add explicit visibility modifier and explicit return types for public declarations
  • Run spotless check
  • Run tests
  • Update metalava's signature text files

@google-cla
Copy link

google-cla bot commented Jul 10, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@MohitMandalia MohitMandalia force-pushed the mohit-remove_ignore_test branch from 6b9d207 to 56b11bd Compare July 10, 2022 17:56
@MohitMandalia
Copy link
Contributor Author

@yschimke sorry I am new to metalava can you suggest me what to do here.

Thanks

@yschimke
Copy link
Collaborator

Metalava checks public API, you aren't changing any, so don't worry.

@yschimke
Copy link
Collaborator

Failing on this test


com.google.android.horologist.compose.snackbar.SnackbarHostTest > snackbarHost_returnedResult[test(AVD) - 9] FAILED 
	androidx.compose.ui.test.ComposeTimeoutException: Condition still not satisfied after 5000 ms
	at androidx.compose.ui.test.AndroidComposeUiTestEnvironment$AndroidComposeUiTestImpl.waitUntil(ComposeUiTest.android.kt:412)

28 and 30 refer to the API versions.

@MohitMandalia
Copy link
Contributor Author

Yes i'll check

@MohitMandalia
Copy link
Contributor Author

MohitMandalia commented Jul 17, 2022

I tried running the test with API 30 emulator and API 28 both runs fine in the studio but fails in github.

Any issue with the workflow file?

API 28
Screenshot 2022-07-17 at 7 13 03 PM

API 30
Screenshot 2022-07-17 at 7 20 15 PM

@yschimke
Copy link
Collaborator

Quite possibly, either the emulators are different, or maybe the config to run tests?

This build runs this

      - name: Run tests
        uses: reactivecircus/android-emulator-runner@v2
        with:
          api-level: ${{ matrix.api-level }}
          target: android-wear
          profile: wear_round_454
          script: ./scripts/run-tests.sh --log-file=logcat.txt --run-affected --affected-base-ref=$BASE_REF --shard-index=${{ matrix.shard }} --shard-count=2

From here https://github.com/google/horologist/blob/main/.github/workflows/build.yml

@MohitMandalia
Copy link
Contributor Author

MohitMandalia commented Jul 17, 2022

still exploring the issues but have found few leads this might be an issue with emulator or config as you said .

ReactiveCircus/android-emulator-runner#53

ReactiveCircus/android-emulator-runner#160

@yschimke
Copy link
Collaborator

Thanks for digging into it. If it's not coming to a solution, then I understand if you decide to leave it.

One option might be to rewrite the test using other mechanisms/code paths that might be less flaky.

@MohitMandalia
Copy link
Contributor Author

I'll try to check few details about the test and that issues I linked if i dont get a solution may be will move on with some other things. Thanks.

@yschimke
Copy link
Collaborator

@MohitMandalia Going to close this PR for now, since it's showing issues we need to fix. Please reopen if/when you pick it up again. No problem if you don't intend to either, thanks for taking a look.

@yschimke yschimke closed this Jul 25, 2022
@MohitMandalia
Copy link
Contributor Author

Yes sure i'll reopen it when I start picking up things.😊👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants