Hi Hans, On Wed, Mar 2, 2022 at 8:52 AM Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > > Hi, > > On 3/2/22 15:09, bluez.test.bot@xxxxxxxxx wrote: > > This is automated email and please do not reply to this email! > > > > Dear submitter, > > > > Thank you for submitting the patches to the linux bluetooth mailing list. > > This is a CI test results with your patch series: > > PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=619579 > > > > ---Test result--- > > > > Test Summary: > > CheckPatch PASS 1.68 seconds > > GitLint PASS 0.97 seconds > > SubjectPrefix PASS 0.85 seconds > > BuildKernel PASS 36.20 seconds > > BuildKernel32 PASS 31.72 seconds > > Incremental Build with patchesPASS 43.70 seconds > > TestRunner: Setup PASS 564.00 seconds > > TestRunner: l2cap-tester PASS 15.37 seconds > > TestRunner: bnep-tester PASS 7.22 seconds > > TestRunner: mgmt-tester PASS 117.53 seconds > > TestRunner: rfcomm-tester FAIL 9.09 seconds > > TestRunner: sco-tester PASS 8.99 seconds > > TestRunner: smp-tester PASS 8.92 seconds > > TestRunner: userchan-tester PASS 7.47 seconds > > > > Details > > ############################## > > Test: TestRunner: rfcomm-tester - FAIL - 9.09 seconds > > Run test-runner with rfcomm-tester > > Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0 > > > > Failed Test Cases > > Basic RFCOMM Socket Client - Write 32k Success Failed 0.188 seconds > > This seems like a false-positive failure, since I don't > see anyway how this patch can cause this issue. Its a known problem, CI is running against bluetooth-next.git while the fix for this is on our stable bluetooth.git, once bluetooth-next.git gets rebased this should go away. -- Luiz Augusto von Dentz
