Skip to content

Fix support for gts extensions remaining in emitted declarations #1470

Fix support for gts extensions remaining in emitted declarations

Fix support for gts extensions remaining in emitted declarations #1470

Triggered via pull request November 7, 2023 22:22
Status Failure
Total duration 27m 26s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
Test
40s
Test
Test Windows
27m 14s
Test Windows
Test Floating Dependencies
1m 54s
Test Floating Dependencies
Test TypeScript Nightly
7m 13s
Test TypeScript Nightly
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 3 warnings
Test
Process completed with exit code 1.
Test Floating Dependencies: packages/core/node_modules/@types/node/ts4.8/globals.d.ts#L2
Definitions of the following identifiers conflict with those in another file: TypedArray, ArrayBufferView, _Request, _Response, _FormData, _Headers, _RequestInit, Request, Response, Headers, FormData, RequestInit, RequestInfo, HeadersInit, BodyInit, RequestRedirect, RequestCredentials, RequestMode, ReferrerPolicy, Dispatcher, RequestDuplex
Test Floating Dependencies: packages/core/node_modules/@types/node/ts4.8/globals.d.ts#L317
Duplicate index signature for type 'string'.
Test TypeScript Nightly
The process '/usr/bin/xvfb-run' failed with exit code 1
Test Windows
Final attempt failed. Child_process exited with error code 1
Test Windows
Segmentfault Error Detected: FATAL ERROR: v8::FromJust Maybe value is Nothing.
Test Windows
Attempt 1 failed. Reason: Child_process exited with error code 1
Test Windows
Segmentfault Error Detected: FATAL ERROR: v8::FromJust Maybe value is Nothing.