Skip to content
Unit Tests

fix: added retry for connecting to a port not in use #1126

Sign in to view logs

fix: added retry for connecting to a port not in use

fix: added retry for connecting to a port not in use #1126

Triggered via pull request June 11, 2024 16:06
@jsalaberjsalaber
opened #401
retry-login-if-port-in-use
Status Success
Total duration 1m 58s
Artifacts –

tests.yml

on: pull_request
run-tests
1m 49s
run-tests
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
run-tests: src/api/apiClient.ts#L34
Unexpected any. Specify a different type
run-tests: src/api/projects.ts#L1
'IsNotEmpty' is defined but never used
run-tests: src/api/projects.ts#L1
'IsOptional' is defined but never used
run-tests: src/api/projects.ts#L1
'IsString' is defined but never used
run-tests: src/api/targeting.ts#L1
'IsOptional' is defined but never used
run-tests: src/api/targeting.ts#L1
'IsString' is defined but never used
run-tests: src/api/targeting.ts#L1
'IsArray' is defined but never used
run-tests: src/api/targeting.ts#L1
'IsNotEmpty' is defined but never used
run-tests: src/api/userProfile.ts#L1
'IsString' is defined but never used
run-tests: src/api/variations.ts#L1
'IsString' is defined but never used