[lldb-dev] New build machine in the cluster lldb-amd64-ninja-netbsd8
Pavel Labath via lldb-dev
lldb-dev at lists.llvm.org
Mon Apr 24 02:42:35 PDT 2017
On 22 April 2017 at 23:57, Kamil Rytarowski via lldb-dev <
lldb-dev at lists.llvm.org> wrote:
> Hello,
>
> I'm in process of attaching new build machine lldb-amd64-ninja-netbsd8.
>
> It will run prerelease of NetBSD/amd64 8.0 (as of today 7.99.70) with
> the GNU toolchain.
>
> Once the new one setup will be in operation, I will upgrade the old one
> to 7.99.70 (& retain the same name), switch the to the staging cluster
> http://lab.llvm.org:8014/ and turn on execution of tests.
>
> Am I right that in order to turn tests I need to switch "runTest=False"
> to "runTest=True" in buildbot/osuosl/master/config/builders.py?
>
Affirmative.
As you are using the "scripted" build factory, you'll also need to create a
test_cfg.json in your scripts folder on the build slave, which describes
the kind of tests you want to run:
For example, the linux build bot has this in the file:
{
"test1": "local,clang-3.5,i386",
"test2": "local,clang-3.5,x86_64",
"test3": "local,totclang,i386",
"test4": "local,totclang,x86_64",
"test5": "local,/lldb-buildbot/bin/gcc-4.9.2/bin/gcc,i386",
"test6": "local,/lldb-buildbot/bin/gcc-4.9.2/bin/gcc,x86_64"
}
but a single test line would probably be enough for you.
Then, the master will invoke a script "test.sh" with the test config
argument: (e.g., ./test.sh local,clang-3.5,i386) and your script should run
the tests.
let me know if you run into problems,
pl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170424/adbb0aa5/attachment.html>
More information about the lldb-dev
mailing list