Disregard old test repository quirks for migration

[CasperWA]

An old test created a .gitignore file in the Node repository folder
path, while also creating files under a raw_input folder.
This adds a logic test for this specific edge-case, migrating the
raw_input folder and ignoring the path folder for the specific Node.

Fixes #4910.

[codecov]

Codecov Report

Merging #4954 (b5ff789) into develop (b5b5051) will increase coverage by 0.01%.
The diff coverage is 66.67%.

@@             Coverage Diff             @@
##           develop    #4954      +/-   ##
===========================================
+ Coverage    80.11%   80.11%   +0.01%     
===========================================
  Files          515      515              
  Lines        36665    36666       +1     
===========================================
+ Hits         29369    29371       +2     
+ Misses        7296     7295       -1     

Flag	Coverage Δ
django	74.58% <66.67%> (+0.01%)	⬆️
sqlalchemy	73.50% <66.67%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
aiida/backends/general/migrations/utils.py	89.19% <66.67%> (+0.05%)	⬆️
aiida/transports/util.py	65.63% <0.00%> (+3.13%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b5b5051...b5ff789. Read the comment docs.

[chrisjsewell]

cheers @CasperWA, just to confirm there is not an analogous change required in the sqlalchemy migrations?

[chrisjsewell]

well actually I guess I meant test for the sqlalchemy backend, since the actual change is in general utils, so I assume that applies to both

[CasperWA]

well actually I guess I meant test for the sqlalchemy backend, since the actual change is in general utils, so I assume that applies to both

Yeah, it seems the checks were done backend-agnostically here, which makes sense as it has nothing to do with the DB. But I'm unsure exactly what you mean otherwise here? Do you want a unittest for something or?

Edit: Ah, I think you do want another unit test, but for the SQLAlchemy backend. Hmm, I don't think it's necessary, but I can set it up if you want, just to be absolutely sure?

[chrisjsewell]

Ah, I think you do want another unit test, but for the SQLAlchemy backend. Hmm, I don't think it's necessary, but I can set it up if you want, just to be absolutely sure?

Yeh that was the point; I just initially noted there was a django named file, but not an sqla one lol.
If its possible to do easily/quickly, I guess it would be nice? (although I'm sure we have better things to do with our lives)

[CasperWA]

If its possible to do easily/quickly, I guess it would be nice? (although I'm sure we have better things to do with our lives)

Mnjeh - you'd say so wouldn't you? 😏 😅

Anyway, I've made a test, but now I'm not remembering how to test the SQLAlchemy backend, what's the env var?

[CasperWA]

Anyway, I've made a test, but now I'm not remembering how to test the SQLAlchemy backend, what's the env var?

Nevermind, I figurereded it out. I'm totally sticky brain.

(But for real: AIIDA_TEST_BACKEND=sqlalchemy pytest...) 👍

[chrisjsewell]

Merge that bad boy!