You can imagine TCK as gigantic and pretty good testsuite, runing 24hours with quite complicated setup. The pull and setup and run is completely autoamted, but it is a lot of HW you need (all architecures x all oses x all jdks). In adition, you need human power to keep with TCK evolution, sometimes to dapt setup, and to check resutls if they fails... and.. to fix it. We have HW from Red hat, and we deal with failures we keep track with usptream and TCK evolution. But it is not easy from human resources point of view. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
