brimstone

[tests] Mock current time during tests #1619

Sign in to view logs

Triggered via pull request June 19, 2026 07:02

synchronize #362

mocked-unix-time

Status Success

Total duration 17m 23s

Artifacts –

ci.yml

on: pull_request

integration-tests-debug

integration-tests-release

integration-tests-gc-stress-test

integration-tests-handle-tracking

integration-tests-panic-on-oom-nightly

Annotations

27 warnings

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+uk0agAAAABnYyg/sdgJRroBbuhedmnUUEhMMzBFREdFMDQwNwBFZGdl

Failed to restore: Cache service responded with 400

cargo-tests

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

cargo-tests

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AOo0agAAAACb2t+ZKb9DR69t+aUBV0GxTEFYRURHRTE4MTcARWRnZQ==

cargo-tests

Failed to restore: Cache service responded with 400

build-fuzzer

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

build-fuzzer

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0K+o0agAAAACqUTSm4rm3RJg3vJksnVfoTEFYMzExMDAwMTExMDIxAEVkZ2U=

build-fuzzer

Failed to restore: Cache service responded with 400

integration-tests-release

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

integration-tests-release

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0R+o0agAAAADMRzFiamBLSosOmN/RrxZzUEhMMzBFREdFMDQxOABFZGdl

integration-tests-release

Failed to restore: Cache service responded with 400

integration-tests-handle-tracking

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

integration-tests-handle-tracking

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0T+o0agAAAAB5OcbbknTgT5foSxANjWtgUEhMMzBFREdFMDQxOQBFZGdl

integration-tests-handle-tracking

Failed to restore: Cache service responded with 400

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0T+o0agAAAACMyh6XBrVBS7WPD7ADd96YUEhMMzBFREdFMDQwOABFZGdl

Failed to restore: Cache service responded with 400

integration-tests-panic-on-oom-nightly

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

integration-tests-panic-on-oom-nightly

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0UOo0agAAAACI/sx+8jwlQYjuMFgWx9CAUEhMMzBFREdFMDIwOABFZGdl

integration-tests-panic-on-oom-nightly

Failed to restore: Cache service responded with 400

integration-tests-debug

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

integration-tests-debug

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+uo0agAAAAB40QXvAOd9SKHBDmXK+EYyUEhYMzFFREdFMDIxMgBFZGdl

integration-tests-debug

Failed to restore: Cache service responded with 400

integration-tests-gc-stress-test

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, Swatinem/rust-cache@82a92a6e8fbeee089604da2575dc567ae9ddeaab. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

integration-tests-gc-stress-test

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0pO00agAAAACVeeiD6bY7QbJfPSetDF0hUEhMMzBFREdFMDExMwBFZGdl

integration-tests-gc-stress-test

Failed to restore: Cache service responded with 400