[PATCH] Archive test traces to outer directory named by build number after lldb-test
Ying Chen
chying at google.com
Fri May 1 17:56:43 PDT 2015
Hi chaoren, vharron, sivachandra,
The test traces will be stored temporarily on slave machine
There will be a sheduled task running on slave machine to zip and upload traces to google storage
http://reviews.llvm.org/D9453
Files:
zorg/buildbot/builders/LLDBBuilder.py
Index: zorg/buildbot/builders/LLDBBuilder.py
===================================================================
--- zorg/buildbot/builders/LLDBBuilder.py
+++ zorg/buildbot/builders/LLDBBuilder.py
@@ -296,6 +296,14 @@
workdir='%s' % llvm_builddir,
env=testenv))
f=cleanSVNSourceTree(f, '%s/tools/lldb' % llvm_srcdir)
+ # After test, move test traces to outer folder
+ # Those test traces will accumulate on slave machine until being cleaned up manully or by script
+ f.addStep(ShellCommand(name="archive test traces",
+ command=WithProperties('mkdir -p ../testtraces/build-%(buildnumber)s && mv lldb-test-traces-* ../testtraces/build-%(buildnumber)s/'),
+ description="archive test traces ",
+ haltOnFailure=False,
+ env=env,
+ workdir='%s' % llvm_builddir))
return f
# Define a structure to describe remote target
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D9453.24849.patch
Type: text/x-patch
Size: 1051 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150502/5359e01d/attachment.bin>
More information about the llvm-commits
mailing list