Build #593

Plan branch:

Stages & jobs

  1. Build

  2. Package

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
3 minutes
Labels
None
Revisions
Git
23d3a0fa45f6ce82970685d94b539f18358d0681 23d3a0fa45f6ce82970685d94b539f18358d0681
Distribution
e959535ca70a71bf853d59d3c7068f525615093c e959535ca70a71bf853d59d3c7068f525615093c
Total tests
58
Fixed in
#601 (Manual run by Darius Jazayeri)

Tests

Responsible

  • djazayeri djazayeri Automatically assigned

Code commits

Git
Author Commit Message Commit date
Darius Jazayeri <jazayeri@alum.mit.edu> Darius Jazayeri <jazayeri@alum.mit.edu> 23d3a0fa45f6ce82970685d94b539f18358d0681 23d3a0fa45f6ce82970685d94b539f18358d0681 ER-122 - Let the tablet app use the login info from the laptop app app (avoiding a case where you are asked to log in unnecessarily)

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 1
Status Test View job Duration
Collapse Failed EbolaLoginControllerTest shouldReturnUnknownProviderForAuthenticatedUserWithInvalidProviderId History
Build Module < 1 sec 
junit.framework.AssertionFailedError: Expected: <null> but was: {uuid=6adb7c42-cfd2-4301-b53b-ff17c5654ff7, display=Person(personId=1), voided=false, links=[ All Data resources need to define their representations ]}
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.assertTrue(Assert.java:22)
	at junit.framework.Assert.assertNull(Assert.java:277)
	at junit.framework.Assert.assertNull(Assert.java:268)
	at junit.framework.TestCase.assertNull(TestCase.java:438)
	at org.openmrs.module.ebolaexample.rest.controller.EbolaLoginControllerTest.shouldReturnUnknownProviderForAuthenticatedUserWithInvalidProviderId(EbolaLoginControllerTest.java:138)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(36 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeER-122Could not obtain issue details from Jira