Closed Bug 1948150 Opened 29 days ago Closed 28 days ago

[wpt-sync] Sync PR 50702 - Bump taskcluster from 68.0.4 to 81.0.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 50702 into mozilla-central (this bug is closed when the sync is complete).

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

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

Bump taskcluster from 68.0.4 to 81.0.1 in /tools

Bumps taskcluster from 68.0.4 to 81.0.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>v81.0.1</h2>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7517">#7517</a>
Generic Worker: fixes <code>fork/exec</code> issue on headless, multiuser engine introduced in v81.0.0.</p>
<h2>v81.0.0</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Upgrades to go1.23.6 and golangci-lint 1.63.4</p>
<h3>DEPLOYERS</h3>
<p>▶ [minor] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7508">#7508</a>
Removes Cloud Armor specific policy config from deployment templates as it was applied incorrectly.</p>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [MAJOR]
Generic Worker: feature <code>runTaskAsCurrentUser</code> (note: <code>Task</code> not <code>Tasks</code>) has been added to replace the previous global task config setting <code>runTasksAsCurrentUser</code> (which is no longer supported). Worker pools can elect to enable or disable the feature with boolean config setting <code>enableRunTaskAsCurrentUser</code>. Tasks with the feature enabled (<code>task.payload.features.runTaskAsCurrentUser = true</code>) require scope <code>generic-worker:run-task-as-current-user:<provisionerID>/<workerType></code>.</p>
<p>This change was introduced in order that access to this privileged feature are guarded not only by worker config settings, but also by task scopes, and furthermore the feature must be explicitly requested, in order that tasks do not unintentionally inherit the feature by virtue of overgenerous scopes or unintentionally running on a pool with the feature enabled.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7462">#7462</a>
Generic Worker (D2G): prune docker images during garbage collection, if needed.</p>
<h3>USERS</h3>
<p>▶ [MAJOR]
The interactive feature will now drop users in the task container instead of the host</p>
<p>▶ [minor] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7506">#7506</a>
Generic Worker Chain Of Trust feature now allows tasks to inject additional
data into <code>public/chain-of-trust.json</code>. Tasks wishing to add additional fields
should write them as json to the file <code>chain-of-trust-additional-data.json</code> in
the task directory. In this initial release, there are no provisions to
customise the name or path of the file. The file contents will be merged with
the default chain of trust certificate, with the default field values taking
precedence over any provided in <code>chain-of-trust-additional-data.json</code>. If the
file is not created by the task, no merging will take place, and the feature
will operate as before.</p>
<p>▶ [minor]
Set TASK_WORKDIR environment variable for generic-worker tasks.</p>
<p>▶ [patch]
Fixed the <code>--completed</code> flag for <code>taskcluster group list</code> so it actually works instead of returning an empty list all the time</p>
<h2>v80.0.0</h2>
<!-- 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>v81.0.1</h2>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7517">#7517</a>
Generic Worker: fixes <code>fork/exec</code> issue on headless, multiuser engine introduced in v81.0.0.</p>
<h2>v81.0.0</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Upgrades to go1.23.6 and golangci-lint 1.63.4</p>
<h3>DEPLOYERS</h3>
<p>▶ [minor] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7508">#7508</a>
Removes Cloud Armor specific policy config from deployment templates as it was applied incorrectly.</p>
<h3>WORKER-DEPLOYERS</h3>
<p>▶ [MAJOR]
Generic Worker: feature <code>runTaskAsCurrentUser</code> (note: <code>Task</code> not <code>Tasks</code>) has been added to replace the previous global task config setting <code>runTasksAsCurrentUser</code> (which is no longer supported). Worker pools can elect to enable or disable the feature with boolean config setting <code>enableRunTaskAsCurrentUser</code>. Tasks with the feature enabled (<code>task.payload.features.runTaskAsCurrentUser = true</code>) require scope <code>generic-worker:run-task-as-current-user:<provisionerID>/<workerType></code>.</p>
<p>This change was introduced in order that access to this privileged feature are guarded not only by worker config settings, but also by task scopes, and furthermore the feature must be explicitly requested, in order that tasks do not unintentionally inherit the feature by virtue of overgenerous scopes or unintentionally running on a pool with the feature enabled.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7462">#7462</a>
Generic Worker (D2G): prune docker images during garbage collection, if needed.</p>
<h3>USERS</h3>
<p>▶ [MAJOR]
The interactive feature will now drop users in the task container instead of the host</p>
<p>▶ [minor] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7506">#7506</a>
Generic Worker Chain Of Trust feature now allows tasks to inject additional
data into <code>public/chain-of-trust.json</code>. Tasks wishing to add additional fields
should write them as json to the file <code>chain-of-trust-additional-data.json</code> in
the task directory. In this initial release, there are no provisions to
customise the name or path of the file. The file contents will be merged with
the default chain of trust certificate, with the default field values taking
precedence over any provided in <code>chain-of-trust-additional-data.json</code>. If the
file is not created by the task, no merging will take place, and the feature
will operate as before.</p>
<p>▶ [minor]
Set TASK_WORKDIR environment variable for generic-worker tasks.</p>
<p>▶ [patch]
Fixed the <code>--completed</code> flag for <code>taskcluster group list</code> so it actually works instead of returning an empty list all the time</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taskcluster/taskcluster/commit/e69c44b48cfa75020f193cab7ebff1d5c1c8ccf9"><code>e69c44b</code></a> v81.0.1</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/a1a4fdc680b06d5976c3b5a41f188009870af7cc"><code>a1a4fdc</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7518">#7518</a> from taskcluster/matt-boris/testingSysProcAttrStaging</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/3102be3625026509a5082b4551da5614df99cd9e"><code>3102be3</code></a> fix(generic-worker): fix <code>fork/exec</code> issue on headless, multiuser engine</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/90b697fb0ea80e869a8fc5a8708d32b936bef7de"><code>90b697f</code></a> v81.0.0</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/5732875ce31e341228efb817273a36cf4700d6b0"><code>5732875</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7505">#7505</a> from taskcluster/matt-boris/runTasksAsCurrentUserAdd...</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/583758431f99c43bf8b592d1335a1d491a6d8146"><code>5837584</code></a> Address PR comments</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/1a21be8b620053dba94ea38a6d37c46768ce783e"><code>1a21be8</code></a> Move platform data inside TaskRun struct and impl inside task feature</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/bd32c684668f3c53205e7c08ba981bc1d8797cbb"><code>bd32c68</code></a> feat(generic-worker)!: add runTaskAsCurrentUser task feature,</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/7b4da18fad5cec18a15f4e3d2b87106660cc1cb0"><code>7b4da18</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7508">#7508</a> from taskcluster/revert-7439-OPST-1758-backend-config</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/562bd1c434b6688564c198a987fc0bcccf9be0af"><code>562bd1c</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/7509">#7509</a> from Eijebong/fix-completed-flag-cli</li>
<li>Additional commits viewable in <a href="https://github.com/taskcluster/taskcluster/compare/v68.0.4...v81.0.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: 28 days ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.