From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 1 Dec 2017 17:44:08 -0500 Subject: [U-Boot] [RFC PATCH] test: py: Disable sleep test for qemu targets In-Reply-To: References: <55ea4a9704460aeefaf48b17ed7ab19c8b0285fc.1512139562.git.michal.simek@xilinx.com> <346f23bc-7e7b-6fcb-5f53-8ad674febd60@gmx.de> <9babee0f-f5a8-d66a-db6f-ead7c4ac7dab@xilinx.com> Message-ID: <20171201224408.GV3587@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Dec 01, 2017 at 10:07:54AM -0700, Stephen Warren wrote: > On 12/01/2017 08:19 AM, Michal Simek wrote: > >Hi, > > > >On 1.12.2017 16:06, Heinrich Schuchardt wrote: > >> > >> > >>On 12/01/2017 03:46 PM, Michal Simek wrote: > >>>Qemu for arm32/arm64 has a problem with time setup. > >> > >>Wouldn't it be preferable to fix the root cause? > > > >Definitely that would be the best and IIRC I have tried to convince our > >qemu guy to do that but they have never done that. > > What is the exact failure condition? Is it simply that the test is still > slightly too strict about which delays it accepts, or is sleep outright > broken? > > You can use command-line option -k to avoid some tests. For example "-k not > sleep". That way, we don't have to hard-code the dependency into the test > source. Depending on the root cause (issue in U-Boot, or issue in just your > local version of qemu, or something that will never work) this might be > better? Even with the most recent relaxing of the sleep test requirements, I can still (depending on overall system load) have 'sleep' take too long, on QEMU. I think it might have been half a second slow, but I don't have the log handy anymore. Both locally and in travis we -k not sleep all of the qemu instances. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: