On Tue, Nov 22, 2011 at 11:03 PM, Andrew Stubbs <andrew.stu...@linaro.org> wrote: > On Mon 21 Nov 2011 21:26:03 GMT, Michael Hope wrote: >>> >>> Took Michael's rootfs that is used for all the toolchain testing and >>> benchmarking, unpacked it, and repacked it so that it is compatible with >>> "linaro-media-create", then tested that I could use it to run tests on >>> LAVA >>> successfully. I was hoping to use this for extra benchmarking bandwidth, >>> but >>> there's a permissions problem in the LAVA website software that means >>> it's >>> not yet possible to post private results to the system, so no proprietary >>> benchmarks yet. I can still continue pipe-cleaning my process, and maybe >>> run >>> some benchmarks without actually reporting the results (or perhaps >>> posting >>> them somewhere write-only). >> >> We can rsync them to the validation machine as a step and only post a >> summary, such as the number of regressions or improvements, to LAVA. > > Yeah, I've investigated pushing the private results to people.linaro.org, > but to do so would require exposing an encryption key, and p.l.o does not > permit use of .ssh/authorized_keys so I can't create a restricted one for > the purpose. I could upload them to my home server, but that doesn't help > anyone else. I could set something up to receive write-only file drops on > p.l.o with a non-standard port number (if there's no firewall), but it might > be harder to encrypt it, though that might not matter.
There's a machine on the same network with a role based account. We can push to there and use a password-less key with host authenticatation and anything else that we can come up with to make up for the lack of password :) Or perhaps a write-only rsyncd would be better? -- Michael _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
