Build: #1572 failed

Job: Build and Test failed

Stages & jobs

  1. Build and Test

  2. Deploy

  3. Release

    Requires a user to start manually

Job result summary

Completed
Duration
21 minutes
Revision
97c176be614acdb843e8906c6f97615d37735fcd 97c176be614acdb843e8906c6f97615d37735fcd
Total tests
3482
Fixed in
#1573 (Code changes detected)

Tests

  • 3,482 tests in total
  • 1 test failed
  • 1 failure is new
  • 37 tests were quarantined / skipped
  • 15 minutes taken in total.
New test failures 1
Status Test Duration
Collapse Failed OrderServiceTest getNewOrderNumber_shouldAlwaysReturnUniqueOrderNumbersWhenCalledMultipleTimesWithoutSavingOrders History
1 sec
java.lang.AssertionError: expected:<50> but was:<49>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:743)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:555)
	at org.junit.Assert.assertEquals(Assert.java:542)
	at org.openmrs.api.OrderServiceTest.getNewOrderNumber_shouldAlwaysReturnUniqueOrderNumbersWhenCalledMultipleTimesWithoutSavingOrders(OrderServiceTest.java:256)

Error summary

The build generated some errors. See the full build log for more details.

INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/5/17 1:18 AM:liquibase: Successfully acquired change log lock
INFO 4/5/17 1:18 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/5/17 1:18 AM:liquibase: Successfully released change log lock
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
INFO 4/5/17 1:19 AM:liquibase: Reading from LIQUIBASECHANGELOG
[Field error in object 'term' on field 'conceptReferenceTermMaps[1].termB': rejected value [weight term(WGT234)]; codes [ConceptReferenceTerm.termToTerm.alreadyMapped.term.conceptReferenceTermMaps[1].termB,ConceptReferenceTerm.termToTerm.alreadyMapped.term.conceptReferenceTermMaps.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.conceptReferenceTermMaps[1].termB,ConceptReferenceTerm.termToTerm.alreadyMapped.conceptReferenceTermMaps.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.org.openmrs.ConceptReferenceTerm,ConceptReferenceTerm.termToTerm.alreadyMapped]; arguments []; default message [Cannot map a reference term multiple times to the same concept reference term]]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.