Enabling Test Orchestrator

[ramanpreetSinghKhinda]

b/174660554

Enabling Test Orchestrator to run each of app's instrumentation tests independently without accumulating shared states.

References:

• https://firebase.google.com/docs/test-lab/android/firebase-console#new_instrumentation_tests_with_orchestrator
• http://cloud/sdk/gcloud/reference/firebase/test/android/run#--use-orchestrator

[vkryachko]

@ramanpreetSinghKhinda while you're at it, do you mind also increasing the timeout to 45m? This should help with your e2e test failures we are seeing.
for reference: https://cloud.google.com/sdk/gcloud/reference/firebase/test/android/run#--timeout

[ramanpreetSinghKhinda]

@ramanpreetSinghKhinda while you're at it, do you mind also increasing the timeout to 45m? This should help with your e2e test failures we are seeing.
for reference: https://cloud.google.com/sdk/gcloud/reference/firebase/test/android/run#--timeout

I think the current timeout is 15 min. Our tests usually finish within 9 min and the timeout in b/174660554 is not actually because our test is taking longer. It's because the android test runner is just waiting and not starting the test. If we increase the timeout it will just hold and waste resources for that timeout period.

[google-oss-bot]

Coverage Report

Affected SDKs

• firebase-database

  SDK overall coverage changed from 50.30% (00e6a8d) to 50.28% (47496a2c) by -0.02%.

  Filename	Base (00e6a8d)	Head (47496a2c)	Diff
  DoubleNode.java	100.00%	88.24%	-11.76%

• firebase-messaging

  SDK overall coverage changed from 83.43% (00e6a8d) to 83.56% (47496a2c) by +0.14%.

  Filename	Base (00e6a8d)	Head (47496a2c)	Diff
  TopicsSubscriber.java	89.66%	91.38%	+1.72%

Test Logs

• Base (00e6a8d5): https://android-ci.firebaseopensource.com/view/gcs/android-ci/logs/postsubmit-check-coverage/1334171850921480196
• Head (47496a2c): https://android-ci.firebaseopensource.com/view/gcs/android-ci/pr-logs/pull/firebase_firebase-android-sdk/2223/check-coverage-changed/1334241686435401731

Notes

HTML coverage reports can be produced locally with ./gradlew <product>:checkCoverage.
Report files are located at <product-build-dir>/reports/jacoco/.

Head commit (47496a2c) is created by Prow via merging commits: 00e6a8d b8c98fa.

[google-oss-bot]

Binary Size Report

Affected SDKs

No changes between base commit (00e6a8d) and head commit (47496a2c).

Test Logs

• Base (00e6a8d5): https://android-ci.firebaseopensource.com/view/gcs/android-ci/logs/postsubmit-binary-size/1334171850921480195
• Head (47496a2c): https://android-ci.firebaseopensource.com/view/gcs/android-ci/pr-logs/pull/firebase_firebase-android-sdk/2223/binary-size/1334241686435401732

Notes

Head commit (47496a2c) is created by Prow via merging commits: 00e6a8d b8c98fa.

[ramanpreetSinghKhinda]

I see past many runs of smoke tests are failing. Is this a known issue @yifanyang?

/test smoke-tests

[google-oss-bot]

@ramanpreetSinghKhinda: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
smoke-tests	b8c98fa	link	/test smoke-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[ramanpreetSinghKhinda]

Per discussion with @yifanyang

It's safe to merge the PR. The smoke test has been failing since last weekend and Yifan is working on it.