[Lldb-commits] New llvm build server account request

Tue Oct 20 15:50:27 PDT 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Where can I find this updateScripts.sh? It's missing under your link:

https://android.googlesource.com/platform/external/lldb-utils/+/lldb-mas
ter-dev/buildbotScripts/bashShell/svntotbuild/

On 21.10.2015 00:29, Ying Chen wrote:
> Hello Kamil, Galina,
> 
> If you would like to build LLDB with cmake and ninja, I suggest to 
> consider the following two factory functions. Depends on what you
> described, I feel the first one works better for you.
> 
> 1. getLLDBUbuntuCMakeBuildFactory If you only run local lldb tests,
> this is the factory to use.
> 
> For example, if you would like to build host lldb with clang and
> Release config, and run tests with clang on x86_64 host, then call
> the function this way,
> 
> getLLDBUbuntuCMakeBuildFactory(build_compiler = "clang", build_type
> = "Release", local_test_archs=["x86_64"], 
> local_test_compilers=["clang"]) If you would like to run local
> tests with gcc compiler as well, then pass
> local_test_compilers=["clang", "gcc"]
> 
> Dependency: You need to have the required packages to build lldb.
> 
> Note*: please disable the last step in this function 
> "archiveLLDBTestTraces", this steps will upload the log files to a
> cloud storage that you might not have access to.
> 
> 2. getLLDBScriptCommandsFactory
> 
> If you have multiple targets to run tests against, for example,
> remote linux, remote android targets and etc, you should choose
> this factory. The advantage of this factory is that it calls a
> script in each step, so it's highly configurable and easy to make
> changes. You just need to make sure the scripts are in builder
> machine and have the correct commands. For your reference, the ones
> that we're currently using could be found here. 
> https://android.googlesource.com/platform/external/lldb-utils/+/lldb-m
aster-dev/buildbotScripts/bashShell/svntotbuild/
>
> 
updateScript as the first step, is just copy the scripts to local builde
rs.
> 
> Please let me know if you have further questions.
> 
> Thanks, Ying
> 
> 
> On Tue, Oct 20, 2015 at 1:46 PM, Kamil Rytarowski <n54 at gmx.com 
> <mailto:n54 at gmx.com>> wrote:
> 
> Hello Ying,
> 
> I'm in trouble with my attempts to connect my NetBSD/amd64 machine
> to the LLDB/LLVM build zone.
> 
> My host is NetBSD-7.0 (with buildslave ID:
> lldb-amd64-ninja-netbsd7). I use pkgsrc (2015Q3) to ship packages.
> I'm attaching a list of installed ones to this mail.
> 
> I talked with Joerg and it was decided to go for CMake and Ninja,
> we don't want to change it for now (at least till single machine
> will be plugged in).
> 
> Please try to spawn local NetBSD session and connect to the
> staging buildbot and debug it locally, to cut the number of
> iterations between me and the Galina.
> 
> I'm adding here a short tutorial to get to reproduce quickly the
> setup of mine. It will take you like 2-5 minutes to get into
> installed system (depends of an internet connection).
> 
> 1. Prepare a disk image. $ qemu-img create -f qcow2 netbsd7.0_amd64
> 10G
> 
> 2. Get an installation media. $ $FETCH_TOOL 
> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.0/amd64/installation/cdrom/bo
ot
>
> 
- -com.iso
> 
> 3. Spawn installation $ qemu-system-x86_64 \ -enable-kvm \ -net
> user \ -m 2G \ -cdrom boot-com.iso \ -nographic \ -smp cores=2 \ 
> -hda netbsd7.0_amd64 \ -boot d
> 
> 4. Inside the installer push ctrl-c and get the command line.
> 
> 5. Setup network connection: # dhcpcd
> 
> 6. Go to a writable dir, like /tmp # cd /tmp
> 
> 7. Fetch the autoinst.sh script of mine # ftp
> ftp://ftp.netbsd.org/pub/NetBSD/misc/kamil/autoinst.sh
> 
> # sh autoinst.sh -s 128 -r mypass -c com0 -C 9600 -p wd0
> 
> (take a coffee break)
> 
> 8. If everything went OK, just type: # poweroff
> 
> 9. Start your newly installed system qemu-system-x86_64 \ 
> -enable-kvm \ -net user \ -m 2G \ -nographic \ -smp cores=2 \ -hda
> netbsd7.0_amd64 \ -boot c (root password is empty)
> 
> 10. Install dependencies from pkgsrc, like: # cd
> /usr/pkgsrc/devel/cmake && make install
> 
> Please install packags needed for buildslave, create dedicated
> user and try to connect it to the salve.
> 
> Thank you in advance,
> 
> On 20.10.2015 21:40, Galina Kistanova wrote:
>> Hello Kamil,
> 
>> It looks like you are missing dependencies for the LLDB builder 
>> you have chosen. 
>> http://lab.llvm.org:8014/builders/lldb-amd64-ninja-netbsd7/builds/75/
s
>
>> 
teps/update%20scripts/logs/stdio
> <http://lab.llvm.org:8014/builders/lldb-amd64-ninja-netbsd7/builds/75/
s
>
> 
teps/update%20scripts/logs/stdio>
> 
> 
> 
> The getLLDBScriptCommandsFactory build factory does not document
>> the assumed dependency, so you may want to contact Ying Chen,
>> who is the author for the complete list of dependencies.
> 
>> Another thing you may want to do is to reconsider the builder
>> you want to use. Maybe LLDBBuilder.getLLDBBuildFactory would
>> work better for you, though it requires autoconfig and make.
> 
>> I'm adding the LLDB mail list in case somebody has an idea of
>> what would be the easiest way to get the NetBSD builder for LLDB
>> up and running.
> 
>> Hello everyone,
> 
>> Kamil is on the mission of getting LLDB builder for NetBSDwhich 
>> would build clang+LLVM, then LLDB and run tests. What is the 
>> shortest and less painful route there? Any suggestions? Just 
>> looking at the source code of the current set of the LLDB
>> builders, it is hard to tell which one is the "main".
> 
>> Thanks
> 
>> Galina
> 
> 
> 
> 
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWJsUwAAoJEEuzCOmwLnZs0swP/jYtjilLMNrqvLhgIrqRGPOF
TyJ0Davl9OvB5eABlTAPMEtKt73c5hwFSj+oO6UkAAcpRBcF098DDP6ZNoLCKFag
KEpg7HR5mc8FzHNvv4xlTAMJL0JnQU9Qoa0V4PbeRJn51g/Ul8TyeTFL5mzbMzUN
y3qPN2ragyUbV86zkK8dPPQrSdagwY8+xnEGXfMnCF1hUKjNNu7z6cbXIKMypIym
RJyZ8gPe7s+VwLt9byGRkJVfhCeniFNuUyi0V0NHQxwgInPrUnZUPzu9jjZOOX8z
GITDTBtGRI/bWB8xDxMaRLnYO1DDDU2mxriggu2XbbQ8u7qlAgu7bUu1BCVzYTz+
vgnm4ZaHkI4ozc/Tf8wv1UwLUTS0SjnDDcGP/ctDZxdxmktqCNk4ympUazyUjQgF
+BWA9+tS6OKV3alQJEjt7RbbrGPj1bsS9FXc1HkmOOV8IMXD2RFplImNLAnsyZek
34Fw4citgYtIVxIpQIa9+Tpz6XKfa1EVp2LIwcaqVX9wgNwMPeBVYkJcqKdXv30Q
NoLX61Zt1aSKXgBlVireEOf8UMEKrwHGRD5gmpXfKNV8gU4CJOmEarxCQqcLttUh
oMpVqEqWDX93OEVBg31S5JTiKTTTYjHNQMhk8KUSHI8sKmM89KbtMYPwnbxVzEhg
0qG3hc6sGChno9l6WnRX
=XiFI
-----END PGP SIGNATURE-----