OpenMRS Core Master

Stages & jobs

  1. Build and Test

Build result summary

Details

Completed
Queue duration
3 seconds
Duration
6 minutes
Labels
None
Revisions
openmrs-core
57028746b5818c4abdb24873c6d1c4e8e5c20d79 57028746b5818c4abdb24873c6d1c4e8e5c20d79
openmrs-standalone
3a6621ab7bdfa16b1fd679e5aace21fb8d6dd698 3a6621ab7bdfa16b1fd679e5aace21fb8d6dd698
Total tests
2958
Fixed in
#641 (Changes by Daniel Kayiwa and Jakub Kondrat <jkondrat@soldevelo.com>)

Tests

Responsible

Code commits

openmrs-core
Author Commit Message Commit date
Daniel Kayiwa Daniel Kayiwa 57028746b5818c4abdb24873c6d1c4e8e5c20d79 57028746b5818c4abdb24873c6d1c4e8e5c20d79 Merge pull request #1104 from jbuczynski/TRUNK-3474
TRUNK-3474 Remove not null constraint on the description column/property...
jbuczynski <jbuczynski@soldevelo.com> jbuczynski <jbuczynski@soldevelo.com> 621db4505c37cb9e5f824a16c2bd4aad6b90844b 621db4505c37cb9e5f824a16c2bd4aad6b90844b Remove not null constraint on the description column/property for all OpenmrsMetadata objects

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 SchedulerServiceTest shouldSaveLastExecutionTime History
Build and Test 21 secs
java.lang.AssertionError: lastExecutionTime is null, so the SchedulerService didn't save it
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertNotNull(Assert.java:621)
	at org.openmrs.scheduler.SchedulerServiceTest.shouldSaveLastExecutionTime(SchedulerServiceTest.java:404)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
(32 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeTRUNK-3474Could not obtain issue details from Jira