On Fri, Mar 31, 2017 at 3:39 PM, Maxim Uvarov
wrote:
> tm test fails time to time in Travis environment. Because
> of we can not control that machine we can not do things like
> taskset and core isolation there. So simple run test and ignore
> it's result. Threat only segfault as actual error. Li
On 04/18/17 22:26, Bill Fischofer wrote:
> Do I understand this patch correctly that it attempts to run the test
> and if it fails for any reason other than a segfault and we are running
> in Travis that it is then just ignored? That seems reasonable.
>
yes. that is the goal. Run test to make cod
Do I understand this patch correctly that it attempts to run the test and
if it fails for any reason other than a segfault and we are running in
Travis that it is then just ignored? That seems reasonable.
On Tue, Apr 18, 2017 at 11:27 AM, Maxim Uvarov
wrote:
> ping. If people do not want to see
ping. If people do not want to see any entries for CI env in test suite
code then I can make this patch be applied on each Travis run. If it's good
I need a review. Some times this test fails.
On 6 April 2017 at 17:39, Maxim Uvarov wrote:
> Please review this patch. TM very often fails in Travis
Please review this patch. TM very often fails in Travis CI. This patch has
to fix it.
Maxim.
On 31 March 2017 at 23:39, Maxim Uvarov wrote:
> tm test fails time to time in Travis environment. Because
> of we can not control that machine we can not do things like
> taskset and core isolation the
tm test fails time to time in Travis environment. Because
of we can not control that machine we can not do things like
taskset and core isolation there. So simple run test and ignore
it's result. Threat only segfault as actual error. Linaro CI
will still do full test.
https://bugs.linaro.org/show_b
