microsoft / microsoft/VFSForGit

Diagnose issues with Functional Tests on Mojave build agent

Open
#1,264 1 comment 0 reactions 1 assignee View on GitHub

@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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.