Skip to content
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

Verify behavior and initialization of KNetSerialization class #531

Closed
masesdevelopers opened this issue Jul 2, 2024 · 0 comments · Fixed by #534
Closed

Verify behavior and initialization of KNetSerialization class #531

masesdevelopers opened this issue Jul 2, 2024 · 0 comments · Fixed by #534
Assignees
Labels
bug Something isn't working KNet KNet related issue KNetSerDes KNetSerDes related issue

Comments

@masesdevelopers
Copy link
Contributor

masesdevelopers commented Jul 2, 2024

Some tests fails for other reason than the previous: specifically under windows and with JDK 17. Looking at the available dumps, sometime there is an access violation during preparation of the KNetSerialization class. However, trying to reproduce the issue locally, the exception is not raised; between GitHub and local test the differences are:

  • OS: Windows Server for GitHub, Windows Desktop in local
  • JDK: locally tested only with a Temurin JDK 17
  • .NET 6/8: both at latest version

It is possible to highlight that KNetReplicator never raises such exception and the exception is not raised from the same test even if the order of execution is always the same.

Originally posted by @masesdevelopers in masesgroup/KEFCore#243 (comment)

@masesdevelopers masesdevelopers self-assigned this Jul 2, 2024
@masesdevelopers masesdevelopers added bug Something isn't working KNetSerDes KNetSerDes related issue KNet KNet related issue labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working KNet KNet related issue KNetSerDes KNetSerDes related issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant