History log of /4.6.0/forestdb/ (Results 1 - 25 of 1284)
Revision (<<< Hide revision tags) (Show revision tags >>>)Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
1d16951015-Dec-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-21953: Re-open compacted file in rollback to 0 retry

The following racy sequence causes a hang in rollback..
1. Default KV Store opened, new handle created for default kvs.
2

[BP] MB-21953: Re-open compacted file in rollback to 0 retry

The following racy sequence causes a hang in rollback..
1. Default KV Store opened, new handle created for default kvs.
2. Compaction runs and changes file to REMOVED_PENDING
3. rollback attempted with Default KV store handle still pointing to
old file.
4. rollback to zero attempts to remove kvs but finds current file
of root handle in FILE_REMOVE_PENDING state and retries operation.
During retry, new file is not re-opened but rather same file is
examined repeatedly causing a hang.
Simple fix is to check for file reopen on retry even for
rollback to zero
+Test case to reproduce the hang.

Change-Id: Id7e89873c7e283711ce1a1d411ee76e804e0dd06
Reviewed-on: http://review.couchbase.org/70977
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Well-Formed: buildbot <build@couchbase.com>
Tested-by: Sundararaman Sridharan <sundar@couchbase.com>

show more ...

0c08400513-Dec-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP]: MB-21953: Reset file state on compaction failure

If compaction fails on last phase, then file state can remain
in FILE_COMPACT_OLD. This can cause rollback to infinitely
loop,

[BP]: MB-21953: Reset file state on compaction failure

If compaction fails on last phase, then file state can remain
in FILE_COMPACT_OLD. This can cause rollback to infinitely
loop, resulting in hang.
Add fdb_anomaly_test that exactly reproduces this hang.

Change-Id: I6f3388553e6508a2846ce0900e341f93777401b3
Reviewed-on: http://review.couchbase.org/70889
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Well-Formed: buildbot <build@couchbase.com>
Tested-by: Sundararaman Sridharan <sundar@couchbase.com>

show more ...

6d8127fc26-Sep-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-21045: Reclaim stale blocks for non-snapshot handles

Non-snapshot handles which are not actively being used
for any forestdb api calls but are still lingering around
prevents

[BP] MB-21045: Reclaim stale blocks for non-snapshot handles

Non-snapshot handles which are not actively being used
for any forestdb api calls but are still lingering around
prevents their headers being reclaimed for stale block reuse.
Circular block re-use must only consider active snapshot
(and iterator) handles since these are the only types which
do not refresh upon their next forestdb call.
+ Basic stale block functionality verification test.

Change-Id: I1074a32fb3c83fe38ee59500f71d512d599b2a66
Reviewed-on: http://review.couchbase.org/67988
Tested-by: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Reviewed-on: http://review.couchbase.org/68639
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

ef4619e921-Sep-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20091: Don't return root handle on fdb_kvs_open_default

root handle is used internally for commit and must never be
returned by fdb_kvs_open_default() or fdb_rollback()
Other

[BP] MB-20091: Don't return root handle on fdb_kvs_open_default

root handle is used internally for commit and must never be
returned by fdb_kvs_open_default() or fdb_rollback()
Otherwise a reader and writer sharing same file handle
can end up sharing the same KVS Handle and hitting HANDLE_BUSY
Test case: 1 reader 1 writer share file handle,
but different default kvs handles

Change-Id: If376b0c4d94b97d0f504024f5ce3fe3e6cf31d0b
Reviewed-on: http://review.couchbase.org/67901
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

5b78091c20-Sep-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20091: ThreadSanitizer race in handle->last_hdr_bid

WARNING: ThreadSanitizer: data race (pid=29250)
Write of size 8 at 0x7d4c00117c18 by thread T33:
#0 fdb_sync_db_header fo

[BP] MB-20091: ThreadSanitizer race in handle->last_hdr_bid

WARNING: ThreadSanitizer: data race (pid=29250)
Write of size 8 at 0x7d4c00117c18 by thread T33:
#0 fdb_sync_db_header forestdb.cc:1071
#1 FdbEngine::get(FdbKvsHandle*, fdb_doc_struct*, bool) forestdb.cc:2939
#2 fdb_get forestdb.cc:1246
#3 FdbEngine::getKeyValue() api_wrapper.cc:120
#4 fdb_get_kv api_wrapper.cc:51 #5 multi_thread_fhandle_share(void*)
fdb_functional_test.cc:2288

Previous read of size 8 at 0x7d4c00117c18 by thread T34 (mutexes:
write M66515, write M66518, write M66402):
#0 FdbFileHandle::getOldestActiveHeader() file_handle.cc:282
#1 fdb_get_smallest_active_header kv_instance.cc:1215
#2 Superblock::reclaimReusableBlocks(FdbKvsHandle*) superblock.cc:1286
#3 FdbEngine::commitWithKVHandle(FdbKvsHandle*, unsigned char,
bool) forestdb.cc:3786
#4 fdb_commit forestdb.cc:3587
#5 multi_thread_fhandle_share(void*) fdb_functional_test.cc:2272

Change-Id: Ifcf1168bf770294b1df1c729211404b4d5af4a56
Reviewed-on: http://review.couchbase.org/67847
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

c3456ce220-Sep-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20091: ThreadSanitizer Race in superblock bmp_revnum

WARNING: ThreadSanitizer: data race (pid=29250)
Write of size 8 at 0x7d380000df40 by thread T34 (mutexes:
write M66515,

[BP] MB-20091: ThreadSanitizer Race in superblock bmp_revnum

WARNING: ThreadSanitizer: data race (pid=29250)
Write of size 8 at 0x7d380000df40 by thread T34 (mutexes:
write M66515, write M66522):
#0 Superblock::reclaimReusableBlocks(FdbKvsHandle*) superblock.cc:1323
#1 FdbEngine::commitWithKVHandle(FdbKvsHandle*, unsigned char, bool) forestdb.cc:3786
#2 fdb_commit forestdb.cc:3587
#3 multi_thread_fhandle_share(void*)
(fdb_functional_test+0x0000004d6b56)

Previous read of size 8 at 0x7d380000df40 by thread T33:
#0 FileMgr::getSbBmpRevnum() superblock.h:209
#1 DocioHandle::_readThroughBuffer_Docio(unsigned long, bool) docio.cc:717
#2 DocioHandle::_readLength_Docio(unsigned long,
docio_length*, bool) docio.cc:810
#3 DocioHandle::validateChecksum_Docio(bool, long*,
docio_length*, fdb_status*) docio.cc:993
#4 DocioHandle::readDoc_Docio(unsigned long, docio_object*,
bool) docio.cc:1227
#5 FdbEngine::get(FdbKvsHandle*, fdb_doc_struct*, bool)
forestdb.cc:2987
#6 fdb_get forestdb.cc:1246

Change-Id: Ia913b262a3f4c5bcf35d5c2aa1be59ddf3a92af5
Reviewed-on: http://review.couchbase.org/67846
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Well-Formed: buildbot <build@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

e6c5505316-Sep-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP]:MB-20755: Avoid array index-out-of-bounds in compact_move_docs

Change-Id: Ia76494dd985683081ec91ed8b7b4cf96421e6289
Reviewed-on: http://review.couchbase.org/67530
Well-Formed: b

[BP]:MB-20755: Avoid array index-out-of-bounds in compact_move_docs

Change-Id: Ia76494dd985683081ec91ed8b7b4cf96421e6289
Reviewed-on: http://review.couchbase.org/67530
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Sundararaman Sridharan <sundar@couchbase.com>
Tested-by: Sundararaman Sridharan <sundar@couchbase.com>

show more ...

0d24efb912-Aug-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20499: Distinguish seek_to_min/max from regular seek

SET : a b1 b2 b3 c
ITERATOR: [b - c] skip max key
SEEK : c (expected ITR_FAIL, returned result b3)
Reason sinc

[BP] MB-20499: Distinguish seek_to_min/max from regular seek

SET : a b1 b2 b3 c
ITERATOR: [b - c] skip max key
SEEK : c (expected ITR_FAIL, returned result b3)
Reason since seek was overloaded by seek_to_max and seek_to_min
b3 was returned even in regular seek()

Change-Id: I0b98c92ca6494637400e6d3c835741f07ac5eeb4
Reviewed-on: http://review.couchbase.org/66748
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Well-Formed: buildbot <build@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

b10aec3303-Aug-2016 abhinavdangeti <abhinav@couchbase.com>

[BP] MB-20040: Acquire last_hdr_bid before move_docs phase of compaction

+ Acquire the last_hdr_bid value before invoking fdb_compact_move_docs
during fdb_compact_file, to avoid fdb_co

[BP] MB-20040: Acquire last_hdr_bid before move_docs phase of compaction

+ Acquire the last_hdr_bid value before invoking fdb_compact_move_docs
during fdb_compact_file, to avoid fdb_compact_move_docs (which
invokes fdb_get_file_info, and there by fdb_sync_db_header) from
shifting the last_hdr_bid, causing delta compaction to fail to move
some of the documents to the new file.
+ Fix mvcc_functional_test: snapshot_concurrent_compaction_test to
complete in a finite amount of time. This test sets a compaction
callback that writes items as part of the callback, meaning
fdb_compact_move_delta which invokes the compaction_callback fn,
will always find delta docs to move on every iteration.

(Reviewed on: http://review.couchbase.org/#/c/66459/)

Change-Id: I0af184c296d922a0afadc426ecb31c75b18cdf97
Reviewed-on: http://review.couchbase.org/66472
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

fee2123926-Jul-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20284:Auto commit on close iff file had new data

If there was no data written calling fdb_commit unncessarily
causes file size to grow when auto_commit option is enabled.

[BP] MB-20284:Auto commit on close iff file had new data

If there was no data written calling fdb_commit unncessarily
causes file size to grow when auto_commit option is enabled.

Change-Id: I7fa98f4bf082874b7b8a024e9d65b0a56d2a55b8
Reviewed-on: http://review.couchbase.org/66241
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

7e4d980618-Jul-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20112: Only let first open restore wal

When multiple threads call fdb_open() we can have multiple
attempts at _fdb_restore_wal() which can insert items into
the WAL even thou

[BP] MB-20112: Only let first open restore wal

When multiple threads call fdb_open() we can have multiple
attempts at _fdb_restore_wal() which can insert items into
the WAL even though they have been reflected in main index
Ignore those WAL items who offset matches with one in trie
Test case where sequence iterator out of sync with key iterator
This change also prevents many DB headers from polluting the
buffercache, thereby reducing buffercache usage.
(Reviewed-on: http://review.couchbase.org/65906)

Change-Id: Ife1cdc592118f7942314892902db429a15fdc37f
Reviewed-on: http://review.couchbase.org/66045
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

88f49f7321-Jul-2016 abhinavdangeti <abhinav@couchbase.com>

[BP] MB-20219: Stick to heap allocation just for windows

- Move raw key allocation from heap to stack for any
non-windows platform.

- Originally this allocation was always made

[BP] MB-20219: Stick to heap allocation just for windows

- Move raw key allocation from heap to stack for any
non-windows platform.

- Originally this allocation was always made on the
stack, but was moved to the heap because of stack
overflow issues seen during testing just on the
windows platform (MB-19744).
- However the heap allocation has introduced a
performance regression because of all the malloc/free
overhead.
- So, until a good solution (like maintaining and
reusing a simple global buffer pool rather than
allocating space for every hbtrie::find/insert
operation) is implemented, the heap allocation will
be made only for windows.

(Reviewed on: http://review.couchbase.org/#/c/66027/)

Change-Id: I5cde1b90074e398e13103b38c6f00a01c66c2bdf
Reviewed-on: http://review.couchbase.org/66029
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: abhinav dangeti <abhinav@couchbase.com>

show more ...

7f95330420-Jul-2016 abhinavdangeti <abhinav@couchbase.com>

[BP] MB-20196: Validate iterator seek range for deleted keys

(Reviewed on: http://review.couchbase.org/#/c/65974/)

Change-Id: I35affa14cffffa1d78aa80bfcb503c952b7f0366
Reviewed-

[BP] MB-20196: Validate iterator seek range for deleted keys

(Reviewed on: http://review.couchbase.org/#/c/65974/)

Change-Id: I35affa14cffffa1d78aa80bfcb503c952b7f0366
Reviewed-on: http://review.couchbase.org/65978
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

3f1b12bb19-Jul-2016 Jung-Sang Ahn <jungsang.ahn@gmail.com>

MB-20111 Reset 'lastbid' if BMP revnum has been changed

- If superblock's BMP revnum has been changed, 'lastbid' block might
be reused so that we should reset it.

Change-Id: I70

MB-20111 Reset 'lastbid' if BMP revnum has been changed

- If superblock's BMP revnum has been changed, 'lastbid' block might
be reused so that we should reset it.

Change-Id: I709f162225c836a5fa3109bb54912efe1630d198
Reviewed-on: http://review.couchbase.org/65948
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

709b3fd615-Jul-2016 Jung-Sang Ahn <jungsang.ahn@gmail.com>

[BP] MB-20112 Disable log callback during compaction recovery

- As partially compacted file is not a normal file, various kinds of
errors can happen, but they don't need to be reported.

[BP] MB-20112 Disable log callback during compaction recovery

- As partially compacted file is not a normal file, various kinds of
errors can happen, but they don't need to be reported.

Change-Id: I4b04b75b004b1c36fe9dc912d0ddb463c2fa1bf1
Reviewed-on: http://review.couchbase.org/65834
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: abhinav dangeti <abhinav@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

5f874bbf09-Jul-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

[BP] MB-20076: use txn_id instead of pointer for comparisons

The following sequence can cause an item of an committed transaction
to be falsely detected as belonging to an active transac

[BP] MB-20076: use txn_id instead of pointer for comparisons

The following sequence can cause an item of an committed transaction
to be falsely detected as belonging to an active transaction
1. transactionA created at memory address P1
2. Key k1 inserted into transactionA, k1 points to P1 to remember it
3. transactionA commits, k1 still points to P1
4. transactionA memory address P1 is freed
5. transaction B begins and is given same address P1
6. snapshot created & begins to copy all WAL items
7. snapshot skips over key k1 because it finds address P1 belongs to an
open transaction

Change-Id: Ie7eff23ece49ac537b5410194723b7c269093f0d
Reviewed-on: http://review.couchbase.org/65651
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

93e1be8521-Jun-2016 Trond Norbye <trond.norbye@gmail.com>

MB-19390: Use jemalloc on windows

Change-Id: I39df6ec9597f45d5a69533e0d2ccb28ef57183da
Reviewed-on: http://review.couchbase.org/65103
Well-Formed: buildbot <build@couchbase.com>

MB-19390: Use jemalloc on windows

Change-Id: I39df6ec9597f45d5a69533e0d2ccb28ef57183da
Reviewed-on: http://review.couchbase.org/65103
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Will Gardner <will.gardner@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

d632be9715-Jun-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

MB-19941: Validate iterator range for end/start key

Test Case: Insert: keys doc-01 to doc-99
iterator (startkey=doc-24, endkey=doc-29b) endkey does not exist
seek_to_max should retur

MB-19941: Validate iterator range for end/start key

Test Case: Insert: keys doc-01 to doc-99
iterator (startkey=doc-24, endkey=doc-29b) endkey does not exist
seek_to_max should return doc-29 but returns doc-30
seek_to_min with doc-24b should return doc-25 but returns doc-24
due to missing range validation

Change-Id: I14302306f55bf0dafe0860c503e04bbda8493c12
Reviewed-on: http://review.couchbase.org/64966
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

42913b8613-Jun-2016 abhinavdangeti <abhinav@couchbase.com>

MB-19743: Fix cleanup in in_memory_snapshot_cleanup_test

+ Ensure that docs are deleted in a clean manner within
the test to avoid any heap corruption within the test.
+ Remove unu

MB-19743: Fix cleanup in in_memory_snapshot_cleanup_test

+ Ensure that docs are deleted in a clean manner within
the test to avoid any heap corruption within the test.
+ Remove unused values within the test case.
+ Reduce unnecessary stack usage.

Change-Id: I590f34a33cb912ba82fe42b7bd987c676ac05be2
Reviewed-on: http://review.couchbase.org/64434
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

dcd5953525-May-2016 abhinavdangeti <abhinav@couchbase.com>

MB-19744: Move allocation of fdb_docs on to heap

To avoid stack exhaustion, move allocation of the
list of fdb_docs on to the heap.

Change-Id: Ie131a53a13757480631dbb893db81ded4

MB-19744: Move allocation of fdb_docs on to heap

To avoid stack exhaustion, move allocation of the
list of fdb_docs on to the heap.

Change-Id: Ie131a53a13757480631dbb893db81ded472a2f3b
Reviewed-on: http://review.couchbase.org/64428
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

7af74b2125-May-2016 abhinavdangeti <abhinav@couchbase.com>

MB-19744: Reduce stack allocations in hbtrie_insert path

Use heap to allocate memory instead.

Change-Id: I014ff2d8a5444effbff884a00f580c6c10625521
Reviewed-on: http://review.cou

MB-19744: Reduce stack allocations in hbtrie_insert path

Use heap to allocate memory instead.

Change-Id: I014ff2d8a5444effbff884a00f580c6c10625521
Reviewed-on: http://review.couchbase.org/64419
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

b9e5d3c209-Jun-2016 Jung-Sang Ahn <jungsang.ahn@gmail.com>

MB-19845 Update root handle on fdb_kvs_create or fdb_kvs_remove

- At the end of fdb_kvs_create() or fdb_kvs_remove(), a new commit
header is appended, but root handle's 'last_hdr_bid' is

MB-19845 Update root handle on fdb_kvs_create or fdb_kvs_remove

- At the end of fdb_kvs_create() or fdb_kvs_remove(), a new commit
header is appended, but root handle's 'last_hdr_bid' is not updated
correctly.

- If file is closed without commit, then superblock is still pointing
to the previous commit header, as a result KVS creation or removal
will be ignored.

- To address this issue, update root handle's 'last_hdr_bid' properly.

Change-Id: Ida71139ed91373e0b4a84b3f61b86d27ab58b822
Reviewed-on: http://review.couchbase.org/64849
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

1026552026-May-2016 abhinavdangeti <abhinav@couchbase.com>

MB-19745: Handle windows scenario for reading a block at EOF

- When Linux's pread is run at an offset for a block
starting at the end of file, pread succeeds and returns 0.
- With

MB-19745: Handle windows scenario for reading a block at EOF

- When Linux's pread is run at an offset for a block
starting at the end of file, pread succeeds and returns 0.
- With Windows however, on the exact same scenario, ReadFile
fails, and sets errno to ENOENT. ENOENT is mapped to
FDB_RESULT_NO_SUCH_FILE, which is a case that isn't
handled when attempting to read a header block.
- Fixing this issue by handling the case when reading of a
block at EOF is attempted.
- Also do not use _F64 to print a uint32_t value, as on
windows, faulty numbers are seen in logs.

Change-Id: Ifb0718feb9afab489d1d7f1299c9d03a2620eabf
Reviewed-on: http://review.couchbase.org/64506
Reviewed-by: Sundararaman Sridharan <sundar@couchbase.com>
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Reviewed-by: Jung-Sang Ahn <jungsang.ahn@gmail.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

05d8ab7d08-Jun-2016 Sundar Sridharan <sundar.sridharan@gmail.com>

MB-19830: Ignore WRITE_FAIL for parallel fdb_open()+fdb_kvs_open()

fdb_kvs_open() issues commit to persist kv store name. This can
interfere with fdb_open()'s functions like btreeblk_end

MB-19830: Ignore WRITE_FAIL for parallel fdb_open()+fdb_kvs_open()

fdb_kvs_open() issues commit to persist kv store name. This can
interfere with fdb_open()'s functions like btreeblk_end() since
some blocks are now immutable due to the commit from other thread.

Change-Id: Id09673f89ef937095dbbc935cd37a1ed9e13deb6
Reviewed-on: http://review.couchbase.org/64807
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

c81e41fe25-May-2016 abhinavdangeti <abhinav@couchbase.com>

MB-19741: Set winoffs's offset and offsetHigh correctly

In the test case: invalid_get_byoffset_test(), within
scenario 4, set the new offset for a file read operation
correctly for w

MB-19741: Set winoffs's offset and offsetHigh correctly

In the test case: invalid_get_byoffset_test(), within
scenario 4, set the new offset for a file read operation
correctly for windows.

Change-Id: I0bfcd12f28308c42c558d726e6d95451b52b83eb
Reviewed-on: http://review.couchbase.org/64432
Well-Formed: buildbot <build@couchbase.com>
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Chiyoung Seo <chiyoung@couchbase.com>

show more ...

12345678910>>...52