Hi Luiz
The failure is from "test-midi" from the output. However, the current script didn't save the test-suite.log.
I have another test setup on a different account but the test passed on that setup with same patch set. So it could be the false positive as Brian mentioned.
Let me make a change to
- capture/save the "test-suite.log" if there is a failure
Also, I ran again the it passed at the 2nd time.
I will disable the test-midi until we fix this issue.
Regards,
Tedd
On 5/19/20, 2:07 PM, "linux-bluetooth-owner@xxxxxxxxxxxxxxx on behalf of Luiz Augusto von Dentz" <linux-bluetooth-owner@xxxxxxxxxxxxxxx on behalf of luiz.dentz@xxxxxxxxx> wrote:
Hi Tedd,
On Tue, May 19, 2020 at 1:39 PM <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.
> While we are preparing for reviewing the patches, we found the following
> issue/warning.
>
> Test Result:
> makecheck Failed
>
> Outputs:
> ./test-driver: line 107: 14841 Aborted (core dumped) "$@" > $log_file 2>&1
> make[3]: *** [Makefile:9726: test-suite.log] Error 1
> make[2]: *** [Makefile:9834: check-TESTS] Error 2
> make[1]: *** [Makefile:10228: check-am] Error 2
> make: *** [Makefile:10230: check] Error 2
Can you give a look why CI is core dumping here, also perhaps we
should inspect the test-suite.log when this happens.
--
Luiz Augusto von Dentz
