Closed Bug 1858530 Opened 1 years ago Closed 1 years ago

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

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

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

Bump taskcluster from 55.3.2 to 56.0.1 in /tools

Bumps taskcluster from 55.3.2 to 56.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>v56.0.1</h2>
<h3>GENERAL</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/2940">#2940</a>
Patches 91-migration script to account for non-unique pending tasks. This was a blocking exception during migration time.</p>
<h2>v56.0.0</h2>
<h3>GENERAL</h3>
<p>▶ [MAJOR] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/2940">#2940</a>
Queue service internals refactored. <code>azure_queue_messages</code> table and <code>azqueue</code> library are no longer used.
Claim, resolved, deadline and pending queues now use separate tables. Existing messages are preserved during migration.
Database migration <code>0091</code> expects that previous <code>0090</code> migration was applied and there are no pending tasks that didn't migrate to the new format yet.
Make sure that <code>v55.3.x</code> was deployed first and data was fully migrated before deploying this version.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/2940">#2940</a>
Resolved tasks do not drop deadline messages, which was removed during queue refactoring.
Messages will stay until task deadline even if task is being resolved.</p>
<p>▶ [patch]
Upgrades to go1.21.2</p>
<h3>USERS</h3>
<p>▶ [patch]
UI: Task Definitions and Payloads now display in YAML by default for readability.</p>
<h3>Automated Package Updates</h3>
<!-- raw HTML omitted -->
<ul>
<li>build(deps): bump postcss from 8.4.21 to 8.4.31 (ec421c290)</li>
</ul>
<!-- raw HTML omitted -->
<h2>v55.3.4</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Patches an issue in github service cancelling task groups for non-push/pull-request events</p>
<h3>Automated Package Updates</h3>
<!-- raw HTML omitted -->
<ul>
<li>build(deps): bump urllib3 from 2.0.3 to 2.0.6 in /taskcluster (928877aeb)</li>
</ul>
<!-- 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>v56.0.1</h2>
<h3>GENERAL</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/2940">#2940</a>
Patches 91-migration script to account for non-unique pending tasks. This was a blocking exception during migration time.</p>
<h2>v56.0.0</h2>
<h3>GENERAL</h3>
<p>▶ [MAJOR] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/2940">#2940</a>
Queue service internals refactored. <code>azure_queue_messages</code> table and <code>azqueue</code> library are no longer used.
Claim, resolved, deadline and pending queues now use separate tables. Existing messages are preserved during migration.
Database migration <code>0091</code> expects that previous <code>0090</code> migration was applied and there are no pending tasks that didn't migrate to the new format yet.
Make sure that <code>v55.3.x</code> was deployed first and data was fully migrated before deploying this version.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/2940">#2940</a>
Resolved tasks do not drop deadline messages, which was removed during queue refactoring.
Messages will stay until task deadline even if task is being resolved.</p>
<p>▶ [patch]
Upgrades to go1.21.2</p>
<h3>USERS</h3>
<p>▶ [patch]
UI: Task Definitions and Payloads now display in YAML by default for readability.</p>
<h3>Automated Package Updates</h3>
<!-- raw HTML omitted -->
<ul>
<li>build(deps): bump postcss from 8.4.21 to 8.4.31 (ec421c290)</li>
</ul>
<!-- raw HTML omitted -->
<h2>v55.3.4</h2>
<h3>GENERAL</h3>
<p>▶ [patch]
Patches an issue in github service cancelling task groups for non-push/pull-request events</p>
<h3>Automated Package Updates</h3>
<!-- raw HTML omitted -->
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taskcluster/taskcluster/commit/e8bf310dcbf5ec5f1ae6deba9fc72f058e745061"><code>e8bf310</code></a> v56.0.1</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/932c49b7b53290950c2d0534f62ee60f0c8f7b86"><code>932c49b</code></a> feat(queue): Ensure there are no duplicate (taskId,runId) pending (<a href="https://redirect.github.com/taskcluster/taskcluster/issues/6610">#6610</a>)</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/b4a012748ffaeeb9a35f867b3dfc4dee3d8703e0"><code>b4a0127</code></a> v56.0.0</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/80a1101da9bf89dd2d20a6a520bd78ef0b18a998"><code>80a1101</code></a> feat(queue): Resolved task should not drop deadline message (<a href="https://redirect.github.com/taskcluster/taskcluster/issues/6609">#6609</a>)</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/0c427c63c852265f04aa598adc878c7936298fe9"><code>0c427c6</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6607">#6607</a> from taskcluster/matt-boris/fixConfigLinks</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/2a5e0e14e1eeb29910c1b1e43d48caaecff35632"><code>2a5e0e1</code></a> chore: update community-tc-config links [skip ci]</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/a3547fc0f49c37ab30153c92bafe3232204219ba"><code>a3547fc</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6606">#6606</a> from taskcluster/pre-commit-ci-update-config</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/78394619e47b23045f352753e672697d56ee8a5e"><code>7839461</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/ab7a2a87bb25c6b8b3a7d1f5d9819bfd6b50317d"><code>ab7a2a8</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6604">#6604</a> from taskcluster/native-copy-tool-for-explicit-logging</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/17a9dec999ffb006b737e5ea6fad8157ea080446"><code>17a9dec</code></a> Separate gzip artifact compression copying into separate parts</li>
<li>Additional commits viewable in <a href="https://github.com/taskcluster/taskcluster/compare/v55.3.2...v56.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: 1 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.