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.

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

-[GTMSessionFetcherServiceTest testThreadingStress] is flaky #356

Open
bhamiltoncx opened this issue Jul 24, 2023 · 1 comment
Open

-[GTMSessionFetcherServiceTest testThreadingStress] is flaky #356

bhamiltoncx opened this issue Jul 24, 2023 · 1 comment

Comments

@bhamiltoncx
Copy link
Member

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.

@thomasvl
Copy link
Member

thomasvl commented Feb 8, 2024

I saw this once today, but I haven't been able to repo it since. Even running the test in a loop with Xcode, no failures in 100 iterations. 😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants