Skip to content

Kiro CLI provider

Kiro CLI provider #18

Triggered via pull request November 18, 2025 10:05
Status Success
Total duration 27s
Artifacts

test-q-cli-provider.yml

on: pull_request
Integration Tests
0s
Integration Tests
Code Quality
23s
Code Quality
Matrix: Unit Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 8 warnings
Code Quality
Process completed with exit code 1.
Unit Tests (3.10)
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>0A0UcaQAAAACYd35ZJh6tTrm3nUf8J0JAUEhMMzBFREdFMDEyMQBFZGdl
Unit Tests (3.10)
Failed to restore: Cache service responded with 400
Unit Tests (3.12)
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>0BEUcaQAAAAD4yqeE5PjKQahvNkEjGYt/UEhMMzBFREdFMDExOQBFZGdl
Unit Tests (3.12)
Failed to restore: Cache service responded with 400
Unit Tests (3.11)
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>0BUUcaQAAAADLC9kQLymLSK2zZcbxjVF5RE0yRURHRTA5MDkARWRnZQ==
Unit Tests (3.11)
Failed to restore: Cache service responded with 400
Code Quality
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>0DEUcaQAAAAC3n1LX87kZTIxXYQ+k0ZmdUEFPRURHRTA1MTYARWRnZQ==
Code Quality
Failed to restore: Cache service responded with 400