Kevin Hilman <khilman@baylibre.com> writes:

> Neil Williams <codehelp@debian.org> writes:
>
>> On Wed, 28 Nov 2018 18:26:34 +0200
>> Oleksandr Terentiev <oterenti@cisco.com> wrote:
>>
>>> Hi,
>>>
>>> I wasn't able to sign up at https://register.linaro.org/ with the
>>> following message:
>>> "Linaro employees and assignees, and people from Member companies
>>> cannot use this form"
>>
>> In which case, you should be able to sign in to validation.linaro.org
>> yourself using your Linaro LDAP details. If your linaro email address
>> is oleksandr.terentiev@linaro.org, your LDAP username to use with LAVA
>> is oleksandr.terentiev and then your LDAP password. Otherwise, contact
>> Linaro support / your Tech Lead in Linaro.
>>
>> Once logged in, just need to ask an admin to give you submission rights.
>> (JIRA ticket is easiest:
>> https://projects.linaro.org/secure/CreateIssue!default.jspa and select
>> LAB & System Software (LSS) - remember to specify validation.linaro.org
>> as the server you want to access.
>>
>>>
>>> So I uploaded my changes to GitHub:
>>> https://github.com/oterenti/test-definitions/tree/ptest_modify
>>>
>>> If https://validation.linaro.org/scheduler/job/1890442 can be good
>>> example of ptest run
>>> I'd suggest the following test action:
>>>
>>> - test:
>>>      namespace: dragonboard-820c
>>>      name: qcomlt-ptest
>>>      timeout:
>>>        minutes: 160
>>>      definitions:
>>>      - repository: https://github.com/oterenti/test-definitions.git
>>>        from: git
>>>        path: automated/linux/ptest/ptest.yaml
>>>        name: linux-ptest
>>>        branch: ptest_modify
>>>        params:
>>>          EXCLUDE: bluez5 libxml2 parted python strace
>>
>> I tried a couple of test jobs but the first failed trying to fastboot
>> flash and another kernel panicked:
>> https://lkft-staging.validation.linaro.org/scheduler/job/18795
>>
>> See if this one completes - it looks hung to me:
>> https://validation.linaro.org/scheduler/job/1899004
>
> That hang looks similar to the results I see.  After the first ptest
> runs (acl), I see the "b'STOP: ptest-runner'" and then no more
> output[1], then a LAVA timeout.
>
> I'm using the "ptest_modify" branch of the Oleksandr's test-definitions
> repository, and attempting to run a subset of the ptests[2].

And for reference, even trying to run a single ptest (acl)[1], I run
into the same problem.

Kevin

[1] http://lava-baylibre.baylibre:10080/scheduler/job/58187/definition#defline89