Closed Bug 1840737 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 40776 - Add report-lite to stash reports from PAA test for protected audience

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox117 fixed)

Status:
RESOLVED FIXED
Milestone:
117 Branch
Tracking Flags:
Tracking Status
firefox117 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 40776 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/40776
Details from upstream follow.

Tianyang Xu <xtlsheep@google.com> wrote:

Add report-lite to stash reports from PAA test for protected audience

Create a lite version report script to receive message during protected
audience test cases. It only support passing reports via parameters and
the reports are stored by uuid.

For the successful test cases, a sendReportTo() is triggered after
calling contributeToHistogram(). It will send a report of
"worklet: test description" to the report-lite server.

For the failure test cases, a sendReportTo() is triggered when an
exception is catched. The report format is same as above.

At the end of each test case, there is a observe function which will
try to get the stashed reports by the uuid to check if the reports are
sent and stashed successfully to verify contributeToHistogram() is
called with or without errors.

In the report-lite server, the GET is set with a timeout of 15 seconds.

Bug: 1456401
Change-Id: I7382203a8a8a4da14667d9e7eddeef16c89ffe73
Reviewed-on: https://chromium-review.googlesource.com/4650073
WPT-Export-Revision: f55127b10716a549d9423f68cd53ee03cdea58a0

PR 40776 applied with additional changes from upstream: ccbd015dc689928083e651f8052f2e506c16f4e1
PR 40776 applied with additional changes from upstream: 291143d928be5808818c8008d887b52e856c960e

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 7 subtests

Status Summary

Firefox

OK : 2
FAIL: 11

Chrome

OK : 2
FAIL: 11

Safari

OK : 2
FAIL: 11

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /private-aggregation/protected-audience-surface-failure.https.html [wpt.fyi]
    • contributeToHistogram() with too large bucket in scoreAd(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with negative bucket in reportResult(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with non-BigInt bucket in generateBid(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with negative value in reportWin(): FAIL (Chrome: FAIL, Safari: FAIL)
  • /private-aggregation/protected-audience-surface-success.https.html [wpt.fyi]
    • contributeToHistogram() with positive bucket in scoreAd(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with zero bucket in reportResult(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with large bucket in generateBid(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with max bucket in reportWin(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with positive value in scoreAd(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with zero value in reportResult(): FAIL (Chrome: FAIL, Safari: FAIL)
    • contributeToHistogram() with non-integer value in generateBid(): FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d27c68ba2184 [wpt PR 40776] - Allow PAA WPTs for Protected Audience to detect JavaScript errors, a=testonly https://hg.mozilla.org/integration/autoland/rev/fe42cc8d4574 [wpt PR 40776] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/d27c68ba2184
https://hg.mozilla.org/mozilla-central/rev/fe42cc8d4574

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox117: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.