Closed Bug 2009886 Opened 1 day ago Closed 4 hours ago

[wpt-sync] Sync PR 57140 - Bump taskcluster from 91.0.1 to 95.1.1 in /tools

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> wrote:

Bump taskcluster from 91.0.1 to 95.1.1 in /tools

Bumps taskcluster from 91.0.1 to 95.1.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/taskcluster/taskcluster/releases">taskcluster's releases</a>.</em></p>
<blockquote>
<h2>v95.1.1</h2>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [patch] <a href="http://bugzil.la/2006698">bug 2006698</a>
Fixes worker-manager killing zombie workers when queue data is missing.
For long running tasks that took longer than queueInactivityTimeout to finish was a high risk of getting claim-expired
because w-m incorrectly assumed worker is not doing anything (missing queue information)</p>
<h2>v95.1.0</h2>
<h3>USERS</h3>
<p>▶ [minor]
Queue service allows changing the priority of unresolved tasks.
Two new endpoints are being introduced:</p>
<ul>
<li>queue.changeTaskPriority</li>
<li>queue.changeTaskGroupPriority</li>
</ul>
<p>This is the implementation of the <a href="https://redirect.github.com/taskcluster/taskcluster-rfcs/pull/190">RFC190</a></p>
<h2>v95.0.3</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Notify Service: upgrades to use <code>@aws-sdk/client-sesv2</code> with the latest version of <code>nodemailer</code> to resolve some security vulnerabilities.</p>
<p>▶ [patch]
Upgrades CI Decision task to use Taskgraph v18.0.3.</p>
<p>▶ [patch]
Upgrades to Node.js v24.12.0.</p>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/8176">#8176</a>
Worker-manager ensures workers are spawned for single launch config worker pools when adjusted weight might drop below zero with remaining capacity.</p>
<p>▶ [patch]
Changed the garbage collector to clean caches after docker resources when d2g is enabled</p>
<h3>USERS</h3>
<p>▶ [patch]
Switch back web-server queues to classic, as those are only used for short-lived task group updates in the UI
and don't require same durability and Raft consensus algorithm.</p>
<h3>Automated Package Updates</h3>
<!-- raw HTML omitted -->
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md">taskcluster's changelog</a>.</em></p>
<blockquote>
<h2>v95.1.1</h2>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [patch] <a href="http://bugzil.la/2006698">bug 2006698</a>
Fixes worker-manager killing zombie workers when queue data is missing.
For long running tasks that took longer than queueInactivityTimeout to finish was a high risk of getting claim-expired
because w-m incorrectly assumed worker is not doing anything (missing queue information)</p>
<h2>v95.1.0</h2>
<h3>USERS</h3>
<p>▶ [minor]
Queue service allows changing the priority of unresolved tasks.
Two new endpoints are being introduced:</p>
<ul>
<li>queue.changeTaskPriority</li>
<li>queue.changeTaskGroupPriority</li>
</ul>
<p>This is the implementation of the <a href="https://redirect.github.com/taskcluster/taskcluster-rfcs/pull/190">RFC190</a></p>
<h2>v95.0.3</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Notify Service: upgrades to use <code>@aws-sdk/client-sesv2</code> with the latest version of <code>nodemailer</code> to resolve some security vulnerabilities.</p>
<p>▶ [patch]
Upgrades CI Decision task to use Taskgraph v18.0.3.</p>
<p>▶ [patch]
Upgrades to Node.js v24.12.0.</p>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/8176">#8176</a>
Worker-manager ensures workers are spawned for single launch config worker pools when adjusted weight might drop below zero with remaining capacity.</p>
<p>▶ [patch]
Changed the garbage collector to clean caches after docker resources when d2g is enabled</p>
<h3>USERS</h3>
<p>▶ [patch]
Switch back web-server queues to classic, as those are only used for short-lived task group updates in the UI
and don't require same durability and Raft consensus algorithm.</p>
<h3>Automated Package Updates</h3>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taskcluster/taskcluster/commit/cbb4697b6cc8bfa53bc339ae85c1e00a9e3398ef"><code>cbb4697</code></a> v95.1.1</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/b57126dcf5153fbb693ac7a06e141549ec9ae779"><code>b57126d</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/8192">#8192</a> from taskcluster/fix-error-log</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/0ef9ac634ee2d0fd0a909ecba0b806222e200b52"><code>0ef9ac6</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/8193">#8193</a> from taskcluster/feat/fix-zombie-detection-wm</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/dd7a3bc207d189a3e5da2e1a71387fd9249d35fd"><code>dd7a3bc</code></a> feat(w-m): Properly detect zombie worker using queue information</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/1fb5adfea93819bf0de17ad5d54d80652f471419"><code>1fb5adf</code></a> feat(w-m): Fix incorrectly used monitor method</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/42f6cb7a8bf569830f8dba835943723c7d8e2e7d"><code>42f6cb7</code></a> v95.1.0</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/52483d466e770c24f8a2c35bfa985e870d4cf897"><code>52483d4</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/8191">#8191</a> from taskcluster/feat/rfc190-task-priroity-change</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/8cd815c61879580c7c56af26ee57b6f8dc882361"><code>8cd815c</code></a> feat(queue): Change task and task group priority endpoints</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/a996b8269b1f67ce723d5b18b07019b210d21e99"><code>a996b82</code></a> v95.0.3</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/62dc77f1f9116a28d662c08b788575a97d75217e"><code>62dc77f</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/8177">#8177</a> from taskcluster/feat/fix-launch-configs-single-lc</li>
<li>Additional commits viewable in <a href="https://github.com/taskcluster/taskcluster/compare/v91.0.1...v95.1.1">compare view</a></li>
</ul>
</details>
<br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Status: NEW → RESOLVED
Closed: 4 hours ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.