Closed Bug 1891455 Opened 3 months ago Closed 2 months ago

[wpt-sync] Sync PR 45711 - Bump pywebsocket3 to 4.0.2 from PyPI

Categories

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

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

Tracking

(firefox127 fixed)

Status:
RESOLVED FIXED
Milestone:
127 Branch
Tracking Flags:
Tracking Status
firefox127 --- fixed

People

(Reporter: wpt-sync, Assigned: whimboo)

References

(
URL
)

Details

(Whiteboard: [webdriver:m11][wptsync downstream])

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

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

Henrik Skupin <mail@hskupin.info> wrote:

Bump pywebsocket3 to 4.0.2 from PyPI

Follow-up from PR #45346 which we closed because pywebsocket3 is now officially available via PyPI.

This replaces all the code references for mod_pywebsocket with pywebsocket3 by updating the pywebsocket3 package to the latest release (4.0.2) as available from PyPI.

This change will also finally allow us to release a new version of wptserve to PyPI (see #35978).

Assignee: wptsync → hskupin
Status: NEW → ASSIGNED
Whiteboard: [wptsync downstream] → [webdriver:m11][wptsync downstream]
Whiteboard: [webdriver:m11][wptsync downstream] → [webdriver:m11][wptsync downstream error]
Priority: P4 → P2
Points: --- → 2
Whiteboard: [webdriver:m11][wptsync downstream error] → [webdriver:m11][wptsync downstream]
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/547a3ebd3ef2
[wpt PR 45711] - Bump pywebsocket3 to 4.0.2 from PyPI, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/547a3ebd3ef2

Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox127: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
You need to log in before you can comment on or make changes to this bug.