Build: #29 failed

Job: Default Job failed

Stages & jobs

  1. Default Stage

Should fail if the entity has an item in the error queue with an invalid destination: Test case result

The below summarizes the result of the test "Should fail if the entity has an item in the error queue with an invalid destination" in build 29 of openmrs-eip - openmrs-eip - Default Job. View test case history
Description
Should fail if the entity has an item in the error queue with an invalid destination
Test class
org.openmrs.eip.mysql.watcher.route.DbEventListenerRouteTest
Method
shouldFailIfTheEntityHasAnItemInTheErrorQueueWithAnInvalidDestination
Duration
< 1 sec
Status
Failed (Existing Failure)

Error Log

org.springframework.jdbc.datasource.init.ScriptStatementFailedException: Failed to execute SQL script statement #1 of class path resource [sender_retry_queue.sql]: INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00'); nested exception is org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "SENDER_RETRY_QUEUE" not found; SQL statement:
INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00') [42102-200]
org.springframework.jdbc.datasource.init.ScriptStatementFailedException: 
Failed to execute SQL script statement #1 of class path resource [sender_retry_queue.sql]: INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00'); nested exception is org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "SENDER_RETRY_QUEUE" not found; SQL statement:
INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00') [42102-200]
Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 
Table "SENDER_RETRY_QUEUE" not found; SQL statement:
INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00') [42102-200]