Skip to content

Remove all reference to looseObjectCount in LooseObjectStepTests#1198

Merged
derrickstolee merged 1 commit intomicrosoft:masterfrom
derrickstolee:flaky-test-one-more-line
May 24, 2019
Merged

Remove all reference to looseObjectCount in LooseObjectStepTests#1198
derrickstolee merged 1 commit intomicrosoft:masterfrom
derrickstolee:flaky-test-one-more-line

Conversation

@derrickstolee
Copy link
Contributor

When making the tests more flexible in #1162, I missed one instance. To
be sure I didn't miss any more, I removed all use of the
exact loose object count.

When making the tests more flexible, I missed one instance. To
be sure I didn't miss any more, I removed all storage of the
exact loose object count.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
@derrickstolee derrickstolee requested a review from wilbaker May 24, 2019 15:14
@jrbriggs jrbriggs added this to the M153 milestone May 24, 2019
@derrickstolee derrickstolee merged commit 50ef886 into microsoft:master May 24, 2019
derrickstolee added a commit that referenced this pull request May 29, 2019
…nmounting

These tests have been super-flaky and frustrating. After weakening the tests, but still finding places where the loose object count is not deterministic, I thought it was worth starting over with the full list of exact-count assertions. To avoid loose objects being added or dropped from the counts in unexpected ways, now we unmount the repo before counting the objects.

I ran the functional tests 20 times on this PR and only one failure, but it was in the `GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitReadAndGitLockTests.GitAliasNamedAfterKnownCommandAcquiresLock()` test, unrelated to this change.

Replaces #1162, #1198, #1116.

Fixes #1201.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants