Closed Bug 1832185 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 39915 - Bump taskcluster from 49.1.3 to 50.0.0 in /tools

Categories

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

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

Tracking

(firefox115 fixed)

Status:
RESOLVED FIXED
Milestone:
115 Branch
Tracking Flags:
Tracking Status
firefox115 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream error])

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

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

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

Bump taskcluster from 49.1.3 to 50.0.0 in /tools

Bumps taskcluster from 49.1.3 to 50.0.0.
<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>v50.0.0</h2>
<h3>GENERAL</h3>
<p>▶ [MAJOR] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6213">#6213</a>
The Generic Worker Docker Engine was an experimental engine that was never used
in production. It was an intended starting point for adding support for
docker-worker style payloads. However, a new approach to running Docker Worker
payloads in the multiuser engine was agreed, and is under <a href="https://github.com/orgs/taskcluster/projects/14">active
development</a>. This will
provide the same functionality that the Docker Engine was intended to provide.
Therefore the old, incomplete, and unused docker engine has been removed.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6216">#6216</a>
Build freebsd versions of livelog, taskcluster-proxy and start-worker to complement the existing generic-worker builds.</p>
<h3>USERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6208">#6208</a>
Return a malformed payload error if <code>payload.features.interactive</code> is enabled in the task definition, while the <code>enableInteractive</code> worker config is false.</p>
<h3>DEVELOPERS</h3>
<p>▶ [patch]
jsonschema2go cli now has options for generating nested structs, and including default values as struct tags.</p>
<h2>v49.2.0</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Upgrade Node.js version to 18.16.0 and go version to 1.19.9.</p>
<h3>USERS</h3>
<p>▶ [minor] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6169">#6169</a>
Adds interactive shell support to generic-worker.</p>
<p>The worker configuration variable <code>enableInteractive</code> needs to be set to <code>true</code> to allow the interactive shell feature to be enabled. <code>enableInteractive</code> is disabled by default.</p>
<p>Once the worker configuration variable is set, the <code>interactive</code> feature can be enabled on a per-task basis.</p>
<p>To enable, set <code>task.payload.features.interactive</code> to <code>true</code>. And toggle on <code>Interactive</code> in the Create Task view of the UI.</p>
</blockquote>
</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>v50.0.0</h2>
<h3>GENERAL</h3>
<p>▶ [MAJOR] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6213">#6213</a>
The Generic Worker Docker Engine was an experimental engine that was never used
in production. It was an intended starting point for adding support for
docker-worker style payloads. However, a new approach to running Docker Worker
payloads in the multiuser engine was agreed, and is under <a href="https://github.com/orgs/taskcluster/projects/14">active
development</a>. This will
provide the same functionality that the Docker Engine was intended to provide.
Therefore the old, incomplete, and unused docker engine has been removed.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6216">#6216</a>
Build freebsd versions of livelog, taskcluster-proxy and start-worker to complement the existing generic-worker builds.</p>
<h3>USERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6208">#6208</a>
Return a malformed payload error if <code>payload.features.interactive</code> is enabled in the task definition, while the <code>enableInteractive</code> worker config is false.</p>
<h3>DEVELOPERS</h3>
<p>▶ [patch]
jsonschema2go cli now has options for generating nested structs, and including default values as struct tags.</p>
<h2>v49.2.0</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Upgrade Node.js version to 18.16.0 and go version to 1.19.9.</p>
<h3>USERS</h3>
<p>▶ [minor] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6169">#6169</a>
Adds interactive shell support to generic-worker.</p>
<p>The worker configuration variable <code>enableInteractive</code> needs to be set to <code>true</code> to allow the interactive shell feature to be enabled. <code>enableInteractive</code> is disabled by default.</p>
<p>Once the worker configuration variable is set, the <code>interactive</code> feature can be enabled on a per-task basis.</p>
<p>To enable, set <code>task.payload.features.interactive</code> to <code>true</code>. And toggle on <code>Interactive</code> in the Create Task view of the UI.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taskcluster/taskcluster/commit/33960f65ddd767651226d66ec384c9b84d226648"><code>33960f6</code></a> v50.0.0</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/980b913a5e1b8bd6ab51bf3fcdc4f1d175bf3a31"><code>980b913</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6217">#6217</a> from taskcluster/freebsd-updates</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/f3c386522a6ff1ec7f9f983e6ba6b67a6f495633"><code>f3c3865</code></a> improved freebsd support</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/d1e0ff8dcde60def39bb1a6a7da118c8572cb70e"><code>d1e0ff8</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6215">#6215</a> from taskcluster/fix-dev-deployment-generic-worker-d...</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/1c271baf83ce5fb8c1e5ed441eae4b7ff5b05099"><code>1c271ba</code></a> Fix for broken staging release: <a href="https://github.com/taskcluster/staging-releas">https://github.com/taskcluster/staging-releas</a>...</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/b3f4edc1b35adebdf94642dbdb4c83270d3303db"><code>b3f4edc</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6214">#6214</a> from taskcluster/no-docker-engine</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/869de3a4327513ed26881ed0acc64988eb3bb2c2"><code>869de3a</code></a> Issue 6213: remove unused docker engine from Generic Worker</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/61418dc6586c69a5a7d5b5d8a88c042d093424ce"><code>61418dc</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6211">#6211</a> from taskcluster/fix-category</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/6cb4cececed3e7aa8088a382f7de1296fe16e890"><code>6cb4cec</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6210">#6210</a> from taskcluster/jsonschema2go-cli-options-defaults-...</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/d4424d8a8aad0da50746d5bc38a8c6a7c6ce52aa"><code>d4424d8</code></a> Add options for jsonschema2go cli for nested structs and defaults</li>
<li>Additional commits viewable in <a href="https://github.com/taskcluster/taskcluster/compare/v49.1.3...v50.0.0">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 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>

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6af5406748a7 [wpt PR 39915] - Bump taskcluster from 49.1.3 to 50.0.0 in /tools, a=testonly

https://hg.mozilla.org/mozilla-central/rev/6af5406748a7

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox115: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.