Archive test traces to outer directory named by build number after lldb-test

[chying]

Summary

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

[sivachandra]

zorg/buildbot/builders/LLDBBuilder.py

306

The summary note says that a separate task would zip and upload traces to google storage. Why cant it be done inline right here as part of this step?

[chying]

zorg/buildbot/builders/LLDBBuilder.py

306

There were two concerns behind this, one is that certain builder might not have access to google storage, or would upload the traces to different locations. Another is that in case of network latency, doing this step inline would slow down the builder, zip&upload step normally only take 6 seconds though.

[sivachandra]

zorg/buildbot/builders/LLDBBuilder.py

306

I don't understand the first of the concerns. For the second one, chromium builders all archive to google storage. To my knowledge, the archive step was never treated as a time bottle neck.

[chying]

zorg/buildbot/builders/LLDBBuilder.py

306

For the first point, I was saying that adding this step inline will require any builders calling this function have google storage access, i.e. builders have no google storage access won't be able to call this factory function.
I am fine with adding this step inline, all of the current lldb builders calling this function have google storage access.

[sivachandra]

zorg/buildbot/builders/LLDBBuilder.py

306

Unless there is a compelling reason, I do not see why this step should not be inline. If not inline, you are also burdening yourselves with the maintenance of another process.

[chying]

zip and upload test traces to gs by shell command

[sivachandra]

lgtm

zorg/buildbot/builders/LLDBBuilder.py

for compiler in test_compilers:
                                      command=['../%s/tools/lldb/test/dosep.py' % llvm_srcdir,
                                               '--options',
                                               WithProperties(DOTEST_OPTS)],
                                      description="test lldb",
                                      parseSummaryOnly=True,
                                      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
 # For example, RemoteConfig('linux','x86_64',['gcc4.8.2','clang'],['i386'])
 RemoteConfig = collections.namedtuple("RemoteConfig", ["platform", "host_arch", "test_compilers", "test_archs"])
 
 # Add steps to run lldb test on remote target
 def getLLDBRemoteTestSteps(f,