Build #4,511

Plan branch:
Deploys Reference Application SNAPSHOT to maven

Build: #4511 failed Changes by Daniel Kayiwa

Stages & jobs

  1. Create Reference Application packages

  2. Deploy to Automated Functional Test Server

  3. Run UI Tests

  4. Deploy to Manual Test Server

  5. Release

    Requires a user to start manually

  6. Create Standalone

Build result summary

Details

Completed
Queue duration
4 seconds
Duration
9 minutes
Labels
None
Revisions
Distribution
3282b5e5e1629dace5cb8b3c9b1c9e70a7c83318 3282b5e5e1629dace5cb8b3c9b1c9e70a7c83318
Standalone RA
2cc1eedc8952f87a71cc34e7c976f30d82d62c32 2cc1eedc8952f87a71cc34e7c976f30d82d62c32
Release scripts
a9c6b4741f415820e397e9b150cf80baca7f9368 a9c6b4741f415820e397e9b150cf80baca7f9368
Total tests
8
Fixed in
#4512 (Manual run by Daniel Kayiwa)

Tests

Responsible

Code commits

Distribution
Author Commit Message Commit date
Daniel Kayiwa Daniel Kayiwa 3282b5e5e1629dace5cb8b3c9b1c9e70a7c83318 3282b5e5e1629dace5cb8b3c9b1c9e70a7c83318 Merge pull request #110 from yancmo/Improve_AddDiagnosisToVisitNoteTest
RA-1102 Improved reliability of AddDiagnosisToVisitNoteTest
yancmo <yancm212@yahoo.com.sg> yancmo <yancm212@yahoo.com.sg> 5324dcf6c603af4b6b1e9f42a41e927d1b3cc5ba m 5324dcf6c603af4b6b1e9f42a41e927d1b3cc5ba Improved reliability of AddDiagnosisToVisitNoteTest
- Removed end visit at end of test so that the number of patients in active visits wont decrease
- Detect end visit link (which will always be there if page is returned successfully), rather than success toast

Configuration changes

Some of the jobs or stages referenced by this result no longer exist.

Restarting failed/incomplete builds only is not possible as some of the affected jobs no longer exist.

Tests

Existing test failures 1
Status Test Failing since View job Duration 
org.openqa.selenium.TimeoutException: Timed out after 15 seconds waiting for org.openmrs.uitestframework.page.Page$1@6075ef17
Build info: version: '2.52.0', revision: '4c2593cfc3689a7fcd7be52549167e5ccc93ad28', time: '2016-02-11 11:22:43'
System info: host: 'gw108', ip: '149.165.228.106', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-77-generic', java.version: '1.7.0_95'
Session ID: 6e9b883d8d2b4237b2767b924d9eeca3
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, hasMetadata=true, browserName=firefox, rotatable=false, locationContextEnabled=true, webdriver.remote.sessionid=6e9b883d8d2b4237b2767b924d9eeca3, version=42.0, cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true, webStorageEnabled=true, nativeEvents=false, applicationCacheEnabled=true, takesScreenshot=true}]
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:80)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:261)
(4 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeRA-1102Could not obtain issue details from Jira