sanity: Use random filename for maximum path length test
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.) (From OE-Core rev: bc28e3f26e7f85af82f403924c0ae29e1ad34a87) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
181875b5d9
commit
447a057988
|
@ -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)
|
||||
|
|
Loading…
Reference in New Issue