[lldb-dev] New build machine in the cluster lldb-amd64-ninja-netbsd8

[Kamil Rytarowski via lldb-dev]

I've managed to configure lldb-amd64-ninja-netbsd7 to run the unit
tests. There has been observed a regression as the number of passing
ones dropped recently from 600+/1200+ to 200+. I've reproduced this also
locally.

http://lab.llvm.org:8014/builders/lldb-amd64-ninja-netbsd7/builds/75

I'm still using google scripts. I think we should drop "upload test
traces" on !Google platforms.

Long term I'm planning to prepare my own set of scripts customized for
NetBSD. I'm evaluation inclusion LLVM and Clang tests in execution to
maximize usage of the new buildbot. Perhaps I will be able to spare my
time on it around September.

For now I will try to mark failing ones with expected failure and file
Bugzilla bugs for them. I'm going to turn on tests on
lldb-amd64-ninja-netbsd8.

On 28.04.2017 13:15, Pavel Labath wrote:
> Indeed,  master restart is needed every time you update the zorg repository.
> 
> cheers,
> pl
> 
> On 28 April 2017 at 03:40, Kamil Rytarowski <n54 at gmx.com> wrote:
>> On 24.04.2017 11:42, Pavel Labath wrote:
>>>
>>>
>>> On 22 April 2017 at 23:57, Kamil Rytarowski via lldb-dev
>>> <lldb-dev at lists.llvm.org <mailto: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
>>
>> lldb-amd64-ninja-netbsd8 [kernel ABI version 7.99.70] is up and running
>>
>> lldb-amd64-ninja-netbsd7 has been upgraded to 7.99.70 and restarted
>>
>> I switched the old machine to the staging buildfarm, set runTest=True in
>> buildbot/osuosl/master/config/builders.py and added the following
>> test_cfg.json:
>>
>> $ cat ./build/build/test_cfg.json
>> {
>>     "test1": "local,gcc,x86_64",
>> }
>>
>> As of now it does not attempt to run the regression tests. Perhaps we
>> need to restart buildmaster configuration? I will ask Galina for it.
>>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170429/f0ae3a15/attachment-0001.sig>