Build result summary

Details

Revision: fcae7dd3df36dc30d0ffed131663f4f4f8de9edc fcae7dd3df36dc30d0ffed131663f4f4f8de9edc
Total tests: 3356
Successful since: #1018 (2 weeks before)

	Commit	Message	Commit date
Wyclif Luyima	fcae7dd3df36dc30d0ffed131663f4f4f8de9edc fcae7dd3df36dc30d0ffed131663f4f4f8de9edc	Merge pull request #1851 from preethi29/TRUNK-4955 Obs.setObsDateTime makes obs dirty even when date is not changed, since one date is of java.sql.timestamp type - TRUNK-4955	10 Oct 2016
Daniel Kayiwa	cc3b5a7aedb57bced3c98e62bedee789a5334f87 cc3b5a7aedb57bced3c98e62bedee789a5334f87	Merge pull request #1853 from teleivo/TRUNK-1916 TRUNK-1916 Add coveralls.io badge to readme	10 Oct 2016
teleivo <mrteleivo@gmail.com>	33f939fed74f68a37c8628a051250c4acc89af61 33f939fed74f68a37c8628a051250c4acc89af61	TRUNK-1916 Add coveralls.io badge to readme Add coveralls.io badge to readme to show current coverage	10 Oct 2016
Preethi <preethi.ms34@gmail.com>	ae677ec09e1e5a5b8622a00097405641ef7cccd7 m ae677ec09e1e5a5b8622a00097405641ef7cccd7	TRUNK-4955 \| Obs not made dirty when obsdatetime is set with same value but compared against timestamp instance	08 Oct 2016

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