date:20170715

Re: [ignite] your /dist/ artifacts - 1 BAD signature

2017-07-15 Thread Aleksey Chetaev

Guys,
I removed test binaries. I hope Ilya S. can give more comments about this
issue on Monday.

Best Regards,
Aleksey Chetaev.



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-ignite-your-dist-artifacts-1-BAD-signature-tp19732p19741.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Ignite Teamcity email notifications

2017-07-15 Thread Denis Magda

Excellent improvement for our testing and continuous intergration
processes, thanks folks!

On Saturday, July 15, 2017, Dmitry Pavlov  wrote:

> Hi Igniters,
>
> Thanks to Alexey Chetaev we can now setup personal email notifications from
> the Teamcity about broken builds.
>
> To set up notifications you can go to your profile and enable email
> notification for your own PR and/or master (see the page
> http://ci.ignite.apache.org/profile.html?item=userNotifications)
>
> You can set branch filter for example as follows:
> +:ignite-2.*
> +:pull/2296/head
> And enable notifications on
> - build fails (only first failing and/or including your changes),
> - and successful build (optionally only first build after failed).
>
> Best Regards,
> Dmitriy Pavlov
>
> пн, 3 июл. 2017 г. в 17:43, Denis Magda 
> >:
>
> > Dmitriy P.,
> >
> > The list has been created. Here is a response from ASF:
> >
> > As requested by you, the following mailing list has been created:
> > c...@ignite.apache.org   >
> > Moderators: dma...@apache.org   dma...@apache.org >,
> > dsetrak...@apache.org   >
> > This list is private.
> >
> >
> >
> > ---
> >
> > The list will start accepting mail in 60 minutes from now.  If it's a
> > public
> > list, it will appear on https://lists.apache.org/ <
> > https://lists.apache.org/> within a few minutes of
> > the first post to it.
> >
> > —
> > Denis
> >
> > > On Jun 29, 2017, at 4:10 PM, Denis Magda  > wrote:
> > >
> > > Trigged the alias creation. Will let you know once it’s ready for
> usage.
> > >
> > > —
> > > Denis
> > >
> > >> On Jun 29, 2017, at 3:51 PM, Dmitriy Setrakyan  >
> > wrote:
> > >>
> > >> I like this alias.
> > >>
> > >> On Thu, Jun 29, 2017 at 3:43 PM, Denis Magda  > wrote:
> > >>
> > >>> What’s about c...@ignite.apache.org   c...@ignite.apache.org >? If
> > there
> > >>> are no objections I’ll create the alias.
> > >>>
> > >>> —
> > >>> Denis
> > >>>
> >  On Jun 29, 2017, at 11:53 AM, Dmitry Pavlov  >
> > >>> wrote:
> > 
> >  Hi Dmitriy,
> > 
> >  At the first step we need some email address to send notifications
> > from
> >  behalf of TeamCity. We need to set up SMTP server, username and
> > password.
> >  Later users may set up personal notification rules ( see the link
> >  http://ci.ignite.apache.org/profile.html?item=userNotifications).
> > 
> >  Teamcity takes into account last commits in branch and sends
> > >>> notifications
> >  separately and only to users which may break the build (option name
> > >>> 'builds
> >  containing my changes').
> > 
> >  Best Regards,
> >  Dmitriy Pavlov
> > 
> > 
> >  чт, 29 июн. 2017 г. в 21:21, Dmitriy Setrakyan <
> dsetrak...@apache.org 
> > >:
> > 
> > > Dmitry, I don't think ign...@apache.org  is a valid
> email address.
> > Why
> > > creating a mailing list for TC is not a good option?
> > >
> > > On Thu, Jun 29, 2017 at 8:17 AM, Dmitry Pavlov <
> > dpavlov@gmail.com >
> > > wrote:
> > >
> > >> Hi Igniters,
> > >>
> > >> I want to set up a email notifications from the public Teamcity
> > about
> > >> broken builds. But there is no configured address and email
> > account. To
> > > set
> > >> up notifications we need some mail box (account) to send messages
> > from.
> > >>
> > >> I asked the apache infrastructure team in
> > >> https://issues.apache.org/jira/browse/INFRA-14455
> > >> However, they recommended through PMC to create a mailing list. I
> > doubt
> > > it
> > >> can solve the problem.
> > >>
> > >> I also found out that there are e-mails from the address Ignite
> > >>> Teamcity
> > > <
> > >> ign...@apache.org >.
> > >>
> > >> Can we use it? Do we know the password for this account?
> > >> Any thought how to solve it?
> > >>
> > >> Best Regards,
> > >> Dmitriy Pavlov
> > >>
> > >
> > >>>
> > >>>
> > >
> >
> >
>

Re: [VOTE] Apache Ignite 2.1.0 RC1

2017-07-15 Thread Denis Magda

-1

Because of the lgpl libraries issue. Please fix the bug and restart the
vote.

Denis

On Saturday, July 15, 2017, Ilya Suntsov  wrote:

> Lgpl binaries should not to be in svn. This build will be removed.
>
> 15 июля 2017 г. 1:52 PM пользователь "Sergey Kozlov"  >
> написал:
>
> > Igniters
> >
> > Could someone explain why we include LGPL binary fabric [1] in the
> release?
> > Either it was a mistake or we should upload also SHA1/MD5/ASC checksums
> as
> > well
> >
> >
> > [1]
> > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
> > apache-ignite-fabric-lgpl-2.1.0-bin.zip
> >
> > On Fri, Jul 14, 2017 at 8:45 PM, Vladimir Ozerov  >
> > wrote:
> >
> > > gniters!
> > >
> > > We have uploaded a 2.1.0 release candidate to
> > > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
> > >
> > > Git tag name is
> > > 2.1.0-rc1
> > >
> > > This release includes the following changes:
> > >
> > > Ignite:
> > > * Persistent cache store
> > > * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync()
> mehtods
> > > * Deprecated IgniteConfiguration.marshaller
> > > * Updated Lucene dependency to version 5.5.2
> > > * Machine learning: implemented K-means clusterization algorithm
> > optimized
> > > for distributed storages
> > > * SQL: CREATE TABLE and DROP TABLE commands support
> > > * SQL: New thin JDBC driver
> > > * SQL: Improved performance of certain queries, when affinity node can
> be
> > > calculated in advance
> > > * SQL: Fixed return type of AVG() function
> > > * SQL: BLOB type support added to thick JDBC driver
> > > * SQL: Improved LocalDate, LocalTime and LocalDateTime support for
> Java 8
> > > * SQL: Added FieldsQueryCursor interface to get fields metadata for
> > > SqlFieldsQuery
> > > * ODBC: Implemented DML statement batching
> > > * Massive performance and stability improvements
> > >
> > > Ignite.NET:
> > > * Automatic remote assembly loading
> > > * NuGet-based standalone node deployment
> > > * Added conditional data removeal via LINQ DeleteAll
> > > * Added TimestampAttribute to control DateTime serialization mode
> > > * Added local collections joins support to LINQ.
> > >
> > > Ignite CPP:
> > > * Added Compute::Call and Compute::Broadcast methods
> > >
> > > Web Console:
> > > * Implemented support for UNIQUE indexes for key fields on import model
> > > from RDBMS
> > > * Added option to show full stack trace on Queries screen
> > > * Added PK alias generation on Models screen.
> > >
> > > Complete list of closed issues:
> > > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20IGNITE%20AND%
> > > 20fixVersion%20%3D%202.1%20AND%20(status%20%3D%
> > > 20closed%20or%20status%20%3D%20resolved)
> > >
> > > DEVNOTES
> > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > plain;f=DEVNOTES.txt;hb=refs/tags/2.1.0-rc1
> > >
> > > RELEASE NOTES
> > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc1
> > >
> > > Please start voting.
> > >
> > > +1 - to accept Apache Ignite 2.1.0-rc1
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite 2.1.0-rc1 (explain why)
> > >
> > > This vote will go for 72 hours.
> > >
> > > Vladimir.
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
> >
>

Re: Ignite Teamcity email notifications

2017-07-15 Thread Dmitry Pavlov

Hi Igniters,

Thanks to Alexey Chetaev we can now setup personal email notifications from
the Teamcity about broken builds.

To set up notifications you can go to your profile and enable email
notification for your own PR and/or master (see the page
http://ci.ignite.apache.org/profile.html?item=userNotifications)

You can set branch filter for example as follows:
+:ignite-2.*
+:pull/2296/head
And enable notifications on
- build fails (only first failing and/or including your changes),
- and successful build (optionally only first build after failed).

Best Regards,
Dmitriy Pavlov

пн, 3 июл. 2017 г. в 17:43, Denis Magda :

> Dmitriy P.,
>
> The list has been created. Here is a response from ASF:
>
> As requested by you, the following mailing list has been created:
> c...@ignite.apache.org 
> Moderators: dma...@apache.org ,
> dsetrak...@apache.org 
> This list is private.
>
>
>
> ---
>
> The list will start accepting mail in 60 minutes from now.  If it's a
> public
> list, it will appear on https://lists.apache.org/ <
> https://lists.apache.org/> within a few minutes of
> the first post to it.
>
> —
> Denis
>
> > On Jun 29, 2017, at 4:10 PM, Denis Magda  wrote:
> >
> > Trigged the alias creation. Will let you know once it’s ready for usage.
> >
> > —
> > Denis
> >
> >> On Jun 29, 2017, at 3:51 PM, Dmitriy Setrakyan 
> wrote:
> >>
> >> I like this alias.
> >>
> >> On Thu, Jun 29, 2017 at 3:43 PM, Denis Magda  wrote:
> >>
> >>> What’s about c...@ignite.apache.org ? If
> there
> >>> are no objections I’ll create the alias.
> >>>
> >>> —
> >>> Denis
> >>>
>  On Jun 29, 2017, at 11:53 AM, Dmitry Pavlov 
> >>> wrote:
> 
>  Hi Dmitriy,
> 
>  At the first step we need some email address to send notifications
> from
>  behalf of TeamCity. We need to set up SMTP server, username and
> password.
>  Later users may set up personal notification rules ( see the link
>  http://ci.ignite.apache.org/profile.html?item=userNotifications).
> 
>  Teamcity takes into account last commits in branch and sends
> >>> notifications
>  separately and only to users which may break the build (option name
> >>> 'builds
>  containing my changes').
> 
>  Best Regards,
>  Dmitriy Pavlov
> 
> 
>  чт, 29 июн. 2017 г. в 21:21, Dmitriy Setrakyan  >:
> 
> > Dmitry, I don't think ign...@apache.org is a valid email address.
> Why
> > creating a mailing list for TC is not a good option?
> >
> > On Thu, Jun 29, 2017 at 8:17 AM, Dmitry Pavlov <
> dpavlov@gmail.com>
> > wrote:
> >
> >> Hi Igniters,
> >>
> >> I want to set up a email notifications from the public Teamcity
> about
> >> broken builds. But there is no configured address and email
> account. To
> > set
> >> up notifications we need some mail box (account) to send messages
> from.
> >>
> >> I asked the apache infrastructure team in
> >> https://issues.apache.org/jira/browse/INFRA-14455
> >> However, they recommended through PMC to create a mailing list. I
> doubt
> > it
> >> can solve the problem.
> >>
> >> I also found out that there are e-mails from the address Ignite
> >>> Teamcity
> > <
> >> ign...@apache.org>.
> >>
> >> Can we use it? Do we know the password for this account?
> >> Any thought how to solve it?
> >>
> >> Best Regards,
> >> Dmitriy Pavlov
> >>
> >
> >>>
> >>>
> >
>
>

[jira] [Created] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

2017-07-15 Thread Dmitriy Pavlov (JIRA)

Dmitriy Pavlov created IGNITE-5759:
--

 Summary: IgniteCache5 suite timed out probably by 
GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
 Key: IGNITE-5759
 URL: https://issues.apache.org/jira/browse/IGNITE-5759
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Pavlov


http://ci.ignite.apache.org/viewLog.html?buildId=727951=Ignite20Tests_IgniteCache5

There is no 'Test has been timed out' message in logs.
Last 'Starting test:' message was 
GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent

Latest exception from working test was as follows;
{noformat}
[23:19:11]W: [org.apache.ignite:ignite-core] [2017-07-14 
20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
 TcpCommunicationSpi failed to establish connection to node, node will be 
dropped from cluster [rmtNode=TcpDiscoveryNode 
[id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4, 
lastExchangeTime=1500063443391, loc=false, ver=2.1.0#19700101-sha1:, 
isClient=false]]
[23:19:11]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node 
still alive?). Make sure that each ComputeTask and cache Transaction has a 
timeout set in order to prevent parties from waiting forever in case of network 
issues [nodeId=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[/127.0.0.1:45273]]
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3173)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2757)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2649)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$5900(TcpCommunicationSpi.java:245)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:4065)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3891)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[23:19:11]W: [org.apache.ignite:ignite-core]Suppressed: 
class org.apache.ignite.IgniteCheckedException: Failed to connect to address 
[addr=/127.0.0.1:45273, err=Connection refused]
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3178)
[23:19:11]W: [org.apache.ignite:ignite-core]... 6 
more
[23:19:11]W: [org.apache.ignite:ignite-core]Caused by: 
java.net.ConnectException: Connection refused
[23:19:11]W: [org.apache.ignite:ignite-core]at 
sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3024)
[23:19:11]W: [org.apache.ignite:ignite-core]... 6 
more
{noformat}

and then
{noformat}
[23:19:11]W: [org.apache.ignite:ignite-core] [2017-07-14 
20:19:11,895][WARN ][main][root] Interrupting threads started so far: 5
[23:19:11] : [Step 4/5] [2017-07-14 20:19:11,895][INFO ][main][root] >>> 
Stopping test class: GridCachePartitionEvictionDuringReadThroughSelfTest <<<
[23:19:11]W: [org.apache.ignite:ignite-core] [20:19:11] (err) 
Failed to execute compound future reducer: GridCompoundFuture 
[rdc=LongSumReducer [sum=0], initFlag=1, lsnrCalls=1, done=false, 
cancelled=false, err=null, futs=[true, true]]class 
org.apache.ignite.IgniteCheckedException: null
[23:19:11]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7246)
[23:19:11]W: [org.apache.ignite:ignite-core]at

Re: [VOTE] Apache Ignite 2.1.0 RC1

2017-07-15 Thread Ilya Suntsov

Lgpl binaries should not to be in svn. This build will be removed.

15 июля 2017 г. 1:52 PM пользователь "Sergey Kozlov" 
написал:

> Igniters
>
> Could someone explain why we include LGPL binary fabric [1] in the release?
> Either it was a mistake or we should upload also SHA1/MD5/ASC checksums as
> well
>
>
> [1]
> https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
> apache-ignite-fabric-lgpl-2.1.0-bin.zip
>
> On Fri, Jul 14, 2017 at 8:45 PM, Vladimir Ozerov 
> wrote:
>
> > gniters!
> >
> > We have uploaded a 2.1.0 release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
> >
> > Git tag name is
> > 2.1.0-rc1
> >
> > This release includes the following changes:
> >
> > Ignite:
> > * Persistent cache store
> > * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync() mehtods
> > * Deprecated IgniteConfiguration.marshaller
> > * Updated Lucene dependency to version 5.5.2
> > * Machine learning: implemented K-means clusterization algorithm
> optimized
> > for distributed storages
> > * SQL: CREATE TABLE and DROP TABLE commands support
> > * SQL: New thin JDBC driver
> > * SQL: Improved performance of certain queries, when affinity node can be
> > calculated in advance
> > * SQL: Fixed return type of AVG() function
> > * SQL: BLOB type support added to thick JDBC driver
> > * SQL: Improved LocalDate, LocalTime and LocalDateTime support for Java 8
> > * SQL: Added FieldsQueryCursor interface to get fields metadata for
> > SqlFieldsQuery
> > * ODBC: Implemented DML statement batching
> > * Massive performance and stability improvements
> >
> > Ignite.NET:
> > * Automatic remote assembly loading
> > * NuGet-based standalone node deployment
> > * Added conditional data removeal via LINQ DeleteAll
> > * Added TimestampAttribute to control DateTime serialization mode
> > * Added local collections joins support to LINQ.
> >
> > Ignite CPP:
> > * Added Compute::Call and Compute::Broadcast methods
> >
> > Web Console:
> > * Implemented support for UNIQUE indexes for key fields on import model
> > from RDBMS
> > * Added option to show full stack trace on Queries screen
> > * Added PK alias generation on Models screen.
> >
> > Complete list of closed issues:
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > 20fixVersion%20%3D%202.1%20AND%20(status%20%3D%
> > 20closed%20or%20status%20%3D%20resolved)
> >
> > DEVNOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=DEVNOTES.txt;hb=refs/tags/2.1.0-rc1
> >
> > RELEASE NOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc1
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 2.1.0-rc1
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 2.1.0-rc1 (explain why)
> >
> > This vote will go for 72 hours.
> >
> > Vladimir.
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

Re: [VOTE] Apache Ignite 2.1.0 RC1

2017-07-15 Thread Sergey Kozlov

Igniters

Could someone explain why we include LGPL binary fabric [1] in the release?
Either it was a mistake or we should upload also SHA1/MD5/ASC checksums as
well


[1]
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/apache-ignite-fabric-lgpl-2.1.0-bin.zip

On Fri, Jul 14, 2017 at 8:45 PM, Vladimir Ozerov 
wrote:

> gniters!
>
> We have uploaded a 2.1.0 release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
>
> Git tag name is
> 2.1.0-rc1
>
> This release includes the following changes:
>
> Ignite:
> * Persistent cache store
> * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync() mehtods
> * Deprecated IgniteConfiguration.marshaller
> * Updated Lucene dependency to version 5.5.2
> * Machine learning: implemented K-means clusterization algorithm optimized
> for distributed storages
> * SQL: CREATE TABLE and DROP TABLE commands support
> * SQL: New thin JDBC driver
> * SQL: Improved performance of certain queries, when affinity node can be
> calculated in advance
> * SQL: Fixed return type of AVG() function
> * SQL: BLOB type support added to thick JDBC driver
> * SQL: Improved LocalDate, LocalTime and LocalDateTime support for Java 8
> * SQL: Added FieldsQueryCursor interface to get fields metadata for
> SqlFieldsQuery
> * ODBC: Implemented DML statement batching
> * Massive performance and stability improvements
>
> Ignite.NET:
> * Automatic remote assembly loading
> * NuGet-based standalone node deployment
> * Added conditional data removeal via LINQ DeleteAll
> * Added TimestampAttribute to control DateTime serialization mode
> * Added local collections joins support to LINQ.
>
> Ignite CPP:
> * Added Compute::Call and Compute::Broadcast methods
>
> Web Console:
> * Implemented support for UNIQUE indexes for key fields on import model
> from RDBMS
> * Added option to show full stack trace on Queries screen
> * Added PK alias generation on Models screen.
>
> Complete list of closed issues:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> 20fixVersion%20%3D%202.1%20AND%20(status%20%3D%
> 20closed%20or%20status%20%3D%20resolved)
>
> DEVNOTES
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=DEVNOTES.txt;hb=refs/tags/2.1.0-rc1
>
> RELEASE NOTES
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc1
>
> Please start voting.
>
> +1 - to accept Apache Ignite 2.1.0-rc1
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 2.1.0-rc1 (explain why)
>
> This vote will go for 72 hours.
>
> Vladimir.
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: [ignite] your /dist/ artifacts - 1 BAD signature

2017-07-15 Thread Sergey Kozlov

Guys

I suppose it was uploaded by mistake and should be removed.

Ilya could you explain the reasons of that deployment?

On Sat, Jul 15, 2017 at 9:02 AM, Konstantin Boudnik  wrote:

> BTW, keep in mind that /dist ends up being sync'ed across a bunch of
> Apache mirrors. So, the experiments are better be kept to a less
> visible environment.
>
> Cos
> --
>   With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Fri, Jul 14, 2017 at 10:26 PM, Denis Magda  wrote:
> > Igniters,
> >
> > Especially Sergey K., Ilya S and Alexey Chetaev,
> >
> > Could you explain what those “TEST” artifacts are doing in the dist
> folder? Are you trying out the new release procedure?
> >
> > In addition to the questions, please fix the issue following the issue
> brought out below.
> >
> > —
> > Denis
> >
> >> Begin forwarded message:
> >>
> >> From: Henk Penning 
> >> Subject: [ignite] your /dist/ artifacts - 1 BAD signature
> >> Date: July 14, 2017 at 10:07:11 PM PDT
> >> To: priv...@ignite.apache.org
> >> Cc: he...@apache.org, sboi...@apache.org
> >> Reply-To: priv...@ignite.apache.org
> >>
> >> Hi PMC ignite,
> >>
> >>  I watch 'www.apache.org/dist/', and I noticed that :
> >>
> >>  -- you have 1 BAD pgp signature
> >>
> >>   ignite/2.1.0-TEST/apache-ignite-2.1.0-TEST-src.zip.asc
> >>
> >>  -- you have 3 unsigned artifacts :
> >>
> >>   ignite/2.1.0-TEST/apache-ignite-fabric-2.1.0-TEST-bin.zip
> >>   ignite/2.1.0-TEST/apache-ignite-fabric-lgpl-2.1.0-TEST-bin.zip
> >>   ignite/2.1.0-TEST/apache-ignite-hadoop-2.1.0-TEST-bin.zip
> >>
> >>  Please fix these problems soon ; for details, see
> >>
> >>http://mirror-vm.apache.org/~henkp/checker/sig.html#project-ignite
> >>http://mirror-vm.apache.org/~henkp/checker/md5.html
> >>
> >>  For information on how to fix problems, see the faq :
> >>
> >>http://mirror-vm.apache.org/~henkp/checker/faq.html
> >>
> >>  Thanks a lot, regards,
> >>
> >>  Henk Penning -- apache.org infrastructure
> >>
> >>  PS. The contents of this message is generated,
> >>  but the mail itself is sent "by hand".
> >>  PS. Please cc me on all relevant emails.
> >>
> >>    _
> >> Henk P. Penning, ICT-beta R Uithof BBL-761   _/ \_
> >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> >> Princetonplein 5, 3584CC Utrecht, NL  F +31 30 253 4553 \_/ \_/
> >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> >>
> >
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: [ignite] your /dist/ artifacts - 1 BAD signature

2017-07-15 Thread Konstantin Boudnik

BTW, keep in mind that /dist ends up being sync'ed across a bunch of
Apache mirrors. So, the experiments are better be kept to a less
visible environment.

Cos
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Fri, Jul 14, 2017 at 10:26 PM, Denis Magda  wrote:
> Igniters,
>
> Especially Sergey K., Ilya S and Alexey Chetaev,
>
> Could you explain what those “TEST” artifacts are doing in the dist folder? 
> Are you trying out the new release procedure?
>
> In addition to the questions, please fix the issue following the issue 
> brought out below.
>
> —
> Denis
>
>> Begin forwarded message:
>>
>> From: Henk Penning 
>> Subject: [ignite] your /dist/ artifacts - 1 BAD signature
>> Date: July 14, 2017 at 10:07:11 PM PDT
>> To: priv...@ignite.apache.org
>> Cc: he...@apache.org, sboi...@apache.org
>> Reply-To: priv...@ignite.apache.org
>>
>> Hi PMC ignite,
>>
>>  I watch 'www.apache.org/dist/', and I noticed that :
>>
>>  -- you have 1 BAD pgp signature
>>
>>   ignite/2.1.0-TEST/apache-ignite-2.1.0-TEST-src.zip.asc
>>
>>  -- you have 3 unsigned artifacts :
>>
>>   ignite/2.1.0-TEST/apache-ignite-fabric-2.1.0-TEST-bin.zip
>>   ignite/2.1.0-TEST/apache-ignite-fabric-lgpl-2.1.0-TEST-bin.zip
>>   ignite/2.1.0-TEST/apache-ignite-hadoop-2.1.0-TEST-bin.zip
>>
>>  Please fix these problems soon ; for details, see
>>
>>http://mirror-vm.apache.org/~henkp/checker/sig.html#project-ignite
>>http://mirror-vm.apache.org/~henkp/checker/md5.html
>>
>>  For information on how to fix problems, see the faq :
>>
>>http://mirror-vm.apache.org/~henkp/checker/faq.html
>>
>>  Thanks a lot, regards,
>>
>>  Henk Penning -- apache.org infrastructure
>>
>>  PS. The contents of this message is generated,
>>  but the mail itself is sent "by hand".
>>  PS. Please cc me on all relevant emails.
>>
>>    _
>> Henk P. Penning, ICT-beta R Uithof BBL-761   _/ \_
>> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> Princetonplein 5, 3584CC Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>>
>

Re: [ignite] your /dist/ artifacts - 1 BAD signature

Re: Ignite Teamcity email notifications

Re: [VOTE] Apache Ignite 2.1.0 RC1

Re: Ignite Teamcity email notifications

[jira] [Created] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

Re: [VOTE] Apache Ignite 2.1.0 RC1

Re: [VOTE] Apache Ignite 2.1.0 RC1

Re: [ignite] your /dist/ artifacts - 1 BAD signature

Re: [ignite] your /dist/ artifacts - 1 BAD signature

9 matches

Site Navigation

Mail list logo

Footer information