Ok, I will see if I can split and/or reduce the Travis test jobs. These are not covering full regression checks anyway and are just indicators to the most blatant errors in PRs. We'll need to get to a more minimal set of functionality to include in such a first scan.
bilingual spellchecker used, read at your own risk. On Sat, 6 Apr 2019, 11:59 Nikolaos Dalezios, <dale...@gmail.com> wrote: > I also have noticed this issue with travis tests. After my first PR travis > was failing in the first test but all the local mvn tests were passed. > After a PR update travis is now failing at test 7. Specifically the test > isn' failing it times out but cannot figure it out > > On Fri, Apr 5, 2019, 14:59 Rafael Weingärtner <rafaelweingart...@gmail.com > > > wrote: > > > It is probably a concurrency problem on the test side. > > I had a similar problem a long time ago with > > "*smoke*/*test_primary_storage*". > > That is one of the reasons why this test is there on its own. > > > > On Fri, Apr 5, 2019 at 8:54 AM Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > LS, > > > Lately travis tests show more and more random failures. somtimes these > > > succeed on stuborn retry but lately these are getting more persistent. > > > Especially job .7 is hard to get past/passed. I am very irritated and > > > looking for ways to resolve this without just ignoring. > > > Is there anybody here that has a clear view on shat is happening? I > heard > > > say ubuntu verion and travis traffic increasing. > > > Does anybody know if splitting the runs further is possible and/or > > useful? > > > > > > thanks and kind regards, > > > -- > > > Daan > > > > > > > > > -- > > Rafael Weingärtner > > >
