My mistake; the problems in master appear to be related to test failures of some sort. I'll see if migrating those tests to JUnit 5 (along with any related refactorings) helps make them less flakey.
On Sat, 22 Aug 2020 at 21:04, Matt Sicker <boa...@gmail.com> wrote: > > Ok, so whatever the issue is is a problem in both branches now. > > On Fri, 21 Aug 2020 at 09:56, Matt Sicker <boa...@gmail.com> wrote: > > > > I’ve been modifying build settings in master lately that haven’t been > > merged back to this branch. I’d assume there’s a difference in the pom file > > here. I’ll take a closer look later today. > > > > On Fri, Aug 21, 2020 at 04:31 Volkan Yazıcı <volkan.yaz...@gmail.com> wrote: > >> > >> GitHub Actions CI build is failing on release-2.x > >> > >> <https://github.com/apache/logging-log4j2/runs/1008091524> with the > >> > >> following error: > >> > >> > >> > >> [ERROR] Failed to execute goal > >> > >> org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on > >> > >> project log4j-api-java9: Misconfigured toolchains. Non-existing JDK home > >> > >> configuration at > >> > >> /Users/runner/work/logging-log4j2/logging-log4j2/${env.JAVA_HOME_8_X64} -> > >> > >> [Help 1] > >> > >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > >> > >> goal org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain > >> > >> (default) on project log4j-api-java9: Misconfigured toolchains. > >> > >> > >> > >> I am confused and clueless, since the very same [GitHub Actions] > >> > >> configuration works perfectly well on "master". Any ideas? Matt? > >> > > -- > > Matt Sicker <boa...@gmail.com> > > > > -- > Matt Sicker <boa...@gmail.com> -- Matt Sicker <boa...@gmail.com>