Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mismatch in readlink results (MacOS only) #392

Closed
agroce opened this issue May 14, 2018 · 3 comments
Closed

mismatch in readlink results (MacOS only) #392

agroce opened this issue May 14, 2018 · 3 comments
Labels

Comments

@agroce
Copy link

agroce commented May 14, 2018

import shutil
import pyfakefs.fake_filesystem
import os

ROOT_PATH = "/Volumes/ramdisk/test"

fs = pyfakefs.fake_filesystem.FakeFilesystem()
fs.CreateDirectory('/Volumes')
fs.CreateDirectory('/Volumes/ramdisk')
fs.CreateDirectory('/Volumes/ramdisk/test')
os0 = pyfakefs.fake_filesystem.FakeOsModule(fs)
opener0 = pyfakefs.fake_filesystem.FakeFileOpen(fs)

if False:
    os0 = os
    shutil.rmtree(ROOT_PATH)
    os.mkdir(ROOT_PATH)

component0 = "alpha" 
component1 = "" 
path0 = ROOT_PATH 
path1 = ROOT_PATH 
path1 += os.path.sep + component0 
component0 = "beta" 
path0 += os.path.sep + component0 
os0.symlink(path0,path1) 
os0.symlink(path1,path0) 
path0 += os.path.sep + component1 
result = os0.readlink(path0) 

print result

/Volumes/ramdisk/test/alpha for OS, but /Volumes/ramdisk/test/beta for pyfakefs

@mrbean-bremen mrbean-bremen changed the title mismatch in readlink results mismatch in readlink results (MacOS only) May 14, 2018
@agroce
Copy link
Author

agroce commented May 14, 2018

(these are all from a big batch produced during a two-day run until estimated coverage saturation; I will have a few more from it once triage is done on the 8K failing tests produced)

@mrbean-bremen
Copy link
Member

Sounds like a lot of work... I don't have much time for fixing issues currently, so I will go slow on these. Let me know if there are blocking issues that prevent further testing.

@agroce
Copy link
Author

agroce commented May 14, 2018

Eh, it's all automated; I mostly was doing a test of my saturation implementation, and figured why not get some bug hunting done at the same time to keep it real. Running AFL from the same base now, see if it turns up any other issues, and then just keep those and report remaining issues as you get a chance to fix things. No showstoppers I can see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants