Alex Shi alex.shi@linaro.org writes:
Kevin, what are you using for remote power reset?
I use USB controlled relays called phidgets[1]
These are USB controlled relays.
Also, http://www.digital-loggers.com/lpc.html I use an old rack-mount version of this.
Thanks the info!
Combined with my pyboot tool[2], automatic bisect is as simple as: git bisect run '(rebuild; pyboot <board>)' and it's fully automated
True. but the value of combine bisect command into one script is that you can use it in another automatic tasks. Like, you can auto trigger the build bisection when the build failed, then find out which commit cause this failure.
I'm doing this already, but it's not integrated into my build/boot reports.
We (kernel team and LAVA team) are actively working on a more thorough kernel CI that can do fast builds (and bisects) so once the infrastructure is in place, the next step is automating the bisect process. Any stuff you already have in place will be very useful.
Further more, you can add more standard ARM testing benchmarks after kernel booted, and then bisect which commit cause a performance/power regression on upstream tree or on next/tip trees.
Yes, LAVA can do all of this as well.
If the job does well, any patch which possibly hurt ARM performance/power will be blocked or fixed. Then you will be a great judge in kernel community represent ARM/Linaro. That is a huge achievement! :)
Completely agree. I can't wait until we get ther.
I'm sure pyboot is better but I have to mention that tools/testing/ktest/ktest.pl also works for automated bisecting.
Someday I really should investigate switching my boot/test scripts to pyboot.
Did you using ktest to do bisecting work? In a short glance, it also just support ssh like connection to target machine.
No, I don't use ktest.
Kevin