Flake: HedgedObjectReadSourceTest.HedgeOpenFailureReleasesSlot

Open
#16,413 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp, google-cloud
Domain
testing-qa

Research direction

Start with internal/hedged_object_read_source_test.cc around line 316 and run HedgedObjectReadSourceTest.HedgeOpenFailureReleasesSlot using the linked build log for comparison. Trace why the test receives UNAVAILABLE instead of OK and identify the cause of the intermittent failure. Done means the test no longer flakes and its expected result is reliable.

Written by the indexing model from the issue text.

Description

api: storage type: cleanup

https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/16412/acd756cac86341327010db887393348eaabb9831/ubuntu-22.04-cmake-oldest-deps-__default__/log-412127b2-3ff0-4b33-a2dc-363f228a0a1b.txt

Step #2 - "build.sh": [ RUN      ] HedgedObjectReadSourceTest.HedgeOpenFailureReleasesSlot
Step #2 - "build.sh": 
Step #2 - "build.sh": GMOCK WARNING:
Step #2 - "build.sh": Uninteresting mock function call - returning default value.
Step #2 - "build.sh":     Function call: Close()
Step #2 - "build.sh":           Returns: 104-byte object <E0-24 00-7C 21-7F 00-00 56-00 00-00 00-00 00-00 56-00 00-00 00-00 00-00 30-B6 DA-32 FF-7F 00-00 5E-12 97-8B 21-7F 00-00 70-E2 0C-8B 21-7F 00-00 78-E4 0C-8B 21-7F 00-00 C0-DB 0C-8B 21-7F 00-00 CD-1D 79-CA 76-55 00-00 70-E2 0C-8B 21-7F 00-00 30-E2 0C-8B 21-7F 00-00 60-E4 0C-8B 21-7F 00-00 00-F6 0C-8B 21-7F 00-00>
Step #2 - "build.sh": NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/main/docs/gmock_cook_book.md#knowing-when-to-expect-useoncall for details.
Step #2 - "build.sh": /workspace/google/cloud/storage/internal/hedged_object_read_source_test.cc:316: Failure
Step #2 - "build.sh": Value of: result
Step #2 - "build.sh": Expected: code is equal to OK and message is anything
Step #2 - "build.sh":   Actual: 304-byte object <90-78 6E-CB 76-55 00-00 00-00 00-00 00-00 00-00 A8-7E 8B-CA 76-55 00-00 28-C1 DA-32 FF-7F 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 ... 30-10 00-7C 21-7F 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00>, whose status is UNAVAILABLE: open failed, with a code that isn't equal to OK, but a message that is anything
Step #2 - "build.sh": 
Step #2 - "build.sh": [  FAILED  ] HedgedObjectReadSourceTest.HedgeOpenFailureReleasesSlot (30 ms)
Dominant language
C++
Stars
659
Forks
463
Avg merge
1d 2h
Merged PRs (30d)
89

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-cloud-cpp

All issues in googleapis/google-cloud-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.