Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@carlosmn
Copy link
Member

This is far from an ideal situation, but this causes issues on Windows which
make it harder to develop anything, as these tests hit issues which relate
specifically to the Windows filesystem like permission errors for files we
should be able to access. There is an issue likely related to the ordering of
the repack, but there's enough noise that it does not currently help us to run
this aspect of the test in CI.


This is basically an approach out of desperation. There is too much that the Windows filesystem is throwing at us for us to resolve this before the release, and these edge cases shouldn't block the release, nor should it block CI for unrelated PRs as much as it does.

This is far from an ideal situation, but this causes issues on Windows which
make it harder to develop anything, as these tests hit issues which relate
specifically to the Windows filesystem like permission errors for files we
should be able to access. There is an issue likely related to the ordering of
the repack, but there's enough noise that it does not currently help us to run
this aspect of the test in CI.
@ethomson
Copy link
Member

So, this definitely bums me out. But yes, it's unlikely that we're going to get the underlying issues resolved immediately. It's not a regression, so it shouldn't hold up the release and it definitely shouldn't be failing our CI builds.

I mention this only because I also want to make sure that we circle back on this after the release on that magical day when we both have lots of spare time, har har.

@ethomson ethomson merged commit c5e6ba2 into master Dec 16, 2016
@ethomson ethomson deleted the cmn/windows-no-concurrent-compress branch January 9, 2019 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants