Closed jbescos closed 6 months ago
@jbescos If we "fix" a TCK test, we also need to exclude the test until the next release. Fixing a test may cause another implementation that is already "certified" to fail for some reason, so we need to delay its execution. So you need to provide the exclusion as well.
@alwin-joseph can explain this better.
Thanks for checking it @spericas. What is the proper way to exclude it, with @Disabled
?
Yes @jbescos We use @Disabled
to exclude the test once the corresponding TCK challenge for the specific version is accepted.
So, since the test in latest TCK 3.1.4 is challenged here via https://github.com/jakartaee/rest/issues/1196, once the challenge is accepted we can exclude the same in branch release-3.1.x
, for eg: https://github.com/jakartaee/rest/pull/1181.
This PR for fixing the test can exist in master branch as it will be in effect for next release(4.0).
Thank you @alwin-joseph . It is disabled now for branch release-3.1.x https://github.com/jakartaee/rest/pull/1198
Issue closed
Relates to https://github.com/jakartaee/rest/issues/1196
It also increased the frequency that events are sent back. I had a problem in Helidon that it took longer than the test expects to be aware of the closed stream.
This is the stacktrace when the exception is thrown: