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
Added jtreg-buffer testsuite #5308
base: master
Are you sure you want to change the base?
Conversation
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.
Need to understand why :-)
Co-authored-by: Martijn Verburg <martijnverburg@gmail.com>
Yah. That it honest question, and not easy one indeed! Various reasons, from dummy ones like: Original author quit, original author forget, original author was lazy or simply not brave enough to push it. And later, no one had time to take it over. Not exactly an good excuse, but is covering about half of the tests. I would silently nod in agreeing to anybody refusing to accept this test set for this reason. But I tried to do quite a few in past, and burned out on it. Other reasons are weird corner cases, which do not run everywhere. Most of them are currenly labeled as |
I had recalled, that I was tracking the upstreaming. Its part of the repo, you can see it via githubhack: https://rawcdn.githack.com/rh-openjdk/jtreg-buffer/581161a13dd731f9eac1f89e5164884a77465bca/dupes.html the |
based on:
#5195
#5167