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
TST: set --allow-unrelated-histories in the mk_push_target setup for Windows #5855
Conversation
Codecov Report
@@ Coverage Diff @@
## maint #5855 +/- ##
===========================================
- Coverage 90.28% 29.54% -60.75%
===========================================
Files 300 297 -3
Lines 42370 42338 -32
===========================================
- Hits 38252 12507 -25745
- Misses 4118 29831 +25713
Continue to review full report at Codecov.
|
The test failure looks unrelated to me:
|
I wonder if such a special treatment would only hide an issue which otherwise would eventually hit the users. I still think it should be cleared up with @joeyh since I still feel that it might be just a regression and will be fixed on annex side. Some jobs stalled in our tests (not a good sign :-/ stalls happened recently in other PRs as well), restarted a 12259.1 on travis |
oh, just spotted the comment you @adswa left regarding git-annex change http://source.git-annex.branchable.com/?p=source.git;a=commit;h=3d50b47dede6e4e94232718f4c460cd19147dcfb which exposes that option within git-annex and thus may be the change in behavior is intended. But then it seems it would be for us in probably |
I wondered this, too. But this test setup is arguably a quite special case - creating a new dataset and adding it as a sibling to an existing dataset. And it is only on Windows where this involves unifying two unrelated histories. Maybe I don't have enough imagination, but I would think that a typical workflow would rather involve a |
Yes, this may well be. But this PR here just wants to make this test helper functional again |
isn't it for any remote which would be on a crippled FS (external usb stick), thus adjusted branches etc? |
oh yes, probably! Sorry, I keep forgetting about crippled FSs |
Is create-sibling now functional on windows? The reason for these test helpers was that datalad is not capable to do this on windows. I am all in favor of fixing the helpers, and leaving bigger plans aside. Filed #5857 to make things a bit more obvious. |
…Windows The test helper mk_push_target creates a sibling dataset by creating an unrelated dataset and adding it as a sibling. On Windows, this was not straightforward, as the datasets had unrelated histories due to the initial adjusted branch commit in the target dataset. Until git-annex version 20210720, a git annex sync would establish a shared history - more recent versions of git-annex will fail to sync unrelated histories unless --allow-unrelated-histories is set.
rebased to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. Thx!
The failing linting is not the fault of this PR. |
The test helper mk_push_target creates a sibling dataset by
creating an unrelated dataset and adding it as a sibling. On
Windows, this was not straightforward, as the datasets had
unrelated histories due to the initial adjusted branch commit
in the target dataset. Until git-annex version 20210720, a git
annex sync would establish a shared history - more recent versions
of git-annex will fail to sync unrelated histories unless
--allow-unrelated-histories is set.
With this patch, the tests that started to fail on Windows in #5811 pass again.
Fixes #5811.