From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751540AbdJEPyp (ORCPT ); Thu, 5 Oct 2017 11:54:45 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34808 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751216AbdJEPyn (ORCPT ); Thu, 5 Oct 2017 11:54:43 -0400 Date: Thu, 5 Oct 2017 17:54:41 +0200 From: Sebastian Andrzej Siewior To: Mike Galbraith Cc: Thomas Gleixner , LKML , linux-rt-users , Steven Rostedt Subject: Re: [ANNOUNCE] v4.11.12-rt13 Message-ID: <20171005155441.72mjaac5c42rjilf@linutronix.de> References: <20170905145244.jro4jywfxugmn7eh@linutronix.de> <1507133279.6934.66.camel@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1507133279.6934.66.camel@gmx.de> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote: > Seems combo-patch induced some ltp posix conformance test grumbling. > > +clock_settime_8_1 ... ... FAILED > +clock_settime_4_2 ... ... FAILED > +clock_settime_speculative_4_3 ... ... FAILED > +timer_settime_5_2 ... ... FAILED > +timer_settime_5_1 ... ... FAILED > +timer_settime_5_3 ... ... FAILED > > rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_8-1.run-test > Ended too late. 1507131910 >> 1507131908 > Test FAILED > rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_4-2.run-test > timer should have expired _immediately_ > rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/speculative/clock_settime_speculative_4-3.run-test > Overrun count =0, not # of repeating timer expirys > FAIL: Caught 0 signals, not 1 > Test FAILED > rtbox:/root # /opt/ltp/conformance/interfaces/timer_settime/timer_settime_5-2.run-test > signal was not sent So the last triggers here, too and I have an idea. Sebastian