Skip to content

vips reader now supports caching using fetch, memory profiling is nee… #34

vips reader now supports caching using fetch, memory profiling is nee…

vips reader now supports caching using fetch, memory profiling is nee… #34

Triggered via push December 10, 2023 19:59
Status Failure
Total duration 1m 21s
Artifacts

build.yaml

on: push
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

12 errors
Test (ubuntu-latest, 3.11)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (ubuntu-latest, 3.9)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (ubuntu-latest, 3.8)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (ubuntu-latest, 3.10)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (windows-latest, 3.8)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (windows-latest, 3.9)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (windows-latest, 3.11)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (windows-latest, 3.10)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (macos-latest, 3.11)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (macos-latest, 3.10)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (macos-latest, 3.9)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
Test (macos-latest, 3.8)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.