You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2019/02/08 19:18:00 UTC
[jira] [Updated] (TINKERPOP-2157) SparkStarBarrierInterceptor
injects (Byte) 0
[ https://issues.apache.org/jira/browse/TINKERPOP-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kuppitz updated TINKERPOP-2157:
--------------------------------------
Summary: SparkStarBarrierInterceptor injects (Byte) 0 (was: SparkStarBarrierInterceptor injects (Bte) 0)
> SparkStarBarrierInterceptor injects (Byte) 0
> --------------------------------------------
>
> Key: TINKERPOP-2157
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2157
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.4.1
> Reporter: Daniel Kuppitz
> Assignee: stephen mallette
> Priority: Major
>
> There are 3 tests that occasionally fail in {{SparkGraphComputerProcessIntegrateTest}}:
> * {{g_V_name_min}}
> * {{g_V_name_max}}
> * {{g_V_age_min}}
> In all cases, failure is a result of a mysterious {{(Byte) 0}}. Apparently, this zero gets injected by the {{SparkStarBarrierInterceptor}}. I came to this conclusion because I wasn't able to reproduce any of the failures after excluding this interceptor. However, the failures happen randomly*, so I can't say with 100% certainty that the interceptor is the problem.
>
> * on my system it never happened in the Docker builds, rarely in IntelliJ debug sessions, but quite often when I just run the test suite in IntelliJ
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)