Skip to content
PR Validation

Add variable presentation #437

Sign in to view logs

Add variable presentation

Add variable presentation #437

Triggered via pull request August 6, 2024 21:13
@paulacamargo25paulacamargo25
opened #433
paulacamargo25:Add-VariablePresentation
Status Failure
Total duration 3m 9s
Artifacts 1

pr-check.yml

on: pull_request
Create VSIX
48s
Create VSIX
Lint
22s
Lint
Matrix: Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 20 warnings
Lint
Process completed with exit code 1.
Lint: src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Lint: src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Create VSIX
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Tests (ubuntu-latest, 3.8): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.8): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.9): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.9): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.10): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.10): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.11): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (ubuntu-latest, 3.11): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (windows-latest, 3.8): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (windows-latest, 3.8): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (windows-latest, 3.11): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (windows-latest, 3.11): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (windows-latest, 3.10): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (windows-latest, 3.10): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Tests (windows-latest, 3.9): src/extension/debugger/configuration/resolvers/attach.ts#L53
Expected '===' and instead saw '=='
Tests (windows-latest, 3.9): src/extension/debugger/configuration/resolvers/launch.ts#L117
Expected '===' and instead saw '=='
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "linter-package". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
linter-package Expired
6.15 MB