You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2015/11/23 21:17:11 UTC

[jira] [Updated] (CASSANDRA-10019) UFPureScriptTest.testJavascriptTupleType fails on uninitialized thread id

     [ https://issues.apache.org/jira/browse/CASSANDRA-10019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ariel Weisberg updated CASSANDRA-10019:
---------------------------------------
    Component/s: Testing
                 Local Write-Read Paths

> UFPureScriptTest.testJavascriptTupleType fails on uninitialized thread id
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10019
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10019
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths, Testing
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>             Fix For: 3.0 beta 1
>
>
> http://cassci.datastax.com/view/trunk/job/trunk_utest/492/testReport/junit/org.apache.cassandra.cql3.validation.entities/UFPureScriptTest/testJavascriptTupleType/
> The thread ID is retrieved from the executor service when the task executes which may not be immediately. There appear to be scenarios where it will try to get CPU time for the uninitialized thread id.
> I propose waiting for the thread id to be set up to a timeout in the event it isn't set.



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