BF(TST): prevent auto-upgrade of "remote" test sibling, do not use local path for URL #6957
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cal path for URL Our docker image for testing of interactions over ssh still has git-annex 7.20190819+git2-g908476a9b-1~ndall+1 and that is great so we can ensure that datalad works well even with older versions (note - current minimal supported is 8.20200309 but upgrade to that one would not matter in this case). We use create_sibling to create remote through ssh but on the path which is also available locally. And then instead of always interacting with that repository remotely, we had direct interactions with it using AnnexRepo or creating a sibling not over ssh but pointing directly to that path. That would have lead local git-annex possibly to upgrade it to later version of git annex repo (10 ATM) whenever remote (docker) instance of git-annex would not know that version. And with annex version 10, a new command was added "filter-process" which it records within .git/config for that annex. So if we ever upgrade it by acessing a local path, "git push" fails since then it runs git-annex filter-process and that fails in turn, and we do not even see that error. Citing it here in full FTR from datalad#6901 (comment) (git-annex)lena:~/.tmp/datalad_temp_test_target_ssh_simplerf0k0b97[dl-test-branch]git $> SSH_AGENT_PID= SSH_AUTH_SOCK= git push local_target dl-test-branch Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 12 threads Compressing objects: 100% (9/9), done. Writing objects: 100% (9/9), 798 bytes | 798.00 KiB/s, done. Total 9 (delta 2), reused 0 (delta 0), pack-reused 0 Invalid argument `filter-process' Usage: git-annex COMMAND git-annex - manage files with git, without checking their contents in Commonly used commands: add PATH ... add files to annex ... fatal: the remote end hung up unexpectedly To ssh://datalad-test/home/yoh/.tmp/datalad_temp_test_target_ssh_simplexx85c2vs/basic ! [remote rejected] dl-test-branch -> dl-test-branch (Could not update working tree to new HEAD) error: failed to push some refs to 'ssh://datalad-test/home/yoh/.tmp/datalad_temp_test_target_ssh_simplexx85c2vs/basic' where in the tests we only see that "Could not update" making it difficult to pin point the problem. In this commit I prevent auto-upgrade on that repo, and if then local operation fails -- I just skip direct interaction with such AnnexRepo. And I also replaced "replace"ing of the repo using local path, and instead using "custom" ssh url so we could still compare that all urls are assigned as expected. Closes datalad#6901
yarikoptic
added
release
mih
approved these changes
Aug 18, 2022
which was a target_path before and now a full url
Codecov Report
@@ Coverage Diff @@
## maint #6957 +/- ##
==========================================
+ Coverage 89.97% 90.99% +1.01%
==========================================
Files 354 354
Lines 46259 46453 +194
==========================================
+ Hits 41622 42269 +647
+ Misses 4637 4184 -453
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
it is green everywhere (besides known crawler) -- let's proceed. Thanks @mih for blessing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our docker image for testing of interactions over ssh still has git-annex 7.20190819+git2-g908476a9b-1~ndall+1
and that is great so we can ensure that datalad works well even with older versions (note - current minimal
supported is 8.20200309 but upgrade to that one would not matter in this case).
We use create_sibling to create remote through ssh but on the path which is also available locally.
And then instead of always interacting with that repository remotely, we had direct interactions with it
using AnnexRepo or creating a sibling not over ssh but pointing directly to that path. That would have lead
local git-annex possibly to upgrade it to later version of git annex repo (10 ATM) whenever remote (docker)
instance of git-annex would not know that version. And with annex version 10, a new command was added
"filter-process" which it records within .git/config for that annex.
So if we ever upgrade it by acessing a local path, "git push" fails since then
it runs git-annex filter-process and that fails in turn, and we do not even see
that error. Citing it here in full FTR from #6901 (comment)
where in the tests we only see that "Could not update" making it
difficult to pin point the problem.
In this commit I prevent auto-upgrade on that repo, and if then local operation
fails -- I just skip direct interaction with such AnnexRepo. And I also
replaced "replace"ing of the repo using local path, and instead using "custom"
ssh url so we could still compare that all urls are assigned as expected.
Closes #6901
PS I added
releaselabel . Auto-releasing would fail as previous one failed due to already too long of a changelog, uff, so I will release it manually after this PR is merged. It is needed to bring our CI in datalad/git-annex back to green.