Skip to content

-[GTMSessionFetcherServiceTest testThreadingStress] is flaky #356

@bhamiltoncx

Description

@bhamiltoncx

I ran swift test twice at be65155.

The first time it failed:

Test Case '-[GTMSessionFetcherServiceTest testThreadingStress]' started.
gtm-session-fetcher/UnitTests/GTMSessionFetcherServiceTest.m:852: error: -[GTMSessionFetcherServiceTest testThreadingStress] : ((fetchData) != nil) failed - index 55
gtm-session-fetcher/UnitTests/GTMSessionFetcherServiceTest.m:853: error: -[GTMSessionFetcherServiceTest testThreadingStress] : ((fetchError) == nil) failed: "Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=60, NSUnderlyingError=0x600001a6e910 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_NSURLErrorNWPathKey=satisfied (Path is satisfied), interface: lo0, _kCFStreamErrorCodeKey=60, _kCFStreamErrorDomainKey=1}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <E354E876-A4E9-4A2A-93E3-74DE878D7BA3>.<25>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask <E354E876-A4E9-4A2A-93E3-74DE878D7BA3>.<25>"
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=http://localhost:59841/gettysburgaddress.txt, NSErrorFailingURLKey=http://localhost:59841/gettysburgaddress.txt, _kCFStreamErrorDomainKey=1}" - index 55
Test Case '-[GTMSessionFetcherServiceTest testThreadingStress]' failed (26.597 seconds).

The second time, it passed.

I'm guessing this test is flaky.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions