Skip to content

test: remove type casts and improve type safety in test files #1610

test: remove type casts and improve type safety in test files

test: remove type casts and improve type safety in test files #1610

Triggered via pull request December 20, 2025 16:36
Status Failure
Total duration 27m 21s
Artifacts

nodejs.yml

on: pull_request
Matrix: test-windows
Matrix: test
Linting
36s
Linting
Azure SQL Server / Node.js 18.x
3m 9s
Azure SQL Server / Node.js 18.x
Azure SQL Server / Node.js 18.x
4m 3s
Azure SQL Server / Node.js 18.x
Azure SQL Server / Node.js 18.x
2m 47s
Azure SQL Server / Node.js 18.x
Azure SQL Server / Node.js 18.x
7m 2s
Azure SQL Server / Node.js 18.x
Pre-Release
Pre-Release
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 25 warnings
SQL Server Linux / Node.js 20.x
Process completed with exit code 1.
SQL Server Linux / Node.js 18.x
Process completed with exit code 1.
SQL Server Linux / Node.js 21.x
Process completed with exit code 1.
SQL Server 2017 Windows / Node.js 18.x
Process completed with exit code 1.
SQL Server 2022 Windows / Node.js 20.x
Process completed with exit code 1.
SQL Server 2016 Windows / Node.js 21.x
Process completed with exit code 1.
SQL Server 2022 Windows / Node.js 18.x
Process completed with exit code 1.
SQL Server 2022 Windows / Node.js 21.x
Process completed with exit code 1.
SQL Server 2017 Windows / Node.js 20.x
Process completed with exit code 1.
SQL Server 2016 Windows / Node.js 18.x
Process completed with exit code 1.
SQL Server 2019 Windows / Node.js 20.x
Process completed with exit code 1.
SQL Server 2017 Windows / Node.js 21.x
Process completed with exit code 1.
SQL Server 2016 Windows / Node.js 20.x
Process completed with exit code 1.
SQL Server 2019 Windows / Node.js 18.x
Process completed with exit code 1.
SQL Server 2019 Windows / Node.js 21.x
Process completed with exit code 1.
SQL Server Linux / Node.js 20.x
Failed to restore: Cache service responded with 400
Linting
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>0BNNGaQAAAACLfK+rUO/VTb4Wh2EIUk+qUEhYMzFFREdFMDYxNgBFZGdl
Linting
Failed to restore: Cache service responded with 400
Azure SQL Server / Node.js 18.x
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>0hNNGaQAAAAA3aQ8Odf1tQrAATTqHu429RE0yRURHRTA3MTUARWRnZQ==
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server Linux / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server Linux / Node.js 21.x
Failed to restore: Cache service responded with 400
Azure SQL Server / Node.js 18.x
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>0A9RGaQAAAAAJmZ1XlVQlRJX70jAYKXXGREVOMzAxMDAwMTA2MDM1AEVkZ2U=
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
Azure SQL Server / Node.js 18.x
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>0HNRGaQAAAAAiklVWyLosS43wu5NZyIRbQ0hJMzBFREdFMDMxNQBFZGdl
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
Azure SQL Server / Node.js 18.x
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>0WdRGaQAAAACvNpT5/QDsTr8aioO9LgzGUEhMMzBFREdFMDQwOABFZGdl
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server 2017 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server 2022 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
SQL Server 2016 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
SQL Server 2022 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server 2022 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
SQL Server 2017 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
SQL Server 2016 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server 2019 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
SQL Server 2017 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
SQL Server 2016 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
SQL Server 2019 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
SQL Server 2019 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400