You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by cd...@apache.org on 2020/01/22 16:32:57 UTC

[plc4x] branch develop updated: - Updated the list of tests that seem to be occasionally a little flaky and causing the build to be marked unstable

This is an automated email from the ASF dual-hosted git repository.

cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git


The following commit(s) were added to refs/heads/develop by this push:
     new d967e9f  - Updated the list of tests that seem to be occasionally a little flaky and causing the build to be marked unstable
d967e9f is described below

commit d967e9f16931c71a800aad84cfca3e8f9bf08699
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Wed Jan 22 17:32:51 2020 +0100

    - Updated the list of tests that seem to be occasionally a little flaky and causing the build to be marked unstable
---
 Sometimes-Failling-Tests.md | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/Sometimes-Failling-Tests.md b/Sometimes-Failling-Tests.md
index 818bfa3..3544668 100644
--- a/Sometimes-Failling-Tests.md
+++ b/Sometimes-Failling-Tests.md
@@ -22,11 +22,6 @@
 This File contains the names and outputs of some tests that have been seen to fail without direct code-changes.
 It's sort of a collection of places we should keep an eye out for improving tests-
 
-## Module: plc4l-opm
-
-[ERROR]   ConnectedEntityTest.useCache_timeout_refetches:83
-mockDevice.read(<any>);
-Wanted 2 times:
--> at org.apache.plc4x.java.opm.ConnectedEntityTest.useCache_timeout_refetches(ConnectedEntityTest.java:83)
-But was 1 time:
--> at org.apache.plc4x.java.mock.PlcMockConnection.lambda$null$0(PlcMockConnection.java:111)
+## Module: plc4j-spi
+
+RequestTransactionManagerTest.abortTransactionFromExternally
\ No newline at end of file