ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Pavlov <dpavlov....@gmail.com>
Subject Re: .NET suite failures
Date Tue, 27 Feb 2018 17:23:30 GMT
Hi Pavel, yes, you're right. All tests passed.

I thought it was because of 'IGNITE-7329 .NET: Thin client: SSL connection
implemented' and did not look in the log

вт, 27 февр. 2018 г. в 19:22, Pavel Tupitsyn <ptupitsyn@apache.org>:

> Hi Dmitry,
>
> Thanks for bringing this up.
> Please see the build log, it indicates failed Java build:
>
> Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (default) on project ignite-storm: Error resolving project artifact: Could
> not transfer artifact ring-cors:ring-cors:pom:0.1.5 from/to central (
> http://repo.maven.apache.org/maven2): repo.maven.apache.org for project
> ring-cors:ring-cors:jar:0.1.5: Unknown host repo.maven.apache.org -> [Help
> 1]
>
> Looks like a Maven connection issue to me, let's wait for the next build.
>
> Pavel
>
> On Tue, Feb 27, 2018 at 7:13 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> wrote:
>
> > Hi Pavel, Igniters,
> >
> > .NET test failed after recent changes
> >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_
> > IgnitePlatformNet&branch_IgniteTests24Java8=%3Cdefault%
> > 3E&tab=buildTypeStatusDiv
> >
> > Failed suites are following:
> >    Ignite Platform .NET [ tests 0 TC_EXIT_CODE ]
> >    Ignite Platform .NET Long Running [ tests 0 TC_EXIT_CODE ]
> >
> > Is it related to recent commits to .NET ?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message