-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
disable repository search in parent directories #675
Conversation
Please document in the code why we need to set the flag on top of the Dir field. Also, are we actually sure that this will fix the bug? We already tried once and didn't get it :) I first thought that writing a regression test would be good, to ensure the code works, but then again we'll stop using |
I can extend modinfo test with linker rebuild and additionally add a panic in case of a "silent" patch skip |
I don't think it's worth it to be honest. The test will be slow, it has nothing to do with module version info, and we'll stop relying on executing |
But it makes sense to add an extra check in case of "silent" skipping patches |
Sure, why not. Perhaps you can do something like:
You should verify this with master, but I think this would always trigger the failure, and it would keep |
Or, to keep the tests more on topic, we could instead make the linker.txtar test set up a git repo with one commit, and do the similar |
Without
|
git
is very smart and tries to find repository in parent directory.This is a very strange situation, but in our
modinfo
test, this is exactly what happens:Fix prevents this behavior