[
https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5425.
-----------------------------------
Resolution: Done
Looking into this more, the issue is cross talk on jgroups with the tests. Because we are
using the same vdb/version in the tests we are seeing lingering state from testNodeFailure
- where the second server is not shutdown and is still using the status table. We
don't have a built-in mechanism to fully address that, so for now I'll just update
the test.
Concurrency/timing issues observed with travis builds
-----------------------------------------------------
Key: TEIID-5425
URL:
https://issues.jboss.org/browse/TEIID-5425
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.1
Several unit tests have been observed to fail during travis builds occasionally:
1. TestODBCSocketTransport.testRegClass:757 » PSQL ResultSet not positioned prope...
2. TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see
https://api.travis-ci.org/v3/job/405801976/log.txt)
3. [ERROR] TestLocalConnections.testWaitForLoadTimeout:475
4. From
https://api.travis-ci.org/v3/job/415138409/log.txt
[ERROR] testReplication(org.teiid.systemmodel.TestReplication) Time elapsed: 35.21 s
<<< FAILURE!
java.lang.AssertionError: expected:<0.9164140964242746> but
was:<0.18750528722359294>
at org.teiid.systemmodel.TestReplication.testReplication(TestReplication.java:122)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)