Build #3,547

Plan branch:
Deploys Reference Application SNAPSHOT to maven

Stages & jobs

  1. Create Reference Application packages

  2. Upload parent pom to maven

  3. Deploy to Automated Functional Test Server

  4. Run UI Tests

  5. Deploy to Manual Test Server

  6. Release

    Requires a user to start manually

  7. Create Standalone

Build result summary

Details

Completed
Queue duration
1 second
Duration
15 minutes
Labels
None
Revisions
Distribution
beb4606ac68ac020834a076d9580cdd1b68f6058
Standalone RA
2cc1eedc8952f87a71cc34e7c976f30d82d62c32
Release scripts
fd5310f196074c1101fc7f1e2349005e2f083d72
Total tests
19
Failing since
#3531 (Changes by Tomasz Mueller <tmueller@soldevelo.com> – )
Fixed in
#3562 (Child of UITF-UITF-47)

Tests

Responsible

This build has been failing since #3531
No one has taken responsibility

Code commits

Distribution
Author Commit Message Commit date
tomaszmueller <tmueller@soldevelo.com> tomaszmueller <tmueller@soldevelo.com> beb4606ac68ac020834a076d9580cdd1b68f6058 Merge pull request #61 from nataliaplonka/RA-786
RA-786 Automating RA-686 Find recently Patient Record Test
Natalia Plonka <nplonka@soldevelo.com> Natalia Plonka <nplonka@soldevelo.com> e261a27d0c290266051094e742d1f0a763b3c555 m RA-789 without selenium

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

New test failures 3
Status Test View job Duration
Collapse Failed CheckModules checkModules
Run UI tests on Travis 10 secs 
org.junit.ComparisonFailure: module not ready: Reference Metadata Module [Not Started] expected:<st[op]> but was:<st[art]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at org.openmrs.reference.CheckModules.checkModules(CheckModules.java:40)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
(30 more lines...)
Collapse Failed ServiceTest AddServiceTest
Run UI tests on Travis 10 secs 
org.openqa.selenium.WebDriverException: unknown error: Element is not clickable at point (965, 34). Other element would receive the click: <div class="toast-item toast-type-success" style="opacity: 0.218906430774783;">...</div>   (Session info: chrome=43.0.2357.81)   (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Linux 3.13.0-49-generic x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 67 milliseconds Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42', time: '2013-10-18 09:51:02' System info: host: 'gw108', ip: '149.165.228.106', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-49-generic', java.version: '1.7.0_79' Session ID: c12d03f4c0a1d3444e67c5413c982fa3 Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, chrome={userDataDir=/tmp/.com.google.Chrome.hRda6H}, rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, version=43.0.2357.81, takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=false, takesScreenshot=true}]
org.openqa.selenium.WebDriverException: unknown error: Element is not clickable at point (965, 34). Other element would receive the click: <div class="toast-item toast-type-success" style="opacity: 0.218906430774783;">...</div>
  (Session info: chrome=43.0.2357.81)
  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Linux 3.13.0-49-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 67 milliseconds
Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42', time: '2013-10-18 09:51:02'
System info: host: 'gw108', ip: '149.165.228.106', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-49-generic', java.version: '1.7.0_79'
Session ID: c12d03f4c0a1d3444e67c5413c982fa3
(49 more lines...)
Collapse Failed ServiceTest DeleteServiceTest
Run UI tests on Travis 1 min 
org.openqa.selenium.TimeoutException: Timed out after 30 seconds waiting for presence of element located by: By.id: username Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42', time: '2013-10-18 09:51:02' System info: host: 'gw108', ip: '149.165.228.106', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-49-generic', java.version: '1.7.0_79' Driver info: driver.version: unknown
org.openqa.selenium.TimeoutException: Timed out after 30 seconds waiting for presence of element located by: By.id: username
Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42', time: '2013-10-18 09:51:02'
System info: host: 'gw108', ip: '149.165.228.106', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-49-generic', java.version: '1.7.0_79'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:259)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:228)
	at org.openmrs.uitestframework.page.AbstractBasePage.findElement(AbstractBasePage.java:51)
(66 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeRA-686Could not obtain issue details from Jira
Unknown Issue TypeRA-786Could not obtain issue details from Jira
Unknown Issue TypeRA-789Could not obtain issue details from Jira