-
Notifications
You must be signed in to change notification settings - Fork 88
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
InitiateKeyEstablishmentRequestCommandSuccess(com.zsmartsystems.zigbee.app.seclient.ZclKeyEstablishmentServerTest) is unstable #1357
Comments
I've just run this 30 times and it's not failed. Please can you at least provide some logs showing what the problem is. |
[INFO] Scanning for projects... T E S T SRunning com.zsmartsystems.zigbee.app.basic.ZigBeeBasicServerExtensionTest |
@cdjackson here you see the logging from |
Thanks. I don't think I've ever seen this fail here and this code has been included in the library for a few years. It also hasn't ever failed with CI which runs on every PR and merge etc... |
It's also strange that the output from the error looks invalid -:
This can't be right since the line that reports to have a problem is this -:
This shows that it is expected to be If I change this test so it will fail, you can see it prints out the expected and actual values -:
I've run just this test class loads more times and can't make it fail (other than if I change the expected result as above ;) ). I wonder if there's something else going on with your environment given it seems to print invalid information. Maybe you can take a look at this if you get a chance? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
InitiateKeyEstablishmentRequestCommandSuccess(com.zsmartsystems.zigbee.app.seclient.ZclKeyEstablishmentServerTest) is failing sometimes.
To Reproduce
mvn clean install (until the test fails)
Expected behavior
All tests pass each time
Additional context
I have not analyzed the issue
The text was updated successfully, but these errors were encountered: