Re: [TeamCity] DataFrame Examples

[Nikolay Izhikov]

Hello, guys.

I think we are ready to enable testing of Spark examples on Team City.
Can you help me with best choice to do it?

Currently, we have 'Ignite Examples' to run `IgniteExamplesSelfTestSuite`.

We also have a `IgniteExamplesSparkSelfTestSuite` to test spark example.
`IgniteExamplesSparkSelfTestSuite` exists in source only if `spark` profile 
enabled so we can't just add it to `IgniteExamplesSelfTestSuite`.

I see following option here:

1. Edit 'Ignite Examples' to run both `IgniteExamplesSelfTestSuite` and 
`IgniteExamplesSparkSelfTestSuite`.
2. Create new test plan to run `IgniteExamplesSparkSelfTestSuite`.

Thoughts?

P.S. We also need minor changes [1] to make sure Spark examples are running 
correctly.

[1] https://github.com/apache/ignite/pull/3590

В Вт, 27/02/2018 в 11:56 -0800, Valentin Kulichenko пишет:
> If we can run Scala examples there, then yes.
> 
> -Val
> 
> On Tue, Feb 27, 2018 at 11:54 AM, Dmitry Pavlov 
> wrote:
> 
> > Nikolay, Val,
> > 
> > Could these examples be tested in standard Ignite Examples test suite? As
> > far as I know Ignite ML and Ignite IGFS are also tested there.
> > 
> > Sincerely,
> > Dmitriy Pavlov
> > 
> > вт, 27 февр. 2018 г. в 22:49, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>:
> > 
> > > Nikolay,
> > > 
> > > Spark integration is not related to Scalar, the only thing they have in
> > > common is Scala. I think we should have a separate configuration for
> > > ignite-spark module. If anything Spark related is currently in Scalar
> > > suite, it should be moved from there.
> > > 
> > > -Val
> > > 
> > > On Tue, Feb 27, 2018 at 3:03 AM, Nikolay Izhikov 
> > > wrote:
> > > 
> > > > Hello, Igniters.
> > > > 
> > > > I've created several examples for a Ignite DataFrame.
> > > > Currently, they are not tested on Team City.
> > > > 
> > > > As far as I can understand, they should be checked in "Ignite Scalar
> > > > Examples [Scala]".
> > > > But it marked as obsolete [1]
> > > > 
> > > > Please, give me advice:
> > > > 
> > > > 1. Should we test Ignite DataFrame examples on Team City?
> > > > 
> > > > 2. Which plan should be used for that?
> > > > 
> > > > [1]
> > > 
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1068099=
> > > > IgniteTestsForCodeCoverage_IgniteScalarExamples=buildParameters

signature.asc
Description: This is a digitally signed message part

[GitHub] ignite pull request #3653: for TeamCity testing

[daradurvs]

GitHub user daradurvs opened a pull request:

https://github.com/apache/ignite/pull/3653

for TeamCity testing



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/daradurvs/ignite ignite-5910-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3653.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3653


commit 3a4e8c0cbc990d13a5b06f11697e7c77878dc708
Author: daradurvs 
Date:   2017-08-03T07:46:14Z

ignite-5910: fixed ClassCastException

commit a8b92625f0718c3e6e8147199a378b0cb7468453
Author: daradurvs 
Date:   2017-08-03T11:17:56Z

ignite-5910: fixed stop remote grid (prevention of freezing)

commit 1f4df24c020c3b6f705287246c8a2153e171db47
Author: Vyacheslav Daradur 
Date:   2018-02-20T16:18:04Z

ignite-5910: reworked logic of node's stopping in separate JVM

commit 329aef9bdd84337a5b10e8a7d6ecb29389e7cc2c
Author: Vyacheslav Daradur 
Date:   2018-02-20T16:20:30Z

Revert "ignite-5910: fixed stop remote grid (prevention of freezing)"

This reverts commit 09f04c6ca6db886dfbd0c0cf94c3f29242ccb8d7.

commit 02d584f58b7f17d362aaf34d22c4bf449f13296b
Author: Vyacheslav Daradur 
Date:   2018-02-20T16:41:19Z

ignite-5910: added NODE_LEFT_TIMEOUT

commit 8d42ffaba90acc597ccbd8b1b779e075fbaeec82
Author: Vyacheslav Daradur 
Date:   2018-02-21T11:20:22Z

ignite-5910: ExecutorService was replaced with CompletableFuture

commit c1bc5514e22658ccf774a88dbd7d6893846f7fd9
Author: Vyacheslav Daradur 
Date:   2018-02-21T11:22:59Z

ignite-5910: code style fix - long line

commit c67c363f24956d26701b63012498fc7f36067155
Author: Vyacheslav Daradur 
Date:   2018-03-15T15:27:34Z

ignite-5910: replace assertion by if statement

commit 8824174fe6583634622c7d15b6da2693517c1961
Author: Vyacheslav Daradur 
Date:   2018-03-16T15:22:24Z

ignite-5910: review fix

commit a23644df237f57b39c1969689b305684e7e7bdbe
Author: Vyacheslav Daradur 
Date:   2018-03-17T21:59:35Z

ignite-5910: synchronization timeout was removed

commit 8fcbcd40a0f00354f57bb189ebc640ab79b8408e
Author: Vyacheslav Daradur 
Date:   2018-03-18T18:50:50Z

ignite-5910: sync id changed

commit afe7783134d936e8bae7dddbb6151dc12c8311bb
Author: Vyacheslav Daradur 
Date:   2018-03-18T19:47:45Z

test




---

[GitHub] ignite pull request #3652: IGNITE-7770 A bunch of changes to fix tx timeout ...

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

https://github.com/apache/ignite/pull/3652

IGNITE-7770 A bunch of changes to fix tx timeout handling.

For TeamCity tests only

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-7770-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3652.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3652


commit 8a46bf807a0c933c9e4d9d2c83c27d03722b6055
Author: Andrey Kuznetsov 
Date:   2018-03-18T17:08:33Z

IGNITE-7770 A bunch of changes to fix tx timeout handling.




---

[jira] [Created] (IGNITE-7979) Web Console: Refactor query notebooks to dedicated screen.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7979:


 Summary: Web Console: Refactor query notebooks to dedicated screen.
 Key: IGNITE-7979
 URL: https://issues.apache.org/jira/browse/IGNITE-7979
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexander Kalinin
 Fix For: 2.5


Current implementation with drop down menu is not good with large number of 
notebooks.

Also, no sorting, no filtering and no cloning available.

Lets rework to dedicated screen with table.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)