Skip to navigation
Skip to content

Stages & jobs

Build and Test
- Build and Test
- Integration Test
Deploy
- Deploy
Release
Requires a user to start manually
- Release to maven

Build result summary

Details

Completed: 19 Jul 2020, 6:15:36 AM – 3 years ago
Queue duration: < 1 second
Duration: 17 minutes
Labels: None

Revisions

openmrs-core: 7481583d88a189d795cae83767536f9caec26cbd 7481583d88a189d795cae83767536f9caec26cbd
openmrs-standalone: 8af748fdb6fe93f74ebb4b89e03b262fcd37b5c0 8af748fdb6fe93f74ebb4b89e03b262fcd37b5c0
Release scripts: 1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370

Total tests

4411

Successful since

#2343 (1 day before)

Tests

0 New failures
0 Existing failures
0 Fixed
41 Quarantined / skipped

Code commits

openmrs-core
Author		Commit	Message	Commit date
	teleivo <teleivo@users.noreply.github.com>	7481583d88a189d795cae83767536f9caec26cbd 7481583d88a189d795cae83767536f9caec26cbd	TRUNK-5816 Run StartModuleAnnotationTest tests in folder test are not run. Not sure when this test was ever run. See surefire exclusions for why. We cannot run a BaseContextSensitive with a BaseModuleContextSensitive test in the same package. You can run it in isolation but as soon as you add another test extending the other base class you get [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.921 s <<< FAILURE! - in org.openmrs.annotation.StartModuleAnnotationTest [ERROR] shouldStartModules Time elapsed: 0.003 s <<< ERROR! java.lang.IllegalStateException: Failed to load ApplicationContext ... Caused by: org.hibernate.cache.CacheException: net.sf.ehcache.CacheException: Another CacheManager with same name 'hibernateCache' already exists in the same VM. Please provide unique names for each CacheManager in the config or do one of following: 1. Use one of the CacheManager.create() static factory methods to reuse same CacheManager with same name or create one if necessary 2. Shutdown the earlier cacheManager before creating new one with same name. The source of the existing CacheManager is: DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ] Caused by: net.sf.ehcache.CacheException: Another CacheManager with same name 'hibernateCache' already exists in the same VM. Please provide unique names for each CacheManager in the config or do one of following: 1. Use one of the CacheManager.create() static factory methods to reuse same CacheManager with same name or create one if necessary 2. Shutdown the earlier cacheManager before creating new one with same name. The source of the existing CacheManager is: DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ] Both will want to create an applicationContext with most likely a lot of the same beans. The cause here is the duplicate ehCache with the same name	19 Jul 2020

Configuration changes

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

Manual stage Release cannot be run as it references jobs that no longer exist.

Jira issues

Issue		Description	Status
Unknown Issue Type	TRUNK-5816	Could not obtain issue details from Jira