test: remove type casts and improve type safety in test files (#1719) #1617
arthurschreibernodejs.yml
on: push
Matrix: test-windows
Matrix: test
Linting
35s
Azure SQL Server / Node.js 18.x
2m 30s
Azure SQL Server / Node.js 18.x
4m 46s
Azure SQL Server / Node.js 18.x
6m 25s
Azure SQL Server / Node.js 18.x
9m 8s
Pre-Release
45s
Annotations
42 warnings
|
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>0ehJHaQAAAAChIcKlDzSDRrWNU6QNFbwkQ0hJMzBFREdFMDQxMgBFZGdl
|
|
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>07hJHaQAAAADFOg300DfATYhp+vHD5gxoQ0hJMzBFREdFMDQxNQBFZGdl
|
|
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>0dRNHaQAAAACBkR2BzN5jQIfOhQPx89XPQ0hJMzBFREdFMDIxNwBFZGdl
|
|
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server Linux / Node.js 20.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>0tRNHaQAAAADOaUxi4EhMSYgc2tax75cmUEhMMzBFREdFMDQyMgBFZGdl
|
|
SQL Server Linux / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server Linux / Node.js 21.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>0uhNHaQAAAADpsoZbC6JkSo65MHP8SmdGUEhMMzBFREdFMDQxMgBFZGdl
|
|
SQL Server Linux / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server Linux / 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>0whNHaQAAAAACJ0YZreODQaA9WvKjSMpLQ0hJMzBFREdFMDIxMgBFZGdl
|
|
SQL Server Linux / 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>05BNHaQAAAAAFDwSZpQ9KTrOt/Yr5WhPKUEhYMzFFREdFMDUxNgBFZGdl
|
|
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>0ehRHaQAAAAAbewHbwxCkSqV3xaLl1Ob+UEFPRURHRTA1MTcARWRnZQ==
|
|
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2022 Windows / Node.js 20.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>0+xRHaQAAAAC7MnV6MQpVRrF0LsGJKoUrUEhYMzFFREdFMDIyMQBFZGdl
|
|
SQL Server 2022 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2022 Windows / 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>0/BRHaQAAAACyNmW1SdRcS6HVVYfrcKh/UEhMMzBFREdFMDQyMQBFZGdl
|
|
SQL Server 2022 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2016 Windows / Node.js 21.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>0HxVHaQAAAAD72Jo6y95DTpmOoMLgrqpjUEhYMzFFREdFMDUxOABFZGdl
|
|
SQL Server 2016 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2017 Windows / Node.js 21.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>0KxVHaQAAAADFY1e/GfKXTIRgQFuPhk/WUEFPRURHRTA1MTYARWRnZQ==
|
|
SQL Server 2017 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2019 Windows / Node.js 20.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>0LxVHaQAAAAABkH5HRwqJR59Rt4Ja6LzRUEFPRURHRTA1MjIARWRnZQ==
|
|
SQL Server 2019 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2019 Windows / 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>0MBVHaQAAAAAp2CC4988bQbxuh93DKt87UEhYMzFFREdFMDYyMQBFZGdl
|
|
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 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>0OxVHaQAAAADoFgXZKo3wS78EdghPulUSQ0hHRURHRTE5MDYARWRnZQ==
|
|
SQL Server 2019 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2017 Windows / 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>0QBVHaQAAAAB9oCEc2qqgQ6RuBsxCQYU7Q0hJMzBFREdFMDEyMABFZGdl
|
|
SQL Server 2017 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2017 Windows / Node.js 20.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>0RhVHaQAAAAClHXy6PJizRqrUOz1by65sQ0hJMzBFREdFMDMyMgBFZGdl
|
|
SQL Server 2017 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2016 Windows / Node.js 20.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>0UBVHaQAAAAC/Tv+McTjITZAmpp/qBBP0UEhYMzFFREdFMDYxMQBFZGdl
|
|
SQL Server 2016 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2022 Windows / Node.js 21.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>0VRVHaQAAAABsh2Om9wZ/RL8y6WMECROZQ0hHRURHRTE5MTAARWRnZQ==
|
|
SQL Server 2022 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2016 Windows / 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>0VhVHaQAAAACcv8xiPmDIRLdGZxJpDGbBQ0hHRURHRTE4MjEARWRnZQ==
|
|
SQL Server 2016 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
Pre-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>0iBVHaQAAAACO1enUiUMDQIfsIrbq4Dm+UEhMMzBFREdFMDQxMgBFZGdl
|
|
Pre-Release
Failed to restore: Cache service responded with 400
|