[MTCGA]: new failures in builds [5868077] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Control Utility https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility?branch=%3Cdefault%3E Changes may lead to failure were done by - kirill tkalenko https://ci.ignite.apache.org/viewModification.html?modId=916619 - aleksey plekhanov https://ci.ignite.apache.org/viewModification.html?modId=916624 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 05:14:48 11-02-2021
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Folks, Do we need any other critical issues from the master branch that need to be cherry-picked picked from the master branch? I've marked the latest select issues with patching version 2.10. - benchmarks completed (I'll do another one prior to preparing rc) - the release notes merged - cherry-picked issue (IGNITE-14073 Fixed transactions failover) - most of the documentation pages also merged Hopefully, by Friday the 12th everything will be ready for the preparation of a release candidate. On Tue, 9 Feb 2021 at 05:09, Никита Сафонов wrote: > > Hi everyone, > > Below are two lists of items representing all the remaining (and completed) > documentation tasks for the Ignite 2.10 release. > > The "*Improvements*" part includes PRs on reworked documentation. > The "*Finished*" part includes PRs on newly added documentation. > > *Improvements:* > > Documentation for .NET thin client service invocation > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > [2] https://github.com/apache/ignite/pull/8756 > > Documentation for cache warm-up strategy > [1] https://issues.apache.org/jira/browse/IGNITE-13385 > [2] https://github.com/apache/ignite/pull/8703 > > *Finished:* > > Document control.(sh|bin) command to get an arbitrary SystemView > [1] https://issues.apache.org/jira/browse/IGNITE-14142 > [2] https://github.com/apache/ignite/pull/8775 > > Document metric for processed keys when rebuilding indexes > [1] https://issues.apache.org/jira/browse/IGNITE-14143 > [2] https://github.com/apache/ignite/pull/8776 > > Document C++ thin client transactions > [1] https://issues.apache.org/jira/browse/IGNITE-14144 > [2] https://github.com/apache/ignite/pull/8777 > > Please don't hesitate to ask me if you have any questions or concerns. > > With best regards, > Nikita > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов : > > > Maxim, > > > > Thank you for being ready to help! > > > > As I mentioned before, I'm sharing the completed doc items today. > > Below is the list of tickets with the prepared PR's: > > > > *- Documentation: SQL tracing.* > > [1] https://issues.apache.org/jira/browse/IGNITE-13981 > > [2] https://github.com/apache/ignite/pull/8762 > > > > *- Documentation for async API (Thin client Java API)* > > [1] https://issues.apache.org/jira/browse/IGNITE-14128 > > [2] https://github.com/apache/ignite/pull/8753 > > > > *- Documentation for .NET: Thin Client: Service invocation* > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > [2] https://github.com/apache/ignite/pull/8756 > > > > *- Document cluster API implementation for CPP* > > [1] https://issues.apache.org/jira/browse/IGNITE-14133 > > [2] https://github.com/apache/ignite/pull/8761 > > > > > > I still have some docs to finish/improve. > > I do believe that I'll provide the rest of the remaining documentation by > > the end of Monday. > > > > Regards, > > Nikita > > > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov : > > > >> Nikita, > >> > >> Thank you, I will be waiting for the review. > >> > >> > I'll give the precise estimate tomorrow as I'm still waiting for some > >> info > >> from the dev side. > >> Let me know if you need any kind of help. > >> > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов > >> wrote: > >> > > >> > Hi Maxim, > >> > > >> > I can take a look! > >> > > >> > Moreover, I'm finishing the work on the remaining documentation tickets. > >> > I do believe that I'll be able to provide several PR's tomorrow and > >> > complete the rest in a couple of days. > >> > I'll give the precise estimate tomorrow as I'm still waiting for some > >> info > >> > from the dev side. > >> > > >> > Regards, > >> > Nikita > >> > > >> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov : > >> > > >> > > Folks, > >> > > > >> > > > >> > > I've prepared the RELEASE_NOTES. > >> > > Would anyone take a look at the PR [2] [1]? > >> > > > >> > > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069 > >> > > [2] https://github.com/apache/ignite/pull/8748/files > >> > > > >> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov > >> wrote: > >> > > > > >> > > > Folks, > >> > > > > >> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1]. > >> > > > Everything looks good at the first glance. > >> > > > > >> > > > > >> > > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10) > >> > > > > >> > > > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов < > >> vlasovpavel2...@gmail.com> > >> > > wrote: > >> > > > > > >> > > > > Hi Maxim, > >> > > > > > >> > > > > terrific! > >> > > > > > >> > > > > Then, I'll continue with the tasks on the list. > >> > > > > > >> > > > > Thank you, > >> > > > > Nikita > >> > > > > > >> > > > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov : > >> > > > > > >> > > > > > Hello Nikita, > >> > > > > > > >> > > > > > Thank you for sharing the state. > >> > > > > > > >> > > > > > I think we can move on to the next stages of the release. There > >> are a > >> > > > > > few
[MTCGA]: new failures in builds [5863529] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Test with high flaky rate in master IgniteSpringBeanSpringResourceInjectionTest.testSpringResourceInjectedInService https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5473373570722907835=%3Cdefault%3E=testDetails Changes may lead to failure were done by - alexey goncharuk https://ci.ignite.apache.org/viewModification.html?modId=916440 - anton kalashnikov https://ci.ignite.apache.org/viewModification.html?modId=916395 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 21:14:48 10-02-2021
[jira] [Created] (IGNITE-14161) Continuous Query ignores first written entry if Transformer returns user type
Ilya Kasnacheev created IGNITE-14161:
Summary: Continuous Query ignores first written entry if
Transformer returns user type
Key: IGNITE-14161
URL: https://issues.apache.org/jira/browse/IGNITE-14161
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.10
Reporter: Ilya Kasnacheev
Yup. Please see the discussion and the reproducer class.
First put will come as CREATED then UPDATED
{code}
CacheContinuousQueryEvent [evtType=CREATED,
key=CacheAccountKey{affinityAccountKey=AffinityAccountKey{accountId=8}},
newVal=Account{accountKey=DomainAccountKey{accountId=8}, name='Person#8'},
oldVal=null, partCntr=1]
CacheContinuousQueryEvent [evtType=UPDATED,
key=CacheAccountKey{affinityAccountKey=AffinityAccountKey{accountId=8}},
newVal=Account{accountKey=DomainAccountKey{accountId=8}, name='Person#8'},
oldVal=Account{accountKey=DomainAccountKey{accountId=8}, name='Person#8'},
partCntr=2]
{code}
and the event will be lost. Subsequent have just 1 event and are OK:
{code}
Transform CacheContinuousQueryEvent [evtType=CREATED,
key=CacheAccountKey{affinityAccountKey=AffinityAccountKey{accountId=16}},
newVal=Account{accountKey=DomainAccountKey{accountId=16}, name='Person#16'},
oldVal=null, partCntr=1]
Transform CacheContinuousQueryEvent [evtType=CREATED,
key=CacheAccountKey{affinityAccountKey=AffinityAccountKey{accountId=18}},
newVal=Account{accountKey=DomainAccountKey{accountId=18}, name='Person#18'},
oldVal=null, partCntr=1]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14160) Issue log warning when GridNioSslHandler.handshake() takes too long
Andrey Kuznetsov created IGNITE-14160: - Summary: Issue log warning when GridNioSslHandler.handshake() takes too long Key: IGNITE-14160 URL: https://issues.apache.org/jira/browse/IGNITE-14160 Project: Ignite Issue Type: Task Affects Versions: 2.9.1 Reporter: Andrey Kuznetsov This will be helpful in investigating client connectivity/performance issues. Threshold duration can be just a reasonable constant, say, 1 second. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14159) IgniteSpiAdapter consistency check also logs warnings for optional configurations
Wouter Bancken created IGNITE-14159:
---
Summary: IgniteSpiAdapter consistency check also logs warnings for
optional configurations
Key: IGNITE-14159
URL: https://issues.apache.org/jira/browse/IGNITE-14159
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Wouter Bancken
*Context*
We are using a setup with a server node and a thick client and since our
upgrade to Ignite 2.9.1 we always get the following notice when the thick
client joins the cluster:
{code:java}
>>> ---
>>> + Courtesy notice that joining node has inconsistent configuration. +
>>> + Ignore this message if you are sure that this is done on purpose. +
>>> ---
>>> Remote Node ID: ...
>>> Remote SPI with the same name is not configured: ...
>>> => Local node: ...
{code}
This notice is triggered because our custom CollisionSPI is not configured for
the thick client while it is configured for the server node since it does not
make sense to configure a CollisionSPI for a thick client.
*Cause*
This new behaviour is caused by commit
[https://github.com/apache/ignite/commit/0ef1debd2fc9452376a9e1ce36f0a9a945469783#diff-0511a13c0739b281c29879279241f4efe824249513527473de0f93674848d301]
Before Ignite 2.9.1 the warning was not logged since the SPI configuration is
optional.
The code in IgniteSpiAdapter explicitly mentions that the notice should not be
logged for optional configurations:
https://github.com/apache/ignite/blob/2d2044a63440e9b9d8495f35819ccee26d8324e4/modules/core/src/main/java/org/apache/ignite/spi/IgniteSpiAdapter.java#L515
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14158) SQL. Calcite: returns an empty string instead of null values for numeric types.
Fedor Malchikov created IGNITE-14158:
-
Summary: SQL. Calcite: returns an empty string instead of null
values for numeric types.
Key: IGNITE-14158
URL: https://issues.apache.org/jira/browse/IGNITE-14158
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Fedor Malchikov
Example:
{code:sql}
CREATE TABLE t1 ( id INT NOT NULL, bool_col BOOLEAN, tinyint_col TINYINT,
smallint_col SMALLINT, int_col INT, bigint_col BIGINT, varchar_col VARCHAR,
char_col CHAR, float_col FLOAT, double_col DOUBLE, time_col TIME, PRIMARY KEY
(id));
INSERT INTO t1
(id,bool_col,tinyint_col,smallint_col,int_col,bigint_col,varchar_col,char_col,float_col,double_col,time_col)
VALUES (1, null, null, null, null, null, null, null, null, null, null);
SELECT * FROM t1;
'ID','BOOL_COL','TINYINT_COL','SMALLINT_COL','INT_COL','BIGINT_COL','VARCHAR_COL','CHAR_COL','FLOAT_COL','DOUBLE_COL','TIME_COL'
'1','','','','','','','','','',''
{code}
H2 return:
{code:sql}
SELECT * FROM t1;
'ID','BOOL_COL','TINYINT_COL','SMALLINT_COL','INT_COL','BIGINT_COL','VARCHAR_COL','CHAR_COL','FLOAT_COL','DOUBLE_COL','TIME_COL'
'1','','null','null','null','null','','','null','null',''
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14156) SQL. Calcite: Does not return the count result if there are 0 elements in the table.
Fedor Malchikov created IGNITE-14156:
-
Summary: SQL. Calcite: Does not return the count result if there
are 0 elements in the table.
Key: IGNITE-14156
URL: https://issues.apache.org/jira/browse/IGNITE-14156
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Fedor Malchikov
Example:
{code:sql}
CREATE TABLE t1 ( id INT NOT NULL, int_col INT, PRIMARY KEY (id));
SELECT COUNT(*) FROM t1;
++
| EXPR$0 |
++
++
{code}
H2 return:
{code:java}
SELECT COUNT(*) FROM t1;
++
|COUNT(*)|
++
| 0 |
++
{code}
if add some elements, then calcite return value:
{code:SQL}
SELECT COUNT(*) FROM t1;
++
| EXPR$0 |
++
| 5 |
++
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14157) SQL. Calcite: Returns the name of the variable for count operations as the column name
Fedor Malchikov created IGNITE-14157:
-
Summary: SQL. Calcite: Returns the name of the variable for count
operations as the column name
Key: IGNITE-14157
URL: https://issues.apache.org/jira/browse/IGNITE-14157
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Fedor Malchikov
Example:
{code:sql}
CREATE TABLE t1 ( id INT NOT NULL, int_col INT, PRIMARY KEY (id));
SELECT COUNT(*) FROM t1;
++
| EXPR$0 |
++
++
{code}
H2 return as expected:
{code:java}
SELECT COUNT(*) FROM t1;
++
|COUNT(*)|
++
| 0 |
++
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14155) Test IgniteClusterIdTagTest.testInMemoryClusterTag is flaky on TC
Sergey Chugunov created IGNITE-14155: Summary: Test IgniteClusterIdTagTest.testInMemoryClusterTag is flaky on TC Key: IGNITE-14155 URL: https://issues.apache.org/jira/browse/IGNITE-14155 Project: Ignite Issue Type: Test Reporter: Sergey Chugunov Assignee: Sergey Chugunov History of the test is available [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2444565365384645281=testDetails_IgniteTests24Java8=%3Cdefault%3E]. This test is flaky but the problem is in the test itself as it synchronously asserts a condition that is intrinsically asynchronous. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14154) Remove test test_unsupported_affinity_cache_operation_routed_to_random_node
Ivan Daschinskiy created IGNITE-14154: - Summary: Remove test test_unsupported_affinity_cache_operation_routed_to_random_node Key: IGNITE-14154 URL: https://issues.apache.org/jira/browse/IGNITE-14154 Project: Ignite Issue Type: Test Reporter: Ivan Daschinskiy Currently, this test simply the same as test_replicated_cache_operation_routed_to_random_node, but it required custom affinity function, that is introduced only in 2.9.1. I suggest to remove it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14153) TcpCommunicationSpi#closeStaleConnections() doesn't work for outcoming connections
Igor Belyakov created IGNITE-14153: -- Summary: TcpCommunicationSpi#closeStaleConnections() doesn't work for outcoming connections Key: IGNITE-14153 URL: https://issues.apache.org/jira/browse/IGNITE-14153 Project: Ignite Issue Type: Improvement Components: networking Affects Versions: 2.9.1 Reporter: Igor Belyakov Assignee: Igor Belyakov Scenario: 1. Node1 established communication connection to Node2. 2. Due to network issue the connection was closed on Node2 side, but was still alive on Node1 side. (half-open connection) 3. At some point of time Node2 tries to send a message to Node1, and since there are no existing connections it creates a new one. 4. Node1 detects that it already has connection to Node2 and prints next message: [TcpCommunicationSpi] Received incoming connection when already connected to this node, rejecting [locNode=2cc905e6--48c1-b316-7652d661, rmtNode=44c537a7-6070-4272-a545-cff054b0] 5. Node1 tries to close existing connection by using closeStaleConnection() method, but since the connection was outcoming it skipped due to "if (ses0.accepted())" check. 6. Node2 makes an infinite amount of tries to connect without success. Reproducer is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14152) JCache TCK suite runs some Ignite tests.
Maksim Timonin created IGNITE-14152: --- Summary: JCache TCK suite runs some Ignite tests. Key: IGNITE-14152 URL: https://issues.apache.org/jira/browse/IGNITE-14152 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin There is a wrong configuration of the "jcache-tck" profile. It excludes only "*Test.java" classes, but by default maven runs also "*Tests.java" classes. [1] So, collection IgniteDataIntegrity*Tests* [2] runs for every start of this TC suite. Also after IGNITE-130512 the default collection of test expanded, then there are more tests started to run within the suite and it started to fail by timeout. [1] https://maven.apache.org/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html [2] https://ci.ignite.apache.org/viewLog.html?buildId=5857723=IgniteTests24Java8_JCacheTck11=testsInfo -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Ignite Extensions tests
Can you pinpoint exact string in log where another Ignite node is interfering, please? > On 10 Feb 2021, at 11:50, Mikhail Petrov wrote: > > Here is an example - [1]. > > [1] - > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_SpringTransactions_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv > > On 10.02.2021 11:39, Petr Ivanov wrote: >> Very good, thanks! >> I will prepare build shortly. >> >> About flakiness — send me link to build where problem is, I will try to >> investigate. >> >>> On 10 Feb 2021, at 11:17, Mikhail Petrov wrote: >>> >>> Petr, ticket [1] was merged to the master branch. TC build is ok now - [2]. >>> Sometimes i faced that some tests can be flaky because test nodes were >>> trying to join extra incompatible node that does not belong to the test. >>> But I think we could investigate it in a separate ticket. >>> >>> Could I ask you to create separate test suite for the Spring Cache >>> extension similar to Spring Transactions for the following PR: >>> https://github.com/apache/ignite-extensions/pull/42 >>> >>> [1] - https://issues.apache.org/jira/browse/IGNITE-14150 >>> >>> [2] - >>> https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions_Tests_IgniteExtensions_Tests=%3Cdefault%3E >>> >>> On 10.02.2021 10:40, Petr Ivanov wrote: I've updated Extensions template to use only Linux agents. Will wait for ticket in master, thanks! > On 10 Feb 2021, at 01:05, Mikhail Petrov wrote: > > Hi, Petr. > > It seems that the problem is in an outdated version of the maven surefire > plugin that is used in ignite-extensions. > > I created the corresponding ticket [1]. > > I also faced that current ignite-extensions build is broken on windows > agents - [2]. It fails with the following error: > > /[22:47:43]'#!' is not recognized as an internal or external command, > [22:47:43]operable program or batch file. > [22:47:43]Environment variable -o nounset; set -o errexit; set -o > pipefail; set -o errtrace; set -o functrace not defined > [22:47:43]Environment variable -x not defined > [22:47:43]'rm' is not recognized as an internal or external command, > [22:47:43]operable program or batch file. > [22:47:43]The syntax of the command is incorrect. > [22:47:43]'cp' is not recognized as an internal or external command, > [22:47:43]operable program or batch file. > [22:47:43]Process exited with code 1/ > > > Could you check it, please? > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14150 > > [2] - > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Flink_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv > > On 09.02.2021 13:36, Petr Ivanov wrote: >> Hi, Nikolay. >> >> >> I've created a set of tests for extensions, and part of them are failing >> with: >> >> JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365 >> » NoSuchMethod >> java.lang.NoSuchMethodError: >> org.apache.maven.surefire.report.SimpleReportEntry.withException(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/apache/maven/surefire/report/StackTraceWriter;)Lorg/apache/maven/surefire/report/SimpleReportEntry; >> at >> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) >> at >> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) >> at >> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) >> at >> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) >> >> >> Could you check [1] please? >> >> >> [1] >> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_RunAllTests/5864907?buildTab=dependencies=list >>
Re: Ignite Extensions tests
Here is an example - [1]. [1] - https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_SpringTransactions_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv On 10.02.2021 11:39, Petr Ivanov wrote: Very good, thanks! I will prepare build shortly. About flakiness — send me link to build where problem is, I will try to investigate. On 10 Feb 2021, at 11:17, Mikhail Petrov wrote: Petr, ticket [1] was merged to the master branch. TC build is ok now - [2]. Sometimes i faced that some tests can be flaky because test nodes were trying to join extra incompatible node that does not belong to the test. But I think we could investigate it in a separate ticket. Could I ask you to create separate test suite for the Spring Cache extension similar to Spring Transactions for the following PR: https://github.com/apache/ignite-extensions/pull/42 [1] - https://issues.apache.org/jira/browse/IGNITE-14150 [2] - https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions_Tests_IgniteExtensions_Tests=%3Cdefault%3E On 10.02.2021 10:40, Petr Ivanov wrote: I've updated Extensions template to use only Linux agents. Will wait for ticket in master, thanks! On 10 Feb 2021, at 01:05, Mikhail Petrov wrote: Hi, Petr. It seems that the problem is in an outdated version of the maven surefire plugin that is used in ignite-extensions. I created the corresponding ticket [1]. I also faced that current ignite-extensions build is broken on windows agents - [2]. It fails with the following error: /[22:47:43]'#!' is not recognized as an internal or external command, [22:47:43]operable program or batch file. [22:47:43]Environment variable -o nounset; set -o errexit; set -o pipefail; set -o errtrace; set -o functrace not defined [22:47:43]Environment variable -x not defined [22:47:43]'rm' is not recognized as an internal or external command, [22:47:43]operable program or batch file. [22:47:43]The syntax of the command is incorrect. [22:47:43]'cp' is not recognized as an internal or external command, [22:47:43]operable program or batch file. [22:47:43]Process exited with code 1/ Could you check it, please? [1] - https://issues.apache.org/jira/browse/IGNITE-14150 [2] - https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Flink_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv On 09.02.2021 13:36, Petr Ivanov wrote: Hi, Nikolay. I've created a set of tests for extensions, and part of them are failing with: JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365 » NoSuchMethod java.lang.NoSuchMethodError: org.apache.maven.surefire.report.SimpleReportEntry.withException(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/apache/maven/surefire/report/StackTraceWriter;)Lorg/apache/maven/surefire/report/SimpleReportEntry; at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) Could you check [1] please? [1] https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_RunAllTests/5864907?buildTab=dependencies=list
Re: Ignite Extensions tests
Very good, thanks! I will prepare build shortly. About flakiness — send me link to build where problem is, I will try to investigate. > On 10 Feb 2021, at 11:17, Mikhail Petrov wrote: > > Petr, ticket [1] was merged to the master branch. TC build is ok now - [2]. > Sometimes i faced that some tests can be flaky because test nodes were trying > to join extra incompatible node that does not belong to the test. But I think > we could investigate it in a separate ticket. > > Could I ask you to create separate test suite for the Spring Cache extension > similar to Spring Transactions for the following PR: > https://github.com/apache/ignite-extensions/pull/42 > > [1] - https://issues.apache.org/jira/browse/IGNITE-14150 > > [2] - > https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions_Tests_IgniteExtensions_Tests=%3Cdefault%3E > > On 10.02.2021 10:40, Petr Ivanov wrote: >> I've updated Extensions template to use only Linux agents. >> >> Will wait for ticket in master, thanks! >> >> >> >>> On 10 Feb 2021, at 01:05, Mikhail Petrov wrote: >>> >>> Hi, Petr. >>> >>> It seems that the problem is in an outdated version of the maven surefire >>> plugin that is used in ignite-extensions. >>> >>> I created the corresponding ticket [1]. >>> >>> I also faced that current ignite-extensions build is broken on windows >>> agents - [2]. It fails with the following error: >>> >>> /[22:47:43]'#!' is not recognized as an internal or external command, >>> [22:47:43]operable program or batch file. >>> [22:47:43]Environment variable -o nounset; set -o errexit; set -o pipefail; >>> set -o errtrace; set -o functrace not defined >>> [22:47:43]Environment variable -x not defined >>> [22:47:43]'rm' is not recognized as an internal or external command, >>> [22:47:43]operable program or batch file. >>> [22:47:43]The syntax of the command is incorrect. >>> [22:47:43]'cp' is not recognized as an internal or external command, >>> [22:47:43]operable program or batch file. >>> [22:47:43]Process exited with code 1/ >>> >>> >>> Could you check it, please? >>> >>> >>> [1] - https://issues.apache.org/jira/browse/IGNITE-14150 >>> >>> [2] - >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Flink_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv >>> >>> On 09.02.2021 13:36, Petr Ivanov wrote: Hi, Nikolay. I've created a set of tests for extensions, and part of them are failing with: JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365 » NoSuchMethod java.lang.NoSuchMethodError: org.apache.maven.surefire.report.SimpleReportEntry.withException(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/apache/maven/surefire/report/StackTraceWriter;)Lorg/apache/maven/surefire/report/SimpleReportEntry; at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) Could you check [1] please? [1] https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_RunAllTests/5864907?buildTab=dependencies=list
Re: Ignite Extensions tests
Petr, ticket [1] was merged to the master branch. TC build is ok now - [2]. Sometimes i faced that some tests can be flaky because test nodes were trying to join extra incompatible node that does not belong to the test. But I think we could investigate it in a separate ticket. Could I ask you to create separate test suite for the Spring Cache extension similar to Spring Transactions for the following PR: https://github.com/apache/ignite-extensions/pull/42 [1] - https://issues.apache.org/jira/browse/IGNITE-14150 [2] - https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions_Tests_IgniteExtensions_Tests=%3Cdefault%3E On 10.02.2021 10:40, Petr Ivanov wrote: I've updated Extensions template to use only Linux agents. Will wait for ticket in master, thanks! On 10 Feb 2021, at 01:05, Mikhail Petrov wrote: Hi, Petr. It seems that the problem is in an outdated version of the maven surefire plugin that is used in ignite-extensions. I created the corresponding ticket [1]. I also faced that current ignite-extensions build is broken on windows agents - [2]. It fails with the following error: /[22:47:43]'#!' is not recognized as an internal or external command, [22:47:43]operable program or batch file. [22:47:43]Environment variable -o nounset; set -o errexit; set -o pipefail; set -o errtrace; set -o functrace not defined [22:47:43]Environment variable -x not defined [22:47:43]'rm' is not recognized as an internal or external command, [22:47:43]operable program or batch file. [22:47:43]The syntax of the command is incorrect. [22:47:43]'cp' is not recognized as an internal or external command, [22:47:43]operable program or batch file. [22:47:43]Process exited with code 1/ Could you check it, please? [1] - https://issues.apache.org/jira/browse/IGNITE-14150 [2] - https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Flink_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv On 09.02.2021 13:36, Petr Ivanov wrote: Hi, Nikolay. I've created a set of tests for extensions, and part of them are failing with: JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365 » NoSuchMethod java.lang.NoSuchMethodError: org.apache.maven.surefire.report.SimpleReportEntry.withException(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/apache/maven/surefire/report/StackTraceWriter;)Lorg/apache/maven/surefire/report/SimpleReportEntry; at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) Could you check [1] please? [1] https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_RunAllTests/5864907?buildTab=dependencies=list
