test: investigate test failure

[efiop]

Only on @shcheklein 's machine: https://gist.github.com/shcheklein/507b0d99a24d1e18249a8c0ad3791110

[shcheklein]

More context:

When cache type is reflinks and we run dvc add foo, we move it to cache under the hood and create a link. It looks like there are two files, two inodes, they internally share data blocks. But we don’t update our state db, as far a I understand. It basically means that we have an inode in state db that belongs to the cached file, not the one from the workspace. It means that if run dvc run -d foo it calculates the md5 again.

^^ This should be fixed in #1221 .

Tests should be fixed two ways if it's indeed related to reflinks:

1. CI should be set to run on APFS, brfts, or similar systems. We need to run the whole test suite on different environment.
2. Failing tests have to be fixed to account for that.

[pared]

#1221 is fixed, @shcheklein, can I close this?

[shcheklein]

Yep, it is fixed. Feel free to close it.

…

On Mon, Feb 25, 2019 at 4:29 AM Paweł Redzyński ***@***.***> wrote: #1221 <#1221> is fixed, @shcheklein <https://github.com/shcheklein>, can I close this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1534 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADfVvLdDgLXBnlx5xmPACOliZeSjuk9Qks5vQ9cYgaJpZM4aUhsb> .