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

Update Fdl Code with tests from piper #2749

Merged
merged 8 commits into from
Jun 21, 2021
Merged

Update Fdl Code with tests from piper #2749

merged 8 commits into from
Jun 21, 2021

Conversation

VinayGuthal
Copy link
Contributor

@VinayGuthal VinayGuthal commented Jun 18, 2021

Move fdl code from piper to github

FolderOrigin-RevId: /google/src/cloud/vguthal/move_stuff/.

changes

update Hide

update

update everything

update

update

update
@google-cla
Copy link

google-cla bot commented Jun 18, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

1 similar comment
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no label Jun 18, 2021
@VinayGuthal VinayGuthal added cla: yes Override cla and removed cla: no labels Jun 18, 2021
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Jun 18, 2021

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@VinayGuthal VinayGuthal changed the title Update FDL code from Piper Update Fdl Code with tests from piper Jun 18, 2021
@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 18, 2021

Coverage Report

Affected SDKs

  • firebase-dynamic-links

    SDK overall coverage changed from 72.28% (c7d8a80) to 72.58% (e267a94c) by +0.31%.

    Filename Base (c7d8a80) Head (e267a94c) Diff
    DynamicLink.java 77.72% 78.69% +0.97%
    DynamicLinksClient.java 35.71% 33.33% -2.38%
    FirebaseDynamicLinksImpl.java 96.15% 95.24% -0.92%
    FirebaseDynamicLinksImplConstants.java ? 0.00% ?

Test Logs

Notes

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

Head commit (e267a94c) is created by Prow via merging commits: c7d8a80 abf6211.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 18, 2021

Binary Size Report

Affected SDKs

  • firebase-dynamic-links

    Type Base (c7d8a80) Head (e267a94c) Diff
    aar 51.8 kB 53.1 kB +1.32 kB (+2.5%)
    apk (aggressive) 307 kB 325 kB +18.6 kB (+6.1%)
    apk (release) 936 kB 971 kB +34.7 kB (+3.7%)

Test Logs

Notes

Head commit (e267a94c) is created by Prow via merging commits: c7d8a80 abf6211.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Jun 18, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@VinayGuthal VinayGuthal added cla: yes Override cla and removed cla: no labels Jun 18, 2021
@google-cla
Copy link

google-cla bot commented Jun 18, 2021

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

1 similar comment
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@@ -70,7 +70,7 @@ public void testImplementsAllTaskInterface() {
}

for (Method method : Task.class.getDeclaredMethods()) {
// This method is annotated with @Hide, skipping.
// This method is annotated with , skipping.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is firestore part of this PR?

@@ -140,7 +139,6 @@ public String getTo() {
}

/** @hide */
@ShowFirstParty
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same for fcm, pls undo this change

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 18, 2021

Macrobenchmark Report

Affected SDKs

Measurements are for head commit (abf6211). Diffing against base commit (c7d8a80) is working in progress.

  • baseline

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait126.0 ms158.0 ms138.0 ms146.5 ms156.7 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait38.0 ms68.0 ms49.5 ms64.0 ms67.2 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait48.0 ms91.0 ms68.0 ms82.1 ms89.5 ms
  • firebase-common

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait129.0 ms168.0 ms147.0 ms162.5 ms167.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait37.0 ms81.0 ms54.5 ms62.2 ms77.8 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait57.0 ms96.0 ms75.0 ms92.1 ms95.4 ms
  • firebase-config

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait130.0 ms167.0 ms142.5 ms155.4 ms165.5 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait40.0 ms65.0 ms55.0 ms60.2 ms64.4 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait57.0 ms94.0 ms76.5 ms88.1 ms93.0 ms
  • firebase-crashlytics

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait140.0 ms191.0 ms159.5 ms171.5 ms188.1 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait41.0 ms71.0 ms52.5 ms66.1 ms70.2 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait53.0 ms88.0 ms70.5 ms84.4 ms88.0 ms
  • firebase-database

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait118.0 ms157.0 ms140.0 ms151.3 ms156.4 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait34.0 ms67.0 ms48.0 ms61.4 ms66.6 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait54.0 ms87.0 ms74.5 ms83.2 ms86.6 ms
  • firebase-dynamic-links

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait136.0 ms175.0 ms142.5 ms155.3 ms171.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait32.0 ms77.0 ms49.0 ms61.5 ms74.9 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait51.0 ms91.0 ms76.5 ms86.5 ms91.0 ms
  • firebase-firestore

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait130.0 ms166.0 ms149.0 ms164.0 ms165.6 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait31.0 ms72.0 ms51.5 ms62.6 ms71.2 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait63.0 ms100.0 ms73.0 ms88.8 ms99.2 ms
  • firebase-functions

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait125.0 ms164.0 ms140.5 ms154.7 ms163.4 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait38.0 ms66.0 ms48.5 ms58.1 ms64.7 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait62.0 ms88.0 ms72.0 ms86.0 ms87.6 ms
  • firebase-inappmessaging-display

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait161.0 ms204.0 ms180.0 ms199.4 ms203.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait35.0 ms77.0 ms52.0 ms65.4 ms75.5 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait54.0 ms89.0 ms75.0 ms86.0 ms88.4 ms
  • firebase-messaging

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait141.0 ms174.0 ms157.0 ms161.3 ms172.1 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait46.0 ms87.0 ms54.0 ms64.5 ms83.6 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait53.0 ms96.0 ms73.5 ms89.2 ms95.1 ms
  • firebase-perf

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait142.0 ms182.0 ms158.5 ms174.1 ms180.7 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait41.0 ms76.0 ms55.5 ms65.1 ms74.1 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait59.0 ms89.0 ms75.5 ms82.2 ms88.1 ms
  • firebase-storage

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait132.0 ms165.0 ms141.5 ms155.5 ms164.0 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait39.0 ms68.0 ms49.0 ms60.7 ms67.8 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait50.0 ms82.0 ms68.5 ms79.2 ms81.8 ms

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla
Copy link

google-cla bot commented Jun 21, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no and removed cla: yes Override cla labels Jun 21, 2021
Copy link
Member

@vkryachko vkryachko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but let's get a review from the fdl folks

@VinayGuthal VinayGuthal added cla: yes Override cla and removed cla: no labels Jun 21, 2021
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Jun 21, 2021

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Jun 21, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no and removed cla: yes Override cla labels Jun 21, 2021
@VinayGuthal VinayGuthal added cla: yes Override cla and removed cla: no labels Jun 21, 2021
@googlebot googlebot added cla: no and removed cla: yes Override cla labels Jun 21, 2021
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link

google-cla bot commented Jun 21, 2021

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: yes Override cla and removed cla: no labels Jun 21, 2021
@VinayGuthal VinayGuthal merged commit 91681dd into master Jun 21, 2021
@VinayGuthal VinayGuthal deleted the new_b branch June 21, 2021 17:55
@firebase firebase locked and limited conversation to collaborators Jul 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants