History log of /libcore/harmony-tests/src/test/java/org/apache/harmony/tests/java/nio/ByteBufferTest.java
Revision Date Author Comments
094c77bee3cb096ab3cfe7a60729037d5add2e8e 05-Jan-2017 Przemyslaw Szczepaniak <pszczepaniak@google.com> Fix ByteBuffer.put(ByteBuffer) edge case.

Replaced use of ByteBuffer.array() in ByteBuffer.put(ByteBuffer)
with a raw "hb" field access. This prevents .array() throwing a
ReadOnlyBufferException in case the buffer is a MappedByteBuffer
(only type of ByteBuffer without a backing array) and the put
argument is a non-empty, read-only HeapByteBuffer.

Test: CtsLibcoreTestCases
Bug: 34045479

_______________________________

Change-Id: I59dcfab85c4ee6bc02f1f5dad4ad2f8de43dd991
d556642d9c5ef258a0867b0101842fae10165f64 25-Nov-2015 Shubham Ajmera <shubhamajmera@google.com> DirectByteBuffer fix

The buffer was being copied in the wrong direction(it should be in the
reversed direction i.e. from current position to the end).

Also, there were different methods used for directbytebuffers and
heapbytebuffer as the previous implementation was using different
method to access the memory. The change will now allow it to use
the same set of instructions for both the buffers.

Added the corresponding unit test.

Bug: 25881506
Change-Id: If8ce299b26a78021e8c66ada35ee5ebec6ca64b1
069d99326386490f9492afd824a364c5fb645e41 21-Oct-2015 Shubham Ajmera <shubhamajmera@google.com> ByteBuffer: Removed the readonly variant

Added isReadOnly flag in HeapByteBuffer. New constructors are
added for handling isReadOnly flag along with some write
checks for put methods.

Change-Id: I468a92fdd1140db48d7c4f1442cb9ff0e6298a49
e5fea3d504609d22337a5311d3ce0e72314bceee 15-Nov-2013 Narayan Kamath <narayan@google.com> Use a consistent package path for harmony tests.

Harmony was never consistent about where they put their
tests. There's no reason we have to be the same.

Also, there's no need to have separate subtrees for nio,
nio_char etc. etc.

This change makes all existing apache harmony tests
subpackages of "org.apache.harmony.tests" and put them under
libcore/harmony-tests.

We somehow managed to end up with two vastly different
copies of CharsetDecoderTest & CharsetEncoderTest. I've
renamed the copies CharsetDecoder2Test & CharsetEncoder2Test
to avoid having to go in and resolve the complicated
diffs or speculate about the reasons for their
divergence.

Change-Id: Ic34e69c2faab8893edd54e05eccd7091f4a09abd