Same here. Ubuntu 18.04 openjdk version "11.0.4" 2019-07-16 (from adoptopenjdk repository)
On Mon, Aug 19, 2019 at 10:19 AM Maxim Solodovnik <[email protected]> wrote: > `mvn clean install` is green for me > > Ubuntu 19.04 > openjdk version "11.0.4" 2019-07-16 > > On Mon, 19 Aug 2019 at 15:01, Martin Grigorov <[email protected]> > wrote: > > > I've updated from 11.0.2 to 11.0.4 > > > > openjdk 11.0.4 2019-07-16 > > OpenJDK Runtime Environment (build 11.0.4+11-post-Ubuntu-1ubuntu219.04) > > OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Ubuntu-1ubuntu219.04, > mixed > > mode, sharing) > > > > but the build passes locally. > > > > GitHub Actions log says: > > > > Run actions/setup-java@v1 > > 2 with: > > 3 java-version: 11 > > 4 architecture: x64 > > 5in/tar xzC /home/runner/work/_temp/temp_1292672611 -f > > /home/runner/work/_temp/5e1bda4a-1c91-40e3-8cae-061677d8110b > > 6##[set-env name=JAVA_HOME;]/opt/hostedtoolcache/Java/11.0.4/x64 > > 7##[set-env > name=JAVA_HOME_11.0.4_x64;]/opt/hostedtoolcache/Java/11.0.4/x64 > > 8##[add-path]/opt/hostedtoolcache/Java/11.0.4/x64/bin > > 9Added matchers: 'java' > > 10 > > > > > ##[add-matcher]/home/runner/work/_actions/actions/setup-java/v1/.github/java.json > > > > but the test fails: > > > > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: > > 0.053 s <<< FAILURE! - in > > org.apache.wicket.util.convert.converter.ZonedDateTimeConverterTest > > [ERROR] convertToObject_java12Minus Time elapsed: 0.027 s <<< FAILURE! > > org.opentest4j.AssertionFailedError: expected: > > <2016-07-11T01:02:03Z[Etc/UCT]> but was: <2016-07-11T01:02:03Z[Etc/UTC]> > > at > > > > > org.apache.wicket.util.convert.converter.ZonedDateTimeConverterTest.convertToObject_java12Minus(ZonedDateTimeConverterTest.java:50) > > > > On Mon, Aug 19, 2019 at 10:40 AM Martin Grigorov <[email protected]> > > wrote: > > > > > Hi, > > > > > > Yesterday evening I've tried the new GitHub Actions service. > > > The build failed because it seems the UCT -> UTC change has been ported > > to > > > Java 11, 11.0.4 specifically. > > > Buildbot is still green: https://ci.apache.org/builders/wicket-master, > > which > > > means that Apache Infra haven't updated Java 11 lately. > > > Last week I've created a ticket to update Java 13 and 14 but they > haven't > > > worked on it yet. https://issues.apache.org/jira/browse/INFRA-18867 > > (JIRA > > > is down at the moment, so I am not sure whether this is the correct > > ticket). > > > I will update my local Java 11 to a newer one and fix the failing test > > but > > > it seems everyone else in the team still uses old Java 11 build as me > > since > > > no one noticed so far. > > > > > > On Sun, Aug 18, 2019 at 9:44 PM Martin Grigorov < > > [email protected]> > > > wrote: > > > > > >> Run failed for master (59b85a1) > > >> > > >> Repository: apache/wicket > > >> Workflow: GitHub Actions > > >> Duration: 1 minute and 36.0 seconds > > >> Finished: 2019-08-18 18:44:33 UTC > > >> > > >> View results > > >> < > > > https://github.com/apache/wicket/commit/59b85a1fd8868edc543cdca9aad69e4238195fc1/checks > > > > > >> Jobs: > > >> > > >> - Build <https://github.com/apache/wicket/runs/196487121> failed > (0 > > >> annotations) > > >> > > >> — > > >> You are receiving this because this workflow ran on your branch. > > >> Manage your GitHub Actions notifications here > > >> <https://github.com/settings/notifications>. > > >> > > > > > > > > -- > WBR > Maxim aka solomax > -- Andrea Del Bene. Apache Wicket committer.
