Hello, As far as I can tell, LAVA currently doesn't set hostname of a LAVA board when running tests, which leads for usage of whatever generic (or random) value was configured in build image. That may pose problem if test/build uses hostname for some logging or identification.
For example, CBuild included hostname in build result id, based on which various logs and result bundles are named, and which then gets parsed by CBuild frontend to display build results. So, we got confusing and inconsistent results from LAVA builds. I so far worked that around by setting CBuild/LAVA builds' hostname to "lava", but that doesn't match how native CBuild builds work, for example, http://cbuild.validation.linaro.org/helpers/buildlog page shows build matrix per individual board, based on hostname. I tried to investigate how it happened that lava-dispatcher doesn't try to set hostname, and actually found it used to, but that was tied to recognition of test prompts, and once that was refactored, setting hostname also gone, see http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/revision/402 (grep for "_customize_ubuntu" - it got factored out to another file, and lost /etc/hostname setting in progress). So, please let me know if the above makes sense, and should be files as lava-dispatcher bug, or are there other reasons for not setting a hostname. Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
