Jira: https://issues.apache.org/jira/browse/OOZIE-3132
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/252/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE 
###########################
[...truncated 685.06 KB...]
Hunk #1 succeeded at 533 (offset 12 lines).
Checking patch 
core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java...
error: while searching for:
import org.apache.oozie.executor.jpa.WorkflowJobQueryExecutor.WorkflowJobQuery;
import org.apache.oozie.service.ConfigurationService;
import org.apache.oozie.service.EventHandlerService;
import org.apache.oozie.service.JPAService;
import org.apache.oozie.service.Services;
import org.apache.oozie.sla.service.SLAService;
import org.apache.oozie.test.XDataTestCase;
import org.apache.oozie.util.DateUtils;
import org.apache.oozie.util.JobUtils;
import org.apache.oozie.util.Pair;
import org.apache.oozie.workflow.WorkflowInstance;

error: patch failed: 
core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java:56
error: core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java: 
patch does not apply
Checking patch docs/src/site/twiki/DG_SLAMonitoring.twiki...
error: while searching for:

---++ Accessing SLA Information

SLA information is accessible via the following two ways
   * Through the SLA tab of the Oozie Web UI.
   * JMS messages sent to a configured JMS provider for instantaneous tracking.
   * RESTful API to query for SLA summary.

For JMS Notifications, you have to have a message broker in place, on which 
Oozie publishes messages and you can
hook on a subscriber to receive those messages. For more info on setting up and 
consuming JMS messages, refer

error: patch failed: docs/src/site/twiki/DG_SLAMonitoring.twiki:151
error: docs/src/site/twiki/DG_SLAMonitoring.twiki: patch does not apply
Checking patch src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java...
error: src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/util/Instrumentation.java...
error: src/main/java/org/apache/oozie/util/Instrumentation.java: No such file 
or directory
Checking patch 
src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java...
error: src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java: No such 
file or directory
Checking patch src/site/twiki/DG_SLAMonitoring.twiki...
error: src/site/twiki/DG_SLAMonitoring.twiki: No such file or directory
Patch failed to apply to head of branch

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0 3706k    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     
0100 3706k  100 3706k    0     0  3363k      0  0:00:01  0:00:01 --:--:-- 17.6M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3132
Archiving artifacts
[Fast Archiver] Compressed 864.13 KB of artifacts by 25.9% relative to #242
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###################################################################################
############################## FAILED TESTS (if any) 
##############################
No tests ran.

Reply via email to