ServiceVdbGeneratorTest::shouldRefreshServiceVdb_SingleSource is flaky
See original GitHub issueThis is a…
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Documentation issue or request
Description
I see this ServiceVdbGeneratorTest::shouldRefreshServiceVdb_SingleSource
test fail occasionally on downstream CI.
[ERROR] shouldRefreshServiceVdb_SingleSource(io.syndesis.dv.server.endpoint.ServiceVdbGeneratorTest) Time elapsed: 0.031 s <<< FAILURE!
org.junit.ComparisonFailure:
expected:<...type="DDL"><![CDATA[[SET NAMESPACE 'http://www.teiid.org/ext/relational/2012' AS teiid_rel;
]CREATE FOREIGN TABLE...> but was:<...type="DDL"><![CDATA[[]CREATE FOREIGN TABLE...>
at io.syndesis.dv.server.endpoint.ServiceVdbGeneratorTest.shouldRefreshServiceVdb_SingleSource(ServiceVdbGeneratorTest.java:406)
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to Fix Flaky Tests - Semaphore CI
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The issue here is a mixing of Teiid versions. This should be happening on the product branch due to a change in Teiid 13. We’ll be rolling Teiid 13 into the upstream today with https://issues.redhat.com/browse/TEIIDTOOLS-891 which will update this test result as well.
Marking as closed. Master and 1.9.x are now aligned with Teiid versions.