microsoft / microsoft/VFSForGit
Diagnose issues with Functional Tests on Mojave build agent
Open
@nickgra is already working on this.
Since Jun 10, 2019.
affects: engineering
platform: macOS
type: test-reliability
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
These two tests deterministically fail:
Errors, Failures and Warnings
1) Failed : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitReadAndGitLockTests.GitAliasNamedAfterKnownCommandAcquiresLock()
Expected substring 'Waiting for 'GVFS.FunctionalTests.LockHolder'' not found in ''
Expected: True
But was: False
at GVFS.Tests.Should.StringShouldExtensions.ShouldContain(String actualValue, String[] expectedSubstrings) in /Users/gvfsadmin/agent/_work/3/s/GVFS/GVFS.Tests/Should/StringShouldExtensions.cs:line 19
at GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitReadAndGitLockTests.GitAliasNamedAfterKnownCommandAcquiresLock() in /Users/gvfsadmin/agent/_work/3/s/GVFS/GVFS.FunctionalTests/Tests/EnlistmentPerFixture/GitReadAndGitLockTests.cs:line 69
2) Failed : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitReadAndGitLockTests.GitAliasInSubfolderNamedAfterKnownCommandAcquiresLock()
Expected substring 'Waiting for 'GVFS.FunctionalTests.LockHolder'' not found in 'error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch' to see the failed patch
'
Expected: True
But was: False
at GVFS.Tests.Should.StringShouldExtensions.ShouldContain(String actualValue, String[] expectedSubstrings) in /Users/gvfsadmin/agent/_work/3/s/GVFS/GVFS.Tests/Should/StringShouldExtensions.cs:line 19
at GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitReadAndGitLockTests.GitAliasInSubfolderNamedAfterKnownCommandAcquiresLock() in /Users/gvfsadmin/agent/_work/3/s/GVFS/GVFS.FunctionalTests/Tests/EnlistmentPerFixture/GitReadAndGitLockTests.cs:line 84
See: https://mseng.visualstudio.com/AzureDevOps/_build/results?buildId=9667762
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.