[LNT] r235561 - Be a little more verbose and helpful when project build code size fails

Chris Matthews cmatthews5 at apple.com
Wed Apr 22 16:35:12 PDT 2015


Author: cmatthews
Date: Wed Apr 22 18:35:11 2015
New Revision: 235561

URL: http://llvm.org/viewvc/llvm-project?rev=235561&view=rev
Log:
Be a little more verbose and helpful when project build code size fails

Modified:
    lnt/trunk/lnt/tests/compile.py

Modified: lnt/trunk/lnt/tests/compile.py
URL: http://llvm.org/viewvc/llvm-project/lnt/trunk/lnt/tests/compile.py?rev=235561&r1=235560&r2=235561&view=diff
==============================================================================
--- lnt/trunk/lnt/tests/compile.py (original)
+++ lnt/trunk/lnt/tests/compile.py Wed Apr 22 18:35:11 2015
@@ -476,11 +476,16 @@ def test_build(base_name, run_info, vari
                 # FIXME: We should resolve this, eventually.
                 for i in range(variables.get('run_count')):
                     samples.append(bytes)
+            else:
+                g_log.warning('Codesize failed.')
+
         except OSError as e:
             if e.errno != errno.ENOENT:
                 raise
+            else:
+                g_log.warning('Codesize failed with ENOENT.')
         yield (success, tname, samples)
-    
+
     # Check that the file sizes of the output log files "make sense", and warn
     # if they do not. That might indicate some kind of non-determinism in the
     # test command, which makes timing less useful.





More information about the llvm-commits mailing list