From 31fc4ecb29dfefb81b1ca09427aaab19d19a7d50 Mon Sep 17 00:00:00 2001
From: Saleem Abdulrasool <abdulras@thebrowser.company>
Date: Mon, 20 Nov 2023 12:43:01 -0800
Subject: [PATCH] Tests: clean up path representation for manifest checks

The path representation on Windows is not Unix-like.  Use `AbsolutePath`
to ensure that we correctly represent the path in expectations.  This
fixes the test on Windows.
---
 Tests/LLBuildManifestTests/LLBuildManifestTests.swift | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Tests/LLBuildManifestTests/LLBuildManifestTests.swift b/Tests/LLBuildManifestTests/LLBuildManifestTests.swift
index 24d42c66e52..ffe03d6e8db 100644
--- a/Tests/LLBuildManifestTests/LLBuildManifestTests.swift
+++ b/Tests/LLBuildManifestTests/LLBuildManifestTests.swift
@@ -199,13 +199,13 @@ final class LLBuildManifestTests: XCTestCase {
             nodes:
               "<C.create.timestamp>":
                 is-command-timestamp: true
-              "/file.out":
+              "\(AbsolutePath("/file.out"))":
                 is-mutated: true
             commands:
               "C.create":
                 tool: shell
-                inputs: ["/file.in"]
-                outputs: ["/file.out","<C.create.timestamp>"]
+                inputs: ["\(AbsolutePath("/file.in"))"]
+                outputs: ["\(AbsolutePath("/file.out"))","<C.create.timestamp>"]
                 description: "C.create"
                 args: ["cp","file.in","file.out"]