Build: #259 failed Changes by Daniel Kayiwa
Build result summary
Details
- Completed
- Queue duration
- 1 second
- Duration
- 6 minutes
- Labels
- None
- Revisions
-
- Git
-
639b029ee4788c74f3e5e47d9beacacf78f8cbab
639b029ee4788c74f3e5e47d9beacacf78f8cbab - Release scripts
-
bb61e06483cd415a55b72cceac8d10ad00ee4e8a
bb61e06483cd415a55b72cceac8d10ad00ee4e8a
- Total tests
- 2250
- Failing since
- #257 (Changes by 6 people – )
- Fixed in
- #264 (Changes by dkayiwa <kayiwadaniel@gmail.com>)
Tests
- 0 New failures
- 1 Existing failures
- 0 Fixed
- 26 Quarantined / skipped
Responsible
- Cintia Del Rio Automatically assigned
- Cosmin Ioan Automatically assigned
- djazayeri Automatically assigned
- Daniel Kayiwa Automatically assigned
- Rafal Korytkowski Automatically assigned
Code commits
Author | Commit | Commit date | |
---|---|---|---|
Daniel Kayiwa |
639b029ee4788c74f3e5e47d9beacacf78f8cbab
|
||
Cosmin Ioan <cioan@pih.org> |
6cadc8f9152cca510a8ba23652c5098f24414653
m |
Configuration changes
Plan configuration has changed since the last successful build. See the plan audit log for more details.
Tests
Status | Test | Failing since | View job | Duration | |
---|---|---|---|---|---|
HL7UtilTest
getTimeZoneOffset_shouldReturnTimezoneForGivenDateAndNotTheCurrentDate
|
Failing since build #257 (Changes by 6 people) | Default Job | < 1 sec | ||
org.junit.ComparisonFailure: expected:<[-05]00> but was:<[+00]00> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.openmrs.hl7.HL7UtilTest.getTimeZoneOffset_shouldReturnTimezoneForGivenDateAndNotTheCurrentDate(HL7UtilTest.java:67) 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) (23 more lines...) |
Jira issues
Issue | Description | Status | |
---|---|---|---|
Unknown Issue Type | TRUNK-3274 | Could not obtain issue details from Jira |