Re: Signal timing problems in python testsuite

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 1/25/21 8:27 PM, Helge Deller wrote:
> On 1/23/21 4:39 PM, Rolf Eike Beer wrote:
>> The Python testsuite in all versions of Python3 I remember fails the eintr
>> tests with output like this:
>>
>> FAIL: test_poll (__main__.SelectEINTRTest)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>>   File "/usr/lib/python3.9/test/eintrdata/eintr_tester.py", line 451, in
>> test_poll
>>     self.assertGreaterEqual(dt, self.sleep_time)
>> AssertionError: 0.19999999995343387 not greater than or equal to 0.2
>
> There have been some changes in the generic timekeeping functions.
> I see timing issues on a few of my machines too, e.g. in the xor
> time measurement functions as reported at lkml.

One more idea:
You could try to enable CONFIG_DEBUG_TIMEKEEPING.


>
>> There are 2 more failing tests with likewise output. This happens on my 4-core
>> C8000. I have attached the testcase, when running it with "python3
>> test_eintr.py" I also get that results.
>>
>> I suspect this could be some cross-cpu clock scew, but of course it can be
>> something entirely different. Could someone have a look what is up there?
>> Kernel is currently 5.10.4, but this has been there for a while.
>>
>> Eike
>>
>
>





[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux