Re: [MTCGA]: new failures in builds [2123440] needs to be handled
All, We had to revert the commit because the fix appeared to be more complex than we expected. Tests should be ok now. вт, 23 окт. 2018 г. в 11:20, Alexey Goncharuk : > Hi all, > > We are working on the fix, it should be merged to master asap. > > вт, 23 окт. 2018 г. в 11:18, Maxim Muzafarov : > >> Hello, >> >> Are there any updates? >> The build constantly fails with `Execution timeout` in the master branch >> since October 20. >> >> The problem commit supposed to be related to the [2] issue and I think the >> probable `IgniteSqlSplitterSelfTest#testPushDown` test fails with >> excpetion: >> >> class org.apache.ignite.binary.BinaryObjectException: Failed to register >> class. >> at >> >> org.apache.ignite.internal.binary.BinaryContext.registerUserClassName(BinaryContext.java:1249) >> at >> >> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:798) >> at >> >> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:775) >> >> and the whole suite hungs. >> >> [1] >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E >> [2] https://issues.apache.org/jira/browse/IGNITE-5795 >> >> On Sun, 21 Oct 2018 at 08:30 Павлухин Иван wrote: >> >> > Hi Anton, >> > >> > I ran a problematic build against my contribution [1] and it seems to >> pass >> > fine. Then I ran the build against your PR branch and it hanged [2]. >> > There is nothing surprising that it fired only in master because the >> build >> > was added to RunAll after your PR runs. >> > Could you please take a look? >> > >> > [1] https://ci.ignite.apache.org/viewLog.html?buildId=2127238; >> > [2] >> > >> > >> https://ci.ignite.apache.org/viewLog.html?buildId=2127232=buildResultsDiv=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries >> > >> > сб, 20 окт. 2018 г. в 10:30, : >> > >> > > 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 Queries (Binary Objects Simple >> > > Mapper) >> > > >> > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=%3Cdefault%3E=buildTypeStatusDiv >> > > Changes may lead to failure were done by >> > > - kaa.dev >> > > >> > >> http://ci.ignite.apache.org/viewModification.html?modId=835798=false >> > > - vololo100 >> > > >> > >> http://ci.ignite.apache.org/viewModification.html?modId=835794=false >> > > >> > > - 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 10:30:43 20-10-2018 >> > > >> > >> > >> > -- >> > Best regards, >> > Ivan Pavlukhin >> > >> -- >> -- >> Maxim Muzafarov >> >
Re: [MTCGA]: new failures in builds [2123440] needs to be handled
Hi all, We are working on the fix, it should be merged to master asap. вт, 23 окт. 2018 г. в 11:18, Maxim Muzafarov : > Hello, > > Are there any updates? > The build constantly fails with `Execution timeout` in the master branch > since October 20. > > The problem commit supposed to be related to the [2] issue and I think the > probable `IgniteSqlSplitterSelfTest#testPushDown` test fails with > excpetion: > > class org.apache.ignite.binary.BinaryObjectException: Failed to register > class. > at > > org.apache.ignite.internal.binary.BinaryContext.registerUserClassName(BinaryContext.java:1249) > at > > org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:798) > at > > org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:775) > > and the whole suite hungs. > > [1] > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E > [2] https://issues.apache.org/jira/browse/IGNITE-5795 > > On Sun, 21 Oct 2018 at 08:30 Павлухин Иван wrote: > > > Hi Anton, > > > > I ran a problematic build against my contribution [1] and it seems to > pass > > fine. Then I ran the build against your PR branch and it hanged [2]. > > There is nothing surprising that it fired only in master because the > build > > was added to RunAll after your PR runs. > > Could you please take a look? > > > > [1] https://ci.ignite.apache.org/viewLog.html?buildId=2127238; > > [2] > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=2127232=buildResultsDiv=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries > > > > сб, 20 окт. 2018 г. в 10:30, : > > > > > 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 Queries (Binary Objects Simple > > > Mapper) > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=%3Cdefault%3E=buildTypeStatusDiv > > > Changes may lead to failure were done by > > > - kaa.dev > > > > > > http://ci.ignite.apache.org/viewModification.html?modId=835798=false > > > - vololo100 > > > > > > http://ci.ignite.apache.org/viewModification.html?modId=835794=false > > > > > > - 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 10:30:43 20-10-2018 > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > -- > -- > Maxim Muzafarov >
Re: [MTCGA]: new failures in builds [2123440] needs to be handled
Hello, Are there any updates? The build constantly fails with `Execution timeout` in the master branch since October 20. The problem commit supposed to be related to the [2] issue and I think the probable `IgniteSqlSplitterSelfTest#testPushDown` test fails with excpetion: class org.apache.ignite.binary.BinaryObjectException: Failed to register class. at org.apache.ignite.internal.binary.BinaryContext.registerUserClassName(BinaryContext.java:1249) at org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:798) at org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:775) and the whole suite hungs. [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E [2] https://issues.apache.org/jira/browse/IGNITE-5795 On Sun, 21 Oct 2018 at 08:30 Павлухин Иван wrote: > Hi Anton, > > I ran a problematic build against my contribution [1] and it seems to pass > fine. Then I ran the build against your PR branch and it hanged [2]. > There is nothing surprising that it fired only in master because the build > was added to RunAll after your PR runs. > Could you please take a look? > > [1] https://ci.ignite.apache.org/viewLog.html?buildId=2127238; > [2] > > https://ci.ignite.apache.org/viewLog.html?buildId=2127232=buildResultsDiv=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries > > сб, 20 окт. 2018 г. в 10:30, : > > > 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 Queries (Binary Objects Simple > > Mapper) > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=%3Cdefault%3E=buildTypeStatusDiv > > Changes may lead to failure were done by > > - kaa.dev > > > http://ci.ignite.apache.org/viewModification.html?modId=835798=false > > - vololo100 > > > http://ci.ignite.apache.org/viewModification.html?modId=835794=false > > > > - 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 10:30:43 20-10-2018 > > > > > -- > Best regards, > Ivan Pavlukhin > -- -- Maxim Muzafarov
Re: [MTCGA]: new failures in builds [2123440] needs to be handled
Hi Anton, I ran a problematic build against my contribution [1] and it seems to pass fine. Then I ran the build against your PR branch and it hanged [2]. There is nothing surprising that it fired only in master because the build was added to RunAll after your PR runs. Could you please take a look? [1] https://ci.ignite.apache.org/viewLog.html?buildId=2127238; [2] https://ci.ignite.apache.org/viewLog.html?buildId=2127232=buildResultsDiv=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries сб, 20 окт. 2018 г. в 10:30, : > 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 Queries (Binary Objects Simple > Mapper) > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries=%3Cdefault%3E=buildTypeStatusDiv > Changes may lead to failure were done by > - kaa.dev > http://ci.ignite.apache.org/viewModification.html?modId=835798=false > - vololo100 > http://ci.ignite.apache.org/viewModification.html?modId=835794=false > > - 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 10:30:43 20-10-2018 > -- Best regards, Ivan Pavlukhin
