New issue
Advanced search Search tips

Issue 737681 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jun 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Consider adding test for code using device::OneWriterSeqLock

Project Member Reported by juncai@chromium.org, Jun 28 2017 
Currently code that uses device::OneWriterSeqLock doesn't have test, for example:
https://cs.chromium.org/chromium/src/content/renderer/gamepad_shared_memory_reader.cc?l=81-105
https://cs.chromium.org/chromium/src/content/renderer/shared_memory_seqlock_reader.cc?l=37-58

Since the use of device::OneWriterSeqLock can be tricky, maybe it is worth to consider adding some test code when using device::OneWriterSeqLock.
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 29 2018

Status: Archived (was: Available)
This issue has been available for more than 365 days with no owner or cc list, so archiving this bug. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment