[ 
https://issues.apache.org/jira/browse/IGNITE-10192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688098#comment-16688098
 ] 

ASF GitHub Bot commented on IGNITE-10192:
-----------------------------------------

GitHub user ibessonov opened a pull request:

    https://github.com/apache/ignite/pull/5400

    IGNITE-10192 OptimizedMarshallerTest#testAllocationOverflow throws OOME 
instead of expected IOE

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-10192

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5400.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5400
    
----
commit 1a45b39e522574721710d938472a3e454cd79611
Author: ibessonov <bessonov.ip@...>
Date:   2018-11-15T13:54:45Z

    IGNITE-10192 Optimized MarshallerTest#_testAllocationOverflow. Buffer 
expansion in GridUnsafeDataOutput improved.

----


> OptimizedMarshallerTest#testAllocationOverflow throws OOME instead of 
> expected IOE
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-10192
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10192
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Oleg Ignatenko
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>
> OptimizedMarshallerTest#_testAllocationOverflow (in current codebase muted by 
> renaming to {{_testAllocationOverflow}}) throws OOME instead of expected IOE 
> when trying to marshal {{HugeObject}} - which in turn writes 4 times {{new 
> byte\[1 << 31 - 2]}}.
> Note test javadocs say: "WARNING! Requires a lot of heap space. Should not be 
> run on CI."



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to