Re: buildbot failure in on wicket-master

Hi, Please see https://issues.apache.org/jira/browse/INFRA-21065 On Mon, Nov 2, 2020 at 2:39 PM wrote: > The Buildbot has detected a new failure on builder wicket-master while > building wicket. Full details are available at: > https://ci.apache.org/builders/wicket-master/builds/1389 > >

Re: buildbot failure in on wicket-master

This should be some temporary network issues (failing test trying to connect URL url = new URL(" http://wicket.apache.org/learn/books/wia.png;); ) On Tue, 11 Feb 2020 at 04:40, Emond Papegaaij wrote: > I don't what happened here, but I'm pretty sure that I didn't break > this with a simple

Re: buildbot failure in on wicket-master

I don't what happened here, but I'm pretty sure that I didn't break this with a simple CSS change. The test runs fine on my machine. Did something change in the infra? Emond On Mon, Feb 10, 2020 at 9:46 PM wrote: > > The Buildbot has detected a new failure on builder wicket-master while >

Re: buildbot failure in on wicket-master-java12

I will remove the java12 build On Thu, Jan 9, 2020 at 12:34 PM Tobias Soloschenko wrote: > +1 to remove JDK 12 testing > > kind regards > > Tobias > > > Am 09.01.2020 um 09:52 schrieb Maxim Solodovnik : > > > > I would vote for removing JDK12 > > no need to test outdated non-LTS versions IMO >

Re: buildbot failure in on wicket-master-java12

+1 to remove JDK 12 testing kind regards Tobias > Am 09.01.2020 um 09:52 schrieb Maxim Solodovnik : > > I would vote for removing JDK12 > no need to test outdated non-LTS versions IMO > >> On Thu, 9 Jan 2020 at 15:06, Martin Grigorov wrote: >> >> Hi team, >> >> The build for Java 12 has

Re: buildbot failure in on wicket-master-java12

I would vote for removing JDK12 no need to test outdated non-LTS versions IMO On Thu, 9 Jan 2020 at 15:06, Martin Grigorov wrote: > Hi team, > > The build for Java 12 has failed due to the removal of the multiple test > methods for the different versions of JDK for >

Re: buildbot failure in on wicket-master-java13

I've created https://issues.apache.org/jira/browse/INFRA-18867 to upgrade Java 13 and 14 at Buildbot slaves. On Mon, Aug 12, 2019 at 2:19 PM wrote: > The Buildbot has detected a new failure on builder wicket-master-java13 > while building wicket. Full details are available at: >

Re: buildbot failure in on wicket-master-java13

https://issues.apache.org/jira/browse/INFRA-18609 On Thu, Jun 13, 2019 at 4:43 PM wrote: > The Buildbot has detected a new failure on builder wicket-master-java13 > while building wicket. Full details are available at: > https://ci.apache.org/builders/wicket-master-java13/builds/85 > >

Re: buildbot failure in on wicket-master

I think there's a problem with buildbot. I will open an issue for the INFRA team. Thank you for removing references to datetime module. I also agree that specific websocket implementation should be removed from master. Andrea. On Tue, May 22, 2018 at 9:59 AM, Emond Papegaaij

Re: buildbot failure in on wicket-master

This error still persists and I have no idea why. Locally the build is fine. I've removed some more references to the old datetime module, including the NOTICE about the bsd license. The userguide still mentions the tomcat and jetty9 modules for native-websockets. I think that part should be

Re: buildbot failure in on wicket-master

-0 for #chained(), this isn't even a verb (I know, 'of' isn't a verb either) Regards Sven On 17.11.2016 12:22, Martin Grigorov wrote: On Thu, Nov 17, 2016 at 12:13 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: We could also opt to rename map(...) to to(...)

Re: buildbot failure in on wicket-master

On Thu, Nov 17, 2016 at 12:13 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > We could also opt to rename map(...) to to(...) > > Model.of(account).to(Account::getPerson).to(Person:: > getLastName).to(String::toUppercase) > #map() is more widely used in JVM langs > > Martijn > > >

Re: buildbot failure in on wicket-master

We could also opt to rename map(...) to to(...) Model.of(account).to(Account::getPerson).to(Person::getLastName).to(String::toUppercase) Martijn On Thu, Nov 17, 2016 at 11:09 AM, Emond Papegaaij wrote: > I also think 'chained' better covers the intent. 'map'

Re: buildbot failure in on wicket-master

I also think 'chained' better covers the intent. 'map' normally isn't a read/write transformation. Emond On Thu, Nov 17, 2016 at 12:38 AM, Martin Grigorov wrote: > +1 for #chained() . > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > >

Re: buildbot failure in on wicket-master

+1 for #chained() . Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Nov 15, 2016 at 10:07 PM, Sven Meier wrote: > Hi, > > >We could rename the methods taking an IModel as first parameter to > >"chained" or "from". > > or "map": > >

Re: buildbot failure in on wicket-master

Hi, >We could rename the methods taking an IModel as first parameter to >"chained" or "from". or "map": LambdaModel.map(IModel, SerializableFunction, SerializableBiConsumer) LambdaModel.map(IModel, SerializableFunction) Sven Am 15.11.2016 um 20:52 schrieb Emond Papegaaij:

Re: buildbot failure in on wicket-master

IModel.map(Function) indeed is functionally equivalent to LambdaModel.of(IModel, Function), but its memory footprint is significantly larger (120 vs 80 bytes). Also, there's no equivalent method for of(IModel, Function, BiConsumer). Naturally, we can add the corresponding method, but it will

Re: buildbot failure in on wicket-master

On Tue, Nov 15, 2016 at 2:51 PM, Emond Papegaaij wrote: > It seems I've hit a bug in javac: > LambdaModelTest[46,61] reference to of is ambiguous: >of(SerializableSupplier, SerializableConsumer) > of(IModel, SerializableFunction) > > This

Re: buildbot failure in on wicket-master

It seems I've hit a bug in javac: LambdaModelTest[46,61] reference to of is ambiguous: of(SerializableSupplier, SerializableConsumer) of(IModel, SerializableFunction) This clearly is wrong: IModel personNameModel = LambdaModel.of( () -> person.getName(), (name)

Re: buildbot failure in on wicket-master

This has been fixed. There is a new problem now: https://issues.apache.org/jira/browse/INFRA-12877 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Nov 8, 2016 at 11:15 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > Ah Thanks! > > I looked into

Re: buildbot failure in on wicket-master

Ah Thanks! I looked into the log, but didn't find anything I could fix. Martijn On Tue, Nov 8, 2016 at 10:58 PM, Martin Grigorov wrote: > https://issues.apache.org/jira/browse/INFRA-12875 > > Martin Grigorov > Wicket Training and Consulting >