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

ASF GitHub Bot commented on THRIFT-3632:
----------------------------------------

GitHub user nsuke opened a pull request:

    https://github.com/apache/thrift/pull/865

    THRIFT-3632 c_glib testserialization fails with glib assertion

    

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

    $ git pull https://github.com/nsuke/thrift THRIFT-3632

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

    https://github.com/apache/thrift/pull/865.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 #865
    
----
commit 336fa5a8e7bebb4f0e2806b138a37d4b8601320f
Author: Nobuaki Sukegawa <[email protected]>
Date:   2016-02-14T11:22:11Z

    THRIFT-3632 c_glib testserialization fails with glib assertion

----


> c_glib testserialization fails with glib assertion
> --------------------------------------------------
>
>                 Key: THRIFT-3632
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3632
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Compiler
>         Environment: ArchLinux
> GCC 5.3.0
> GLib-2.46.2
>            Reporter: Aki Sukegawa
>            Assignee: Aki Sukegawa
>
> Recently it suddenly started failing in my local environment, but no any of 
> CI.
> As it's assertion failure, I suspect it's due to glib version.
> There were a few of them but adding some null check to generated code fixed 
> the problem.
> {code}
> (/home/x/proj/thrift/clean/lib/c_glib/test/.libs/lt-testserialization:24158): 
> GLib-CRITICAL **: g_hash_table_size: assertion 'hash_table != NULL' failed
> /bin/sh: line 5: 24158 Trace/breakpoint trap   (core dumped) ${dir}$tst
> FAIL: testserialization
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to