[OE-core] [PATCH 1/2] sanity: Use random filename for maximum path length test
Mike Crowe
mac at mcrowe.com
Mon Nov 25 15:20:14 UTC 2013
check_create_long_filename used a fixed filename for its test files. This
meant that os.remove(testfile) could fail with ENOENT if two instances were
running at the same time against the same sstate directory. Using a
randomly generated filename stops this from happening.
(Although it might seem unlikely, this race did appear to occur multiple
times with Jenkins - presumably because the matrix jobs were all kicked off
at the same time.)
Signed-off-by: Mike Crowe <mac at mcrowe.com>
---
meta/classes/sanity.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 6807a23..0d40792 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -175,7 +175,8 @@ def check_conf_exists(fn, data):
return False
def check_create_long_filename(filepath, pathname):
- testfile = os.path.join(filepath, ''.join([`num`[-1] for num in xrange(1,200)]))
+ import string, random
+ testfile = os.path.join(filepath, ''.join(random.choice(string.ascii_letters) for x in range(200)))
try:
if not os.path.exists(filepath):
bb.utils.mkdirhier(filepath)
--
1.7.10.4
More information about the Openembedded-core
mailing list