Make alias targets keep their own configuration.

This prevents the case of a rule acquiring the null configuration in case the alias points to an input file. Which, in turn, makes "bazel build" work for these targets. The reason it breaks is that TargetCompletionValue instances are created from the associated ConfiguredTarget in SkyframeExecutor#buildArtifacts(), which means that if the configurations do not match, TargetCompletionFunction requests a different ConfiguredTargetValue than it was created from.

Fixes #1297.

--
MOS_MIGRATED_REVID=122973526

1 files changed, 10 insertions, 0 deletions

diff --git a/src/test/java/com/google/devtools/build/lib/rules/AliasTest.java b/src/test/java/com/google/devtools/build/lib/rules/AliasTest.java
index 34f7336a2a..17d3ea10e8 100644
--- a/src/test/java/com/google/devtools/build/lib/rules/AliasTest.java
+++ b/src/test/java/com/google/devtools/build/lib/rules/AliasTest.java
@@ -46,6 +46,16 @@ public class AliasTest extends BuildViewTestCase {
   }
 
   @Test
+  public void aliasToInputFile() throws Exception {
+    scratch.file("a/BUILD",
+        "exports_files(['a'])",
+        "alias(name='b', actual='a')");
+
+    ConfiguredTarget b = getConfiguredTarget("//a:b");
+    assertThat(ActionsTestUtil.baseArtifactNames(getFilesToBuild(b))).containsExactly("a");
+  }
+
+  @Test
   public void visibilityIsOverriddenAndIsOkay() throws Exception {
     scratch.file("a/BUILD",
         "filegroup(name='a', visibility=['//b:__pkg__'])");