Hi Alex, I reviewed your patch and the results and looks good, I will send a PR to the master repo.
Regards, Anibal On Wed, 12 Dec 2018 at 09:32, Oleksandr Terentiev -X (oterenti - GLOBALLOGIC INC at Cisco) <otere...@cisco.com> wrote: > Hi, > It seems that I'm able to provide an example of the LAVA test run to see > the actual results. > https://validation.linaro.org/scheduler/job/1900356 > But the thing is when we analyze each test, LAVA generates bigger output > and it causes 502 Proxy Error as there are 5586 tests. > Anyway, you can see the results: > https://validation.linaro.org/results/1900356 > The final patch is here: > > https://github.com/oterenti/test-definitions/commit/652b14c7683e9ed2978da1aac8db7ffe55603bcf > > Regards, > Alex > > -----Original Message----- > From: Kevin Hilman [mailto:khil...@baylibre.com] > Sent: Thursday, November 29, 2018 9:06 PM > To: Anibal Limon; Oleksandr Terentiev -X (oterenti - GLOBALLOGIC INC at > Cisco) > Cc: codeh...@debian.org; Nicolas Dechesne; > linaro-validation@lists.linaro.org; xe-linux-external(mailer list) > Subject: Re: [Linaro-validation] ptest.py script seems to generate not > really informative results > > Anibal Limon <anibal.li...@linaro.org> writes: > > > On Wed, 28 Nov 2018 at 17:48, Kevin Hilman <khil...@baylibre.com> wrote: > > > >> Kevin Hilman <khil...@baylibre.com> writes: > >> > >> > Neil Williams <codeh...@debian.org> writes: > >> > > >> >> On Wed, 28 Nov 2018 18:26:34 +0200 > >> >> Oleksandr Terentiev <otere...@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.terent...@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. > >> > > > > Same problem here gets stalled after ACL, > > > > https://validation.linaro.org/scheduler/job/1899050 > > > > And this continues same run without changes, > > > > https://validation.linaro.org/scheduler/job/1899052 > > Continues to run further, but still fails with > > "Test error: lava-test-shell timed out after 6410 seconds" > > Kevin > >
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation
