Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: upgrade node-gyp to fix macOS build error #673

Merged
merged 1 commit into from
Mar 15, 2024

Upgrade node-gyp to fix #643 and #646

9d65ece
Select commit
Loading
Failed to load commit list.
Merged

fix: upgrade node-gyp to fix macOS build error #673

Upgrade node-gyp to fix #643 and #646
9d65ece
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Microsoft.node-pty failed Mar 15, 2024 in 4m 45s

Build #20240315.2 failed

7 errors / 0 warnings

Details

Tests

  • Failed: 0 (0.00%)
  • Passed: 172 (100.00%)
  • Other: 0 (0.00%)
  • Total: 172

Annotations

Check failure on line 143 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Microsoft.node-pty

Build log #L143 

APIScan run failed with exit code: 64

Check failure on line 149 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Microsoft.node-pty

Build log #L149 

Error running apiscan job: 1 of 1

Check failure on line 150 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Microsoft.node-pty

Build log #L150 

GuardianErrorExitCodeException: apiscan completed with an Error exit code: 64. APIScan run failed.

Check failure on line 153 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Microsoft.node-pty

Build log #L153 

Error running tool 1 of 1: apiscan
View more details on Azure Pipelines