release 7.0.0-rc1 #75
Annotations
9 errors and 11 warnings
test
Restarting after unexpected exit, crash, or test timeout in -[CR_BidManagerIntegrationTests test_givenPrefetchingBid_whenMissingBid_shouldProvideEmptyBid]; summary will include totals from previous launches.
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L1543
testLiveBid_GivenExpiredSilentBidInCache_ThenBidFromResponseGiven, XCTAssertEqual failed: ("Optional(<CR_CdbBid
|
test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
test
Process completed with exit code 1.
|
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-java@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L458
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L507
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L589
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L629
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L710
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L750
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L832
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L872
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L952
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L991
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
tests-reports-
Expired
|
7.65 KB |
|