Skip to content

Update protobuf with protovalidate rules #26

Update protobuf with protovalidate rules

Update protobuf with protovalidate rules #26

Triggered via pull request July 22, 2025 08:59
Status Failure
Total duration 27s
Artifacts

main.yml

on: pull_request
Check coding standards
23s
Check coding standards
Matrix: Run tests
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 6 warnings
Run tests (Ubuntu, 3.13)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.13)
Process completed with exit code 1.
Run tests (Ubuntu, 3.10)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.10)
Process completed with exit code 1.
Run tests (Ubuntu, 3.10)
The strategy configuration was canceled because "tests.Ubuntu_3_13" failed
Run tests (Ubuntu, 3.12)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.12)
Process completed with exit code 1.
Run tests (Ubuntu, 3.12)
The strategy configuration was canceled because "tests.Ubuntu_3_13" failed
Run tests (Ubuntu, 3.11)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.11)
Process completed with exit code 1.
Run tests (Ubuntu, 3.11)
The strategy configuration was canceled because "tests.Ubuntu_3_13" failed
Run tests (Ubuntu, 3.13)
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.10)
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.12)
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.11)
Failed to restore: Cache service responded with 400
Check coding standards
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>0DVN/aAAAAADRrvrdkwXaTr/3JGSOFRzEQkwyQUEyMDMwMTA1MDA3AEVkZ2U=
Check coding standards
Failed to restore: Cache service responded with 400