-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Flaky-Test]: A test in the java OPC-UA driver is continuously breaking builds. #1764
Comments
I'll take a look on these and the end of week or early next. I hoped that testcontainers would help us a bit with this issue, but there still seem to be a problem. |
Admittedly I think the issue lies with milo and it therefore doesn't really matter how you start it ... but admittedly I didn't look too deep into the issue. |
org.apache.plc4x.java.opcua.protocol.chunk.ChunkFactoryTest also seems to continuously break builds (all values seem to be off by 1) |
Related to #1764. Signed-off-by: Łukasz Dywicki <[email protected]>
Related to #1764. Signed-off-by: Łukasz Dywicki <[email protected]>
Related to #1764. Signed-off-by: Łukasz Dywicki <[email protected]>
Related to #1764. Signed-off-by: Łukasz Dywicki <[email protected]>
Related to #1764. Signed-off-by: Łukasz Dywicki <[email protected]>
First and foremost - this commit switches OPC-UA tests to rely on dynamic port. This implies also slight change to endpoint selection method and possibility to override desired endpoint port and host which might differ from host/port reported by OPC-UA server. Because server is not aware of actual tcp port and host used by client, it is client duty to make proper decission when looking for endpoint. Related to #1764. Signed-off-by: Łukasz Dywicki <[email protected]>
For now I've changed assertion in Lets keep this issue open to track this test and others, if they keep failing randomly. |
What happened?
The test OpcuaPlcDriverTest.multipleThreads in the java opc-ua driver testsuite is regularly failing the CI/CD builds ... re-runing them usually resolves the issue, however we can't have test break the builds at random.
Version
v0.13.0-SNAPSHOT
Programming Languages
Protocols
The text was updated successfully, but these errors were encountered: