Skip to content

Remove single quotes surrounding displayed venv #41

Remove single quotes surrounding displayed venv

Remove single quotes surrounding displayed venv #41

Triggered via push May 22, 2025 17:03
Status Failure
Total duration 22s
Artifacts

pr-check.yml

on: push
Matrix: Create VSIX
Matrix: Native Tests
Matrix: Python Tests
Matrix: Tests
Lint
4s
Lint
Check Python types
5s
Check Python types
Matrix: Smoke tests
Matrix: Coverage
Fit to window
Zoom out
Zoom in

Annotations

36 errors
Tests (ubuntu-latest, 3.x, functional)
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
Lint
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
Tests (ubuntu-latest, 3.x, single-workspace)
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
Create VSIX (ubuntu-latest, x86_64-unknown-linux-musl, linux-x64)
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
Python Tests (ubuntu-latest, 3.x, pytest)
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
Python Tests (ubuntu-latest, 3.9, pytest)
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
Python Tests (ubuntu-latest, 3.9, pytest==6.2.0)
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
Native Tests (ubuntu-latest)
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
Create VSIX (ubuntu-latest, x86_64-unknown-linux-musl, alpine-x64)
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
Python Tests (ubuntu-latest, 3.x, pytest==6.2.0)
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
Tests (ubuntu-latest, 3.x, ts-unit)
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
Tests (ubuntu-latest, 3.x, venv)
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
Python Tests (ubuntu-latest, 3.13, pytest==6.2.0)
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
Python Tests (ubuntu-latest, 3.13, pytest@pre-release)
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
Check Python types
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
Python Tests (ubuntu-latest, 3.13, pytest)
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
Python Tests (ubuntu-latest, 3.x, pytest@pre-release)
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
Create VSIX (windows-latest, x86_64-pc-windows-msvc, win32-x64)
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
Tests (windows-latest, 3.x, single-workspace)
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
Python Tests (ubuntu-latest, 3.9, pytest@pre-release)
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
Create VSIX (windows-latest, aarch64-pc-windows-msvc, win32-arm64)
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
Tests (windows-latest, 3.x, ts-unit)
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
Tests (ubuntu-latest, 3.x, debugger)
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
Tests (windows-latest, 3.x, debugger)
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
Python Tests (windows-latest, 3.9, pytest)
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
Tests (windows-latest, 3.x, functional)
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
Tests (windows-latest, 3.x, venv)
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
Python Tests (windows-latest, 3.x, pytest@pre-release)
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
Python Tests (windows-latest, 3.x, pytest==6.2.0)
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
Python Tests (windows-latest, 3.13, pytest@pre-release)
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
Native Tests (windows-latest)
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
Python Tests (windows-latest, 3.13, pytest)
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
Python Tests (windows-latest, 3.9, pytest==6.2.0)
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
Python Tests (windows-latest, 3.x, pytest)
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
Python Tests (windows-latest, 3.13, pytest==6.2.0)
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
Python Tests (windows-latest, 3.9, pytest@pre-release)
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