[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (99 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues.apache.org/jira/browse/OOZIE-2588
OOZIE-2587  Background services should be disabled for certain tests
https://issues.apache.org/jira/browse/OOZIE-2587
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues.apache.org/jira/browse/OOZIE-2582
OOZIE-2581  Oozie should reset SecurityManager in finally block
https://issues.apache.org/jira/browse/OOZIE-2581
OOZIE-2579  Bulk kill tests in TestBulkWorkflowXCommand might fail because of a 
race condition
https://issues.apache.org/jira/browse/OOZIE-2579
OOZIE-2574  Oozie to support replication-enabled mysql urls
https://issues.apache.org/jira/browse/OOZIE-2574
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues.apache.org/jira/browse/OOZIE-2572
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues.apache.org/jira/browse/OOZIE-2568
OOZIE-2565  [Oozie web Console] Make the timezones in settings tab to be sorted 
by default
https://issues.apache.org/jira/browse/OOZIE-2565
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues.apache.org/jira/browse/OOZIE-2564
OOZIE-2555  Oozie SSL enable setup does not return port for admin -servers
https://issues.apache.org/jira/browse/OOZIE-2555
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues.apache.org/jira/browse/OOZIE-2552
OOZIE-2539  Incorrect property key is used for 'hive log4j configuration file 
for execution mode'
https://issues.apache.org/jira/browse/OOZIE-2539
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues.apache.org/jira/browse/OOZIE-2521
OOZIE-2520  SortBy filter for ordering the jobs query results
https://issues.apache.org/jira/browse/OOZIE-2520
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues.apache.org/jira/browse/OOZIE-2517
OOZIE-2516  Update web service documentation for jobs API
https://issues.apache.org/jira/browse/OOZIE-2516
OOZIE-2515  Duplicate information for "Changing endtime/pausetime of a Bundle 
Job" in CommandLineTool wiki
https://issues.apache.org/jira/browse/OOZIE-2515
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues.apache.org/jira/browse/OOZIE-2513
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues.apache.org/jira/browse/OOZIE-2508
OOZIE-2507  Expose monitoring via JMX beans in Oozie
https://issues.apache.org/jira/browse/OOZIE-2507
OOZIE-2506  Add logs into RecoverService for logging information about queued 
commnads
https://issues.apache.org/jira/browse/OOZIE-2506
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues.apache.org/jira/browse/OOZIE-2499
OOZIE-2498 

Jenkins build is back to normal : oozie-trunk-find-patches-available #125543

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #125542

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson3102509770904129482.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  306k0  306k0 0   209k  0 --:--:--  0:00:01 --:--:--  209k
100  561k0  561k0 0   231k  0 --:--:--  0:00:02 --:--:--  231k
100  888k0  888k0 0   262k  0 --:--:--  0:00:03 --:--:--  262k
100 1264k0 1264k0 0   287k  0 --:--:--  0:00:04 --:--:--  287k
100 1746k0 1746k0 0   315k  0 --:--:--  0:00:05 --:--:--  345k
100 1746k0 1746k0 0   315k  0 --:--:--  0:00:05 --:--:--  353k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Build failed in Jenkins: oozie-trunk-precommit-build #3019

[Apache Jenkins Server]

See 

--
[...truncated 8404 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run

[jira] [Commented] (OOZIE-2589) CompletedActionXCommand priority param is of no effect

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2589:
--

Testing JIRA OOZIE-2589

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1787
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3019/

> CompletedActionXCommand priority param is of no effect
> --
>
> Key: OOZIE-2589
> URL: https://issues.apache.org/jira/browse/OOZIE-2589
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Linflytang
>  Labels: patch
> Fix For: trunk
>
> Attachments: 0001-Fixed-CompletedActionXCommand-priority-param.patch
>
>
> CompletedActionXCommand priority param is hard coding with 1, but create the 
> action with 2 (HIGH_PRIORITY).
> patch:https://github.com/apache/oozie/pull/20/files



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

[jira] [Updated] (OOZIE-2589) CompletedActionXCommand priority param is of no effect

[Linflytang (JIRA)]

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

Linflytang updated OOZIE-2589:
--
Attachment: 0001-Fixed-CompletedActionXCommand-priority-param.patch

only change a param

> CompletedActionXCommand priority param is of no effect
> --
>
> Key: OOZIE-2589
> URL: https://issues.apache.org/jira/browse/OOZIE-2589
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Linflytang
>  Labels: patch
> Fix For: trunk
>
> Attachments: 0001-Fixed-CompletedActionXCommand-priority-param.patch
>
>
> CompletedActionXCommand priority param is hard coding with 1, but create the 
> action with 2 (HIGH_PRIORITY).
> patch:https://github.com/apache/oozie/pull/20/files



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

[jira] [Updated] (OOZIE-2589) CompletedActionXCommand priority param is of no effect

[Linflytang (JIRA)]

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

Linflytang updated OOZIE-2589:
--
Description: 
CompletedActionXCommand priority param is hard coding with 1, but create the 
action with 2 (HIGH_PRIORITY).

patch:https://github.com/apache/oozie/pull/20/files

  was:CompletedActionXCommand priority param is hard coding with 1, but create 
the action with 2 (HIGH_PRIORITY).


> CompletedActionXCommand priority param is of no effect
> --
>
> Key: OOZIE-2589
> URL: https://issues.apache.org/jira/browse/OOZIE-2589
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Linflytang
> Fix For: trunk
>
>
> CompletedActionXCommand priority param is hard coding with 1, but create the 
> action with 2 (HIGH_PRIORITY).
> patch:https://github.com/apache/oozie/pull/20/files



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

[jira] [Created] (OOZIE-2589) CompletedActionXCommand priority param is of no effect

[Linflytang (JIRA)]

Linflytang created OOZIE-2589:
-

 Summary: CompletedActionXCommand priority param is of no effect
 Key: OOZIE-2589
 URL: https://issues.apache.org/jira/browse/OOZIE-2589
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: trunk
Reporter: Linflytang
 Fix For: trunk


CompletedActionXCommand priority param is hard coding with 1, but create the 
action with 2 (HIGH_PRIORITY).



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

Jenkins build is back to normal : oozie-trunk-find-patches-available #125515

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #125514

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson233290920717046187.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries 
Warning: left.

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries 
Warning: left.

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries 
Warning: left.

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 503 Service Unavailable
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #125513

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #125511

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson7821233440946538186.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:05 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:06 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:07 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:08 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:09 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:10 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:31 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:32 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:33 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:34 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:35 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:36 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:37 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:38 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:39 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:40 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:41 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:42 --:--:-- 0
  0 00 00   

Build failed in Jenkins: oozie-trunk-find-patches-available #125509

[Apache Jenkins Server]

See 

--
Started by timer
Started by timer
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson7022748127283237293.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:05 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:06 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:07 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:08 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:09 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:10 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
100 174030 174030 0   1036  0 --:--:--  0:00:16 --:--:--  3130
100 174030 174030 0   1004  0 --:--:--  0:00:17 --:--:--  3411
100 893390 893390 0   4745  0 --:--:--  0:00:18 --:--:-- 15956
100 893390 893390 0   4505  0 --:--:--  0:00:19 --:--:-- 15956
100 893390 893390 0   4289  0 --:--:--  0:00:20 --:--:-- 15956
100 893390 893390 0   4092  0 --:--:--  0:00:21 --:--:-- 14261
100 893390 893390 0   3912  0 --:--:--  0:00:22 --:--:-- 13069
100 893390 893390 0   3748  0 --:--:--  0:00:23 --:--:-- 0
100 893390 893390 0   3597  0 --:--:--  0:00:24 --:--:-- 0
100 893390 893390 0   3458  0 --:--:--  0:00:25 --:--:-- 0
100 893390 893390 0   3329  0 --:--:--  0:00:26 --:--:-- 0
100 893390 893390 0   3209  0 --:--:--  0:00:27 --:--:-- 0
100 893390 893390 0   3097  0 --:--:--  0:00:28 --:--:-- 0
100 893390 893390 0   2993  0 --:--:--  0:00:29 --:--:-- 0
100 893390 893390 0   2896  0 --:--:--  0:00:30 --:--:-- 0
100 893390 893390 0   2805  0 --:--:--  0:00:31 --:--:-- 0
100 893390 893390 0   2720  0 --:--:--  0:00:32 --:--:-- 0
100 893390 893390 0   2639  0 --:--:--  0:00:33 --:--:-- 0
100 893390 893390 0   2563  0 --:--:--  0:00:34 --:--:-- 0
100 893390 893390 0   2492  0 --:--:--  0:00:35 --:--:-- 0
100 893390 893390 0   2424  0 --:--:--  0:00:36 --:--:-- 0
100 893390 893390 0   2360  0 --:--:--  0:00:37 --:--:-- 0
100 893390 893390 0   2299  0 --:--:--  0:00:38 --:--:-- 0
100 893390 893390 0   2241  0 --:--:--  0:00:39 --:--:-- 0
100 893390 893390 0   2186  0 --:--:--  0:00:40 --:--:-- 0
100 893390 893390 0   2134  0 --:--:--  0:00:41 --:--:-- 0
100 893390 893390 0   2084  0 --:--:--  0:00:42 --:--:-- 

Build failed in Jenkins: oozie-trunk-find-patches-available #125508

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson2831162533662326401.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:05 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:06 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:07 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:08 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:09 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:10 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
100 174030 174030 0679  0 --:--:--  0:00:25 --:--:--  3981
100 533710 533710 0   1980  0 --:--:--  0:00:26 --:--:-- 11362
100 893390 893390 0   3173  0 --:--:--  0:00:28 --:--:-- 18254
100 893390 893390 0   3064  0 --:--:--  0:00:29 --:--:-- 18254
100 893390 893390 0   2962  0 --:--:--  0:00:30 --:--:-- 18221
100 893390 893390 0   2867  0 --:--:--  0:00:31 --:--:-- 13013
100 893390 893390 0   2778  0 --:--:--  0:00:32 --:--:--  6914
100 893390 893390 0   2694  0 --:--:--  0:00:33 --:--:-- 0
100 893390 893390 0   2615  0 --:--:--  0:00:34 --:--:-- 0
100 893390 893390 0   2541  0 --:--:--  0:00:35 --:--:-- 0
100 893390 893390 0   2470  0 --:--:--  0:00:36 --:--:-- 0
100 893390 893390 0   2404  0 --:--:--  0:00:37 --:--:-- 0
100 893390 893390 0   2341  0 --:--:--  0:00:38 --:--:-- 0
100 893390 893390 0   2281  0 --:--:--  0:00:39 --:--:-- 0
100 893390 893390 0   2224  0 --:--:--  0:00:40 --:--:-- 0
100 893390 893390 0   2170  0 --:--:--  0:00:41 --:--:-- 0
100 893390 893390 0   2118  0 --:--:--  0:00:42 --:--:-- 0
100 893390 893390   

[GitHub] oozie pull request #21: extjs filter that leads to replay attacks problems

[philippeback]

GitHub user philippeback opened a pull request:

https://github.com/apache/oozie/pull/21

extjs filter that leads to replay attacks problems

Remove the filter which causes double work on the KDC and leads to replay 
attacks and a non working oozie ui when in a kerberos aware browser against a 
kerberos cluster.

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

$ git pull https://github.com/philippeback/oozie patch-1

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

https://github.com/apache/oozie/pull/21.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 #21


commit 3ab4713cb87474e135c3d0ab433d95bc649b4ff7
Author: Philippe Back 
Date:   2016-06-29T21:09:20Z

extjs filter that leads to replay attacks problems

Remove the filter which causes double work on the KDC and leads to replay 
attacks and a non working oozie ui when in a kerberos aware browser against a 
kerberos cluster.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: oozie-trunk-find-patches-available #125486

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson4731920836125619648.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100 353880 353880 0  51545  0 --:--:-- --:--:-- --:--:-- 51510
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Commented] (OOZIE-2587) Background services should be disabled for certain tests

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2587:
--

Testing JIRA OOZIE-2587

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1787
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testSlaChange(org.apache.oozie.client.TestOozieCLI)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3018/

> Background services should be disabled for certain tests
> 
>
> Key: OOZIE-2587
> URL: https://issues.apache.org/jira/browse/OOZIE-2587
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2587-001.patch
>
>
> There are test cases which might fail because they interfere with some 
> background threads.
> Some examples:
> 1. TestBundleChangeXCommand.testBundlePauseExtendMaterializesCoordinator - 
> can fail because of CoordMaterializeTriggerService
> 2. TestAbandonedCoordChecker.testMessage_withMixedStatus - can fail because 
> of StatusTransitService
> 3. TestCoordChangeXCommand.testCoordStatus_Killed - can fail because of 
> StatusTransitService
> There could be more, but I can confirm that these are affected. 
> Solution: either disable SchedulerService or only the offending background 
> service.



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

Jenkins build is back to normal : oozie-trunk-find-patches-available #125487

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-precommit-build #3018

[Apache Jenkins Server]

See 

--
[...truncated 8396 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run

Jenkins build is back to normal : oozie-trunk-find-patches-available #125485

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #125484

[Apache Jenkins Server]

See 

--
Started by timer
Started by timer
Started by timer
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson175525265800517539.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100 893390 893390 0  47966  0 --:--:--  0:00:01 --:--:-- 47980
100 893390 893390 0  31198  0 --:--:--  0:00:02 --:--:-- 31204
100 893390 893390 0  23116  0 --:--:--  0:00:03 --:--:-- 23120
100 893390 893390 0  18360  0 --:--:--  0:00:04 --:--:-- 18363
100 893390 893390 0  15227  0 --:--:--  0:00:05 --:--:-- 15229
100 893390 893390 0  13007  0 --:--:--  0:00:06 --:--:-- 0
100 893390 893390 0  11352  0 --:--:--  0:00:07 --:--:-- 0
100 893390 893390 0  10071  0 --:--:--  0:00:08 --:--:-- 0
100 893390 893390 0   9050  0 --:--:--  0:00:09 --:--:-- 0
100 893390 893390 0   8216  0 --:--:--  0:00:10 --:--:-- 0
100 893390 893390 0   7523  0 --:--:--  0:00:11 --:--:-- 0
100 893390 893390 0   6938  0 --:--:--  0:00:12 --:--:-- 0
100 893390 893390 0   6438  0 --:--:--  0:00:13 --:--:-- 0
100 893390 893390 0   6005  0 --:--:--  0:00:14 --:--:-- 0
100 893390 893390 0   5626  0 --:--:--  0:00:15 --:--:-- 0
100 893390 893390 0   5292  0 --:--:--  0:00:16 --:--:-- 0
100 893390 893390 0   4996  0 --:--:--  0:00:17 --:--:-- 0
100 893390 893390 0   4731  0 --:--:--  0:00:18 --:--:-- 0
100 893390 893390 0   4493  0 --:--:--  0:00:19 --:--:-- 0
100 893390 893390 0   4277  0 --:--:--  0:00:20 --:--:-- 0
100 893390 893390 0   4082  0 --:--:--  0:00:21 --:--:-- 0
100 893390 893390 0   3903  0 --:--:--  0:00:22 --:--:-- 0
100 893390 893390 0   3740  0 --:--:--  0:00:23 --:--:-- 0
100 893390 893390 0   3589  0 --:--:--  0:00:24 --:--:-- 0
100 893390 893390 0   3450  0 --:--:--  0:00:25 --:--:-- 0
100 893390 893390 0   3322  0 --:--:--  0:00:26 --:--:-- 0
100 893390 893390 0   3203  0 --:--:--  0:00:27 --:--:-- 0
100 893390 893390 0   3092  0 --:--:--  0:00:28 --:--:-- 0
100 893390 893390 0   2988  0 --:--:--  0:00:29 --:--:-- 0
100 893390 893390 0   2891  0 --:--:--  0:00:30 --:--:-- 0
100 893390 893390 0   2800  0 --:--:--  0:00:31 --:--:-- 0
100 893390 893390 0   2715  0 --:--:--  0:00:32 --:--:-- 0
100 893390 893390 0   2635  0 --:--:--  0:00:33 --:--:-- 0
100 893390 893390 0   2559  0 --:--:--  0:00:34 --:--:-- 0
100 893390 893390 0   2488  0 --:--:--  0:00:35 --:--:-- 0
100 893390 893390 0   2421  0 --:--:--  0:00:36 --:--:-- 0
100 893390 893390 0   2357  0 --:--:--  0:00:37 --:--:-- 0
100 893390 893390 0   2296  0 --:--:--  0:00:38 --:--:-- 0
100 893390 893390 0   2238  0 --:--:--  0:00:39 --:--:-- 0
100 893390 893390 0   2184  0 --:--:--  0:00:40 --:--:-- 0
100 893390 893390 0   2131  0 --:--:--  0:00:41 --:--:-- 0
100 893390 893390 0   2082  0 --:--:--  0

[jira] [Updated] (OOZIE-2587) Background services should be disabled for certain tests

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2587:

Attachment: OOZIE-2587-001.patch

> Background services should be disabled for certain tests
> 
>
> Key: OOZIE-2587
> URL: https://issues.apache.org/jira/browse/OOZIE-2587
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2587-001.patch
>
>
> There are test cases which might fail because they interfere with some 
> background threads.
> Some examples:
> 1. TestBundleChangeXCommand.testBundlePauseExtendMaterializesCoordinator - 
> can fail because of CoordMaterializeTriggerService
> 2. TestAbandonedCoordChecker.testMessage_withMixedStatus - can fail because 
> of StatusTransitService
> 3. TestCoordChangeXCommand.testCoordStatus_Killed - can fail because of 
> StatusTransitService
> There could be more, but I can confirm that these are affected. 
> Solution: either disable SchedulerService or only the offending background 
> service.



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

[jira] [Updated] (OOZIE-2587) Background services should be disabled for certain tests

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2587:

Attachment: (was: OOZIE-2587-001.patch)

> Background services should be disabled for certain tests
> 
>
> Key: OOZIE-2587
> URL: https://issues.apache.org/jira/browse/OOZIE-2587
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2587-001.patch
>
>
> There are test cases which might fail because they interfere with some 
> background threads.
> Some examples:
> 1. TestBundleChangeXCommand.testBundlePauseExtendMaterializesCoordinator - 
> can fail because of CoordMaterializeTriggerService
> 2. TestAbandonedCoordChecker.testMessage_withMixedStatus - can fail because 
> of StatusTransitService
> 3. TestCoordChangeXCommand.testCoordStatus_Killed - can fail because of 
> StatusTransitService
> There could be more, but I can confirm that these are affected. 
> Solution: either disable SchedulerService or only the offending background 
> service.



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

Jenkins build is back to normal : oozie-trunk-find-patches-available #125480

[Apache Jenkins Server]

See 

[jira] [Commented] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2585:
--

Testing JIRA OOZIE-2585

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1784
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3017/

> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2585-001.patch, OOZIE-2585-002.patch
>
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

Jenkins build is back to normal : oozie-trunk-precommit-build #3017

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #125479

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson5880861137499453488.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:05 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:06 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:07 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:08 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:09 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:10 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:12 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:13 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:14 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:15 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:16 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:17 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:18 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:19 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:20 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:21 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:22 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:23 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:24 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:25 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:26 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:27 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:28 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:29 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:30 --:--:-- 0
100 353870 353870 0   1123  0 --:--:--  0:00:31 --:--:--  8332
100  113k0  113k0 0   3589  0 --:--:--  0:00:32 --:--:-- 27978
100  210k0  210k0 0   6362  0 --:--:--  0:00:33 --:--:-- 46979
100  210k0  210k0 0   6179  0 --:--:--  0:00:34 --:--:-- 46979
100  210k0  210k0 0   6007  0 --:--:--  0:00:35 --:--:-- 44263
100  210k0  210k0 0   5843  0 --:--:--  0:00:36 --:--:-- 33681
100  210k0  210k0 0   5689  0 --:--:--  0:00:37 --:--:-- 18221
100  210k0  210k0 0   5542  0 --:--:--  0:00:38 --:--:-- 0
100  210k0  210k0 0   5403  0 --:--:--  0:00:39 --:--:-- 0
100  210k0  210k0 0   5270  0 --:--:--  0:00:40 --:--:-- 0
100  210k0  210k0 0   5184  0 --:--:--  0:00:41 --:--:-- 0
100  324k0  324k0   

[jira] [Commented] (OOZIE-2584) Eliminate Thread.sleep() calls in TestMemoryLocks

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2584:
---

+1

> Eliminate Thread.sleep() calls in TestMemoryLocks
> -
>
> Key: OOZIE-2584
> URL: https://issues.apache.org/jira/browse/OOZIE-2584
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2584-001.patch, OOZIE-2584-002.patch
>
>
> There are a lot of Thread.sleep() calls in TestMemoryLocks.
> For example:
> {code}
> new Thread(l1).start();
> Thread.sleep(500);
> new Thread(l2).start();
> Thread.sleep(500);
> {code}
> This solution is very fragile. On a slower build machine, Thread2 might 
> actually start earlier than Thread1, causing test failure.
> Eliminate sleeps and use a more stable approach for start/stop coordination 
> (possibly CountDownLatches).



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

[jira] [Commented] (OOZIE-2584) Eliminate Thread.sleep() calls in TestMemoryLocks

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2584:
---

Thanks for the explanation and the fix!
+1 (nonbinding)

> Eliminate Thread.sleep() calls in TestMemoryLocks
> -
>
> Key: OOZIE-2584
> URL: https://issues.apache.org/jira/browse/OOZIE-2584
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2584-001.patch, OOZIE-2584-002.patch
>
>
> There are a lot of Thread.sleep() calls in TestMemoryLocks.
> For example:
> {code}
> new Thread(l1).start();
> Thread.sleep(500);
> new Thread(l2).start();
> Thread.sleep(500);
> {code}
> This solution is very fragile. On a slower build machine, Thread2 might 
> actually start earlier than Thread1, causing test failure.
> Eliminate sleeps and use a more stable approach for start/stop coordination 
> (possibly CountDownLatches).



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

[jira] [Updated] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2585:

Attachment: OOZIE-2585-002.patch

> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2585-001.patch, OOZIE-2585-002.patch
>
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

[jira] [Commented] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2585:
--

Testing JIRA OOZIE-2585

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1787
.Tests failed: 5
.Tests errors: 2

.The patch failed the following testcases:

.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3016/

> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2585-001.patch
>
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

Build failed in Jenkins: oozie-trunk-precommit-build #3016

[Apache Jenkins Server]

See 

--
[...truncated 8409 lines...]
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.t

[jira] [Commented] (OOZIE-2584) Eliminate Thread.sleep() calls in TestMemoryLocks

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2584:
--

Testing JIRA OOZIE-2584

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1787
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3015/

> Eliminate Thread.sleep() calls in TestMemoryLocks
> -
>
> Key: OOZIE-2584
> URL: https://issues.apache.org/jira/browse/OOZIE-2584
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2584-001.patch, OOZIE-2584-002.patch
>
>
> There are a lot of Thread.sleep() calls in TestMemoryLocks.
> For example:
> {code}
> new Thread(l1).start();
> Thread.sleep(500);
> new Thread(l2).start();
> Thread.sleep(500);
> {code}
> This solution is very fragile. On a slower build machine, Thread2 might 
> actually start earlier than Thread1, causing test failure.
> Eliminate sleeps and use a more stable approach for start/stop coordination 
> (possibly CountDownLatches).



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

Jenkins build is back to normal : oozie-trunk-precommit-build #3015

[Apache Jenkins Server]

See 

[jira] [Updated] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2585:

Attachment: OOZIE-2585-001.patch

> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2585-001.patch
>
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

[jira] [Updated] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2585:

Summary: Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed  (was: Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk)

> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

[jira] [Updated] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2585:

Description: 
There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.

After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
separate thread asynchronously and all put operations return immediately. The 
problem is that after storing the 60k entries, we try to read them back 
instantly, with many of them are still being flushed to the storage. As long as 
disk write in progress, these entries are unavailable.

I didn't find a reliable way to wait for disk writes. Therefore I suggest 
disabling this test or eliminate it altogether -- it's a performance test that 
runs on all kinds of machines during a build, I don't think it makes too much 
sense to keep it.

Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
assertions might evaluate to false:
{code}
assertTrue((endTime - startTime) < insertTimeinMillis);
...
assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
{code}

  was:
There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.

After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
separate thread asynchronously and all put operations return immediately. The 
problem is that after storing the 60k entries, we try to read them back 
instantly, with many of them are still being flushed to the storage. As long as 
disk write in progress, these entries are unavailable.

I didn't find a reliable way to wait for disk writes. Therefore I suggest 
disabling this test or eliminate it altogether -- it's a performance test that 
runs on all kinds of machines during a build, I don't think it makes too much 
sense to keep it.


> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

[jira] [Updated] (OOZIE-2584) Eliminate Thread.sleep() calls in TestMemoryLocks

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2584:

Attachment: OOZIE-2584-002.patch

> Eliminate Thread.sleep() calls in TestMemoryLocks
> -
>
> Key: OOZIE-2584
> URL: https://issues.apache.org/jira/browse/OOZIE-2584
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2584-001.patch, OOZIE-2584-002.patch
>
>
> There are a lot of Thread.sleep() calls in TestMemoryLocks.
> For example:
> {code}
> new Thread(l1).start();
> Thread.sleep(500);
> new Thread(l2).start();
> Thread.sleep(500);
> {code}
> This solution is very fragile. On a slower build machine, Thread2 might 
> actually start earlier than Thread1, causing test failure.
> Eliminate sleeps and use a more stable approach for start/stop coordination 
> (possibly CountDownLatches).



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

Jenkins build is back to normal : oozie-trunk-find-patches-available #125468

[Apache Jenkins Server]

See 

[jira] [Commented] (OOZIE-2584) Eliminate Thread.sleep() calls in TestMemoryLocks

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2584:
-

I was thinking - if the machine is very slow, 1000ms of timeout in 
testTimeoutWaitingWriteLock can be a problem.

If it takes too much time to execute
{code}
l1.proceed();
l1.awaitTermination();
{code}

then L2 might time out. I will increase the value to 1 - that really should 
be enough. Same applies to testWriteLockSameThreadWait.

> Eliminate Thread.sleep() calls in TestMemoryLocks
> -
>
> Key: OOZIE-2584
> URL: https://issues.apache.org/jira/browse/OOZIE-2584
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2584-001.patch
>
>
> There are a lot of Thread.sleep() calls in TestMemoryLocks.
> For example:
> {code}
> new Thread(l1).start();
> Thread.sleep(500);
> new Thread(l2).start();
> Thread.sleep(500);
> {code}
> This solution is very fragile. On a slower build machine, Thread2 might 
> actually start earlier than Thread1, causing test failure.
> Eliminate sleeps and use a more stable approach for start/stop coordination 
> (possibly CountDownLatches).



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

Build failed in Jenkins: oozie-trunk-find-patches-available #125467

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs yahoo-not-h2) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5
 > git rev-list 1c4d56164ed2ea787cddaecd27b1e4ee6e2b3ab5 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson6027596680441594823.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:05 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:06 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:07 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:08 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:09 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:10 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:11 --:--:-- 0
  0 00 00 0  0  0 --:--:--  0:00:11 --:--:-- 0
100 901120 901120 0   7233  0 --:--:--  0:00:12 --:--:-- 21272
100  306k0  306k0 0  23228  0 --:--:--  0:00:13 --:--:-- 73050
100  517k0  517k0 0  36628  0 --:--:--  0:00:14 --:--:--  121k
100  833k0  833k0 0  54925  0 --:--:--  0:00:15 --:--:--  193k
100 1256k0 1256k0 0  78016  0 --:--:--  0:00:16 --:--:--  279k
100 1680k0 1680k0 0  98536  0 --:--:--  0:00:17 --:--:--  318k
100 1729k0 1729k0 0  99296  0 --:--:--  0:00:17 --:--:--  330k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Commented] (OOZIE-2584) Eliminate Thread.sleep() calls in TestMemoryLocks

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2584:
-

I think you mean testTimeoutTimingOutWriteLock.

No, I don't think it can cause problems: 
- L2 will time out for sure, because L1 holds the lock at that point 
(guaranteed)
- We call proceed(), L2 will continue terminating in the else branch
- We call awaitTermination() so we wait until L2 finishes

> Eliminate Thread.sleep() calls in TestMemoryLocks
> -
>
> Key: OOZIE-2584
> URL: https://issues.apache.org/jira/browse/OOZIE-2584
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2584-001.patch
>
>
> There are a lot of Thread.sleep() calls in TestMemoryLocks.
> For example:
> {code}
> new Thread(l1).start();
> Thread.sleep(500);
> new Thread(l2).start();
> Thread.sleep(500);
> {code}
> This solution is very fragile. On a slower build machine, Thread2 might 
> actually start earlier than Thread1, causing test failure.
> Eliminate sleeps and use a more stable approach for start/stop coordination 
> (possibly CountDownLatches).



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