*** lchlan_ has joined #cip | 03:04 | |
*** rjek has joined #cip | 03:07 | |
*** rjek_ has quit IRC | 03:11 | |
*** lchlan has quit IRC | 03:11 | |
*** lchlan_ is now known as lchlan | 03:12 | |
*** patersonc has joined #cip | 07:01 | |
*** rajm has joined #cip | 07:11 | |
rajm | another day, another successful BBB health check | 07:48 |
---|---|---|
*** toscalix has joined #cip | 07:52 | |
* rajm closes issue #18 | 08:13 | |
patersonc | Happy days | 08:16 |
rajm | things may slow down a bit now, starts the day gently.... | 08:30 |
*** mturquette has quit IRC | 08:44 | |
*** mturquette has joined #cip | 08:44 | |
*** kristerman has joined #cip | 09:07 | |
patersonc | toscalix: It looks like our firewall blocks Hangouts. I'll try and get it resolved for next week! | 10:03 |
toscalix | I will prepare next week plan B also which willl be appear.in | 10:04 |
toscalix | in case you cannot make it | 10:04 |
patersonc | appear.in is also blocked, I tried last week ;) | 10:04 |
patersonc | I'll sort the issues out with our IT, no need to change everything just for me. | 10:04 |
patersonc | Let me know if you have any testing queries for today's meeting. | 10:05 |
toscalix | patersonc: testing queries? I do not understand | 10:47 |
patersonc | toscalix: Just things relating to the meeting | 10:50 |
toscalix | ah, we are having issues using lava-ci | 10:50 |
toscalix | we will use lava-tool to see if the issues reproduce | 10:50 |
toscalix | with the outcome we will try to come back upstream | 10:50 |
toscalix | if the issue persist | 10:51 |
patersonc | Okay, thanks. | 10:51 |
patersonc | FYI, my colleagues have successfully run the healthcheck and ramdisk tests on the BBB, using the USB cable method to connect. | 10:51 |
toscalix | rajm: where are you tracing this issue? | 10:51 |
toscalix | tracking | 10:51 |
rajm | About to put something in #20 but may be that's misnomered - renamit it or add another issue? | 10:53 |
rajm | updates #20 anyway | 10:56 |
toscalix | I think we should have a different ticket for lava-tool | 11:00 |
toscalix | once you crerate it, I will add cross references | 11:00 |
* rajm does so | 11:00 | |
toscalix | patersonc: \o/ | 11:01 |
rajm | good news patersonc ! | 11:05 |
rajm | toscalix I've opened https://gitlab.com/cip-project/testing/issues/76 | 11:06 |
toscalix | going over it, thanks | 11:06 |
patersonc | Next step is to recreate with the RZ/G | 11:07 |
rajm | on fire this morning (not literally ;-)) | 11:08 |
toscalix | patersonc: great | 11:08 |
rajm | I've removed my last comment from #20 it was misformatted with <> conent not appearing and is now covered in new ticket | 11:12 |
toscalix | agree | 11:14 |
*** rajm has quit IRC | 11:28 | |
*** rajm has joined #cip | 12:51 | |
rajm | ah better eyesight after lunch and spots https rather than http - now token added successfully | 13:21 |
toscalix | do you see now the results? | 13:38 |
rajm | I see 5(!) - that's what I submitted - jobs in the lava i/f - just need to get them to run | 13:44 |
toscalix | well, that is a good step forward | 13:46 |
rajm | agrees!! | 13:49 |
rajm | The qemu ones appear to sit in the queue - I nicked/shared the script from https://validation.linaro.org/static/docs/v2/explain_first_job.html a little light editing to point to my local build and the beaglebone-black device I've got the job run - dies with a python traceback added to #76 | 14:16 |
rajm | ah of course the qemu device is marked as offline so it's not running the tests I add until it is | 14:28 |
rajm | And I've submitted the bbb health check job via lava-user and that runs through to a successful conclusion | 14:50 |
toscalix | yay | 14:53 |
rajm | now putting the qemu device online to see those queued jobs running (I hope) | 14:56 |
rajm | :-) \o/ | 15:07 |
toscalix | olé | 15:09 |
toscalix | oooooolééééé | 15:10 |
rajm | so do we need lava-ci - or are there things I'm missing? submission queue now empty - all the qemu jobs failed but that's not really the point | 15:12 |
toscalix | rajm: do you understand what is really for? | 15:26 |
toscalix | I haven't found the docu that explains what is for (that I understand) | 15:27 |
toscalix | I should check the history of the lava-users ML though | 15:27 |
*** patersonc has quit IRC | 15:28 | |
rajm | "what is really for?" - what lava-ci is really for? | 15:28 |
rajm | if so - I can't get it to really run anything so hard to tell! | 15:29 |
toscalix | :-) | 15:32 |
rajm | I've just tried - with lava-ci running the bbb health check (I was running a random test before) and that still appears to submit but disappears without trace | 15:34 |
rajm | s/with lava-ci running the /with lava-ci; running the / | 15:34 |
toscalix | lava-ci needs to be the tool to create lava boot tests jobs, but that is my guess. I only find https://github.com/kernelci/lava-ci | 15:36 |
toscalix | ... the tools... | 15:37 |
rajm | yes that's where I'm getting it from - but I thought the boot tests are what are done in the health check - though we need to point it at the build area | 15:37 |
rajm | but that's for tomorrow! | 15:38 |
toscalix | good afternoon | 15:38 |
rajm | I've updated #76 to include the lava-tool commands I ran | 15:39 |
rajm | thank you - good afternoon too! | 15:39 |
*** rajm has quit IRC | 15:49 | |
*** mturquette has quit IRC | 16:35 | |
*** kristerman has quit IRC | 16:39 | |
*** mturquette has joined #cip | 16:43 | |
*** toscalix has quit IRC | 17:51 | |
*** donbrown has quit IRC | 18:42 | |
*** donbrown has joined #cip | 21:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!