> I think we need a different approach, IMO: We only want to allow the > Pack200 tests to fail on Java >= 14. For that, please create a Maven > profile in the POM that excludes those tests on JAva >= 14. This will allow > all us to detect problem in all the other tests. >
+1 I have pushed a PR on github about this: https://github.com/apache/commons-compress/pull/129 (https://link.getmailspring.com/link/9b33ba1b-4173-4682-9dd3-a630a6e08...@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fapache%2Fcommons-compress%2Fpull%2F129&recipient=ZGV2QGNvbW1vbnMuYXBhY2hlLm9yZw%3D%3D) cheers, Lee On 8 21 2020, at 10:18 , Gary Gregory <garydgreg...@gmail.com> wrote: > On Thu, Aug 20, 2020 at 7:57 AM Peter Lee <peter...@apache.org> wrote: > > > Hi all, > > > > The builds in jenkins and github actions are failing. > > For jenkins, the java7, 14 and 16 builds are failing. As we have moved > > from JAVA 7 to 8, maybe we should disable java 7 build in jenkins? Besides > > the java 14 and 16 are also failing, and we can have some "allow failure" > > config on them. > > For github actions, the java 14 and 15 builds are failing. We can easily > > make java 14 build a part of experimental build to have it > > continue-on-error. > > What do you think? > > > > I think we need a different approach, IMO: We only want to allow the > Pack200 tests to fail on Java >= 14. For that, please create a Maven > profile in the POM that excludes those tests on JAva >= 14. This will allow > all us to detect problem in all the other tests. > > Thoughts? > Gary > > > cheers, > > Lee > > >
