From 3c6eedc32e005ad64c9c90ccaacdd71d8de926cf Mon Sep 17 00:00:00 2001 From: Ulf Adams Date: Thu, 16 Apr 2015 10:59:17 +0000 Subject: Actually run the actions tests in Bazel. This requires writing a workspace file for the JDK. -- MOS_MIGRATED_REVID=91287178 --- .../google/devtools/build/lib/analysis/actions/SymlinkActionTest.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/test/java/com/google/devtools/build/lib/analysis/actions/SymlinkActionTest.java') diff --git a/src/test/java/com/google/devtools/build/lib/analysis/actions/SymlinkActionTest.java b/src/test/java/com/google/devtools/build/lib/analysis/actions/SymlinkActionTest.java index c2e1673e68..d2607aa5d8 100644 --- a/src/test/java/com/google/devtools/build/lib/analysis/actions/SymlinkActionTest.java +++ b/src/test/java/com/google/devtools/build/lib/analysis/actions/SymlinkActionTest.java @@ -40,7 +40,7 @@ public class SymlinkActionTest extends BuildViewTestCase { @Override public void setUp() throws Exception { super.setUp(); - input = scratchFile("/workspace/input.txt", "Hello, world."); + input = scratchFile("input.txt", "Hello, world."); inputArtifact = getSourceArtifact("input.txt"); Path linkedInput = directories.getExecRoot().getRelative("input.txt"); FileSystemUtils.createDirectoryAndParents(linkedInput.getParentDirectory()); -- cgit v1.2.3