You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
checks for the "Error scanning" message in the debug.log caused by processing the no_access directory. However, the same message can also be generated when parsing the self_walletdat_symlink directory. As a result, the current implementation is prone to producing false-positive results.
Parsing the self_walletdat_symlink directory with bitcoind.exe depends on how it was built. When cross-compiling, the parsing completes without system errors. On the other hand, when building natively, it raises an "unknown error" exception and logs the "Error scanning" message.
Note: Although Windows supports chmod(), you can only set the file’s read-only flag with it (via the stat.S_IWRITE and stat.S_IREAD constants or a corresponding integer value).
The text was updated successfully, but these errors were encountered:
I guess it would be good to separate the no_access and symlink unit tests into two test cases, not combine them into one. This would allow to skip just one of them, if needed on Windows.
On the master branch @ ebe4cac, the
wallet_multiwallet.py
test has several issues:This code:
bitcoin/test/functional/wallet_multiwallet.py
Lines 132 to 140 in ebe4cac
debug.log
caused by processing theno_access
directory. However, the same message can also be generated when parsing theself_walletdat_symlink
directory. As a result, the current implementation is prone to producing false-positive results.Parsing the
self_walletdat_symlink
directory withbitcoind.exe
depends on how it was built. When cross-compiling, the parsing completes without system errors. On the other hand, when building natively, it raises an "unknown error" exception and logs the "Error scanning" message.This code:
bitcoin/test/functional/wallet_multiwallet.py
Lines 132 to 139 in ebe4cac
os.chmod
:The text was updated successfully, but these errors were encountered: