Thank you very much! If it's the case of what you said, a merge from latest main to this branch will fix this issue?
Thanks, Ken Cheng On Thu, Jul 12, 2018 at 6:16 PM Dmitry Pavlov <dpavlov....@gmail.com> wrote: > Hi, > > I've checked this results and I guess branch was created at some unlucky > moment, and currently most of timeouts were fixed in master. > > "No changes" mean Teamcity does not detected changes between runs. Probably > I've scheduled re-run for some particular suites more than one time. > > I'll take a look to PR itself. > > Sincerely, > Dmitriy Pavlov > > чт, 12 июл. 2018 г. в 11:39, kcheng.mvp <kcheng....@gmail.com>: > > > Here is the latest TC result > > > > > > The high-lighted part shows as "no changes", which mean my changes would > > not cause the failure, right? > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1480732&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll > > <http://apache-ignite-developers.2346864.n4.nabble.com/file/t85/tc.png> > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
