hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-16769) Possible hive service startup due to the existing file /tmp/stderr
Date Fri, 26 May 2017 16:05:04 GMT


Hive QA commented on HIVE-16769:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 10788 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[create_merge_compressed] (batchId=237)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[subquery_scalar] (batchId=152)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr] (batchId=145)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 3 tests failed

This message is automatically generated.

ATTACHMENT ID: 12870079 - PreCommit-HIVE-Build

> Possible hive service startup due to the existing file /tmp/stderr
> ------------------------------------------------------------------
>                 Key: HIVE-16769
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 2.0.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-16769.1.patch
> HIVE-12497 prints the ignoring errors from hadoop version, hbase mapredcp and hadoop
jars to /tmp/$USER/stderr. 
> In some cases $USER is not set, then the file becomes /tmp/stderr.  If  such file preexists
with different permission, it will cause the service startup to fail.
> I just tried the script without outputting to stderr file, I don't see such error any
more {{"ERROR StatusLogger No log4j2 configuration file found. Using default configuration:
logging only errors to the console."}}.
> I think we can remove such redirect to avoid possible startup failure.

This message was sent by Atlassian JIRA

View raw message