microsoft / microsoft/VFSForGit

Non-reproducible Mac Functional Test failures

Open
#1,204 5 comments 0 reactions 1 assignee View on GitHub

@kewillford is already working on this.

Since Jun 5, 2019.

platform: macOS type: test-reliability
Dominant language
C#
Stars
6.1k
Forks
474
Avg merge
2d 4h
Merged PRs (30d)
8

Description

https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=9551320&view=results

I got the 3 failures below on a PR that only touches unit tests, nothing that affects functional tests: #1200.

The the tests are all related to renaming, but at this stage #1193 has not been merged yet, which would otherwise be my prime suspect. The failure mode appears to be that the repo is not mounted however, so possibly it has nothing to do at all with renaming.

Errors, Failures and Warnings

1) Failed : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests(GVFS.FunctionalTests.FileSystemRunners.SystemIORunner).GitStatusAfterRenameFileIntoRepo()
  Expected: <empty>
  But was:  "The repo does not appear to be mounted. Use 'gvfs status' to check.
fatal: pre-command hook aborted command
"
   at GVFS.Tests.Should.EnumerableShouldExtensions.ShouldBeEmpty[T](IEnumerable`1 group, String message) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.Tests/Should/EnumerableShouldExtensions.cs:line 13
   at GVFS.FunctionalTests.Tools.GitHelpers.CheckGitCommandAgainstGVFSRepo(String virtualRepoRoot, String command, String[] expectedLinesInResult) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tools/GitHelpers.cs:line 71
   at GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests.GitStatusAfterRenameFileIntoRepo() in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tests/EnlistmentPerFixture/GitMoveRenameTests.cs:line 199

2) Error : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests(GVFS.FunctionalTests.FileSystemRunners.SystemIORunner).GitStatusAfterRenameFileOutOfRepo()
System.IO.FileNotFoundException : Could not find file '/GVFS.FT/test/c9d3762927934bf0922f/src/Test_EPF_MoveRenameFileTests/ChangeUnhydratedFileName/Program.cs'.
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at GVFS.FunctionalTests.FileSystemRunners.SystemIORunner.MoveFile(String sourcePath, String targetPath) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/FileSystemRunners/SystemIORunner.cs:line 21
   at GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests.GitStatusAfterRenameFileOutOfRepo() in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tests/EnlistmentPerFixture/GitMoveRenameTests.cs:line 214

3) Failed : GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests(GVFS.FunctionalTests.FileSystemRunners.SystemIORunner).GitStatusAfterRenameFolderIntoRepo()
  Expected: <empty>
  But was:  "The repo does not appear to be mounted. Use 'gvfs status' to check.
fatal: pre-command hook aborted command
"
   at GVFS.Tests.Should.EnumerableShouldExtensions.ShouldBeEmpty[T](IEnumerable`1 group, String message) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.Tests/Should/EnumerableShouldExtensions.cs:line 13
   at GVFS.FunctionalTests.Tools.GitHelpers.CheckGitCommandAgainstGVFSRepo(String virtualRepoRoot, String command, String[] expectedLinesInResult) in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tools/GitHelpers.cs:line 71
   at GVFS.FunctionalTests.Tests.EnlistmentPerFixture.GitMoveRenameTests.GitStatusAfterRenameFolderIntoRepo() in /Users/gvfsadmin/agent/_work/4/s/GVFS/GVFS.FunctionalTests/Tests/EnlistmentPerFixture/GitMoveRenameTests.cs:line 241

Run Settings
    Number of Test Workers: 16
    Work Directory: /Users/gvfsadmin/agent/_work/4/s
    Internal Trace: Off

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.