-
Notifications
You must be signed in to change notification settings - Fork 4
Abhishek/seed fail test java #289
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
base: main
Are you sure you want to change the base?
Conversation
- Updated package imports from oteltef to otelstef after main branch merge - Verified seed-based regression testing implementation matches PR #263 - All tests pass successfully - 3 Java-specific seeds loaded and tested correctly
Benchmark ResultBenchmark diff with base branchBenchmark result |
| class ReadWriteTest { | ||
| @Test | ||
| public void testCopy() throws IOException { | ||
| private boolean testCopySeed(long seed) throws IOException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is the seed used in this test? I can't find any usage?
I don't think we need it here. We want seed saving and load tests generated via writerTest.java.tmpl. This should be equivalent of what we do for Go in this PR: https://github.com/splunk/stef/pull/263/files#diff-6cea806d1350c5a7621b9e3b780184637490a125dbc98f0296224c0fdf2e7eeb
Once writerTest.java.tmpl is modified, you can run make all in various directories (e.g. in go/otel and stef) to generate Java code and then run ./gradlew test to see how the tests work.
When you are happy with writerTest.java.tmpl, running make all in root directory will help confirm everything works correctly.
|
Nit: please use more descriptive commit message, PR title and description. Feel free to borrow from #263 which does similar things for Go. |
No description provided.