[ https://issues.apache.org/jira/browse/HIVE-14476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622424#comment-15622424 ]
Sergio Peña commented on HIVE-14476: ------------------------------------ These 3 tests may be fixed with HIVE-13587 {noformat} org.apache.hive.minikdc.TestHiveAuthFactory.testStartTokenManagerForDBTokenStore (batchId=426) org.apache.hive.minikdc.TestHiveAuthFactory.testStartTokenManagerForMemoryTokenStore (batchId=426) org.apache.hive.minikdc.TestMiniHiveKdc.testLogin (batchId=423) {noformat} These 3 tests are also failing on master {noformat} org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJarWithoutAddDriverClazz[0] (batchId=250) org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[0] (batchId=250) org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[1] (batchId=250 {noformat} I don't know what could be causing the failures on the other tests. Are they also failing locally? If they do fail locally, I usually try to search for the commit that is causing those failures. That commit can give you a better idea how to fix it. I use 'git bisect' to investigate the commit. > Fix logging issue for branch-1 > ------------------------------ > > Key: HIVE-14476 > URL: https://issues.apache.org/jira/browse/HIVE-14476 > Project: Hive > Issue Type: Bug > Reporter: Tao Li > Assignee: Tao Li > Attachments: HIVE-14476.1-branch-1.2.patch > > > This issue is from branch-1 code when we decide if a log entry is an > operational log or not (the operational logs are visible to the client). The > problem is that the code is checking the logging mode at the beginning of the > decide() method, while the logging mode is updated after that check. Due to > this issue, we ran into an issue that an operational log could be filtered > out if it's the very first log being checked from the this method. As a > result, that particular log is not showing up for the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)