File: mutable-outputs.llbuild

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (81 lines) | stat: -rw-r--r-- 2,617 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
# Demonstrates the current "recommended" way of modeling mutable outputs. We do
# not yet have the ability to offer strong support for these situations, but
# this approach uses command dependencies and the node "is-mutable" flag to
# emulate support as best as possible.

# Check the behavior of command dependencies.
#
# RUN: rm -rf %t.build
# RUN: mkdir -p %t.build
# RUN: printf Hello > %t.build/input
# RUN: cp %s %t.build/build.llbuild

# Both commands should run on the initial build.
#
# RUN: %{llbuild} buildsystem build --serial --chdir %t.build > %t.initial.out
# RUN: %{FileCheck} --check-prefix CHECK-INITIAL-LOG --input-file %t.initial.out %s
# RUN: printf "Hello, world!\n" > %t.build/expected-output
# RUNX: diff %t.build/output %t.build/expected-output
#
# CHECK-INITIAL-LOG: C.create
# CHECK-INITIAL-LOG: C.mutate

# No commands should run on a null rebuild.
#
# RUN: %{llbuild} buildsystem build --serial --chdir %t.build > %t.null.out
# RUN: echo EOF >> %t.null.out
# RUN: %{FileCheck} --check-prefix CHECK-NULL-LOG --input-file %t.null.out %s
# RUN: printf "Hello, world!\n" > %t.build/expected-output
# RUNX: diff %t.build/output %t.build/expected-output
#
# CHECK-NULL-LOG-NOT: C.
# CHECK-NULL-LOG: EOF

# Forcing the initial command to run should cause them both to run again.
#
# RUN: printf "Hello there" > %t.build/input
# RUN: %{llbuild} buildsystem build --serial --chdir %t.build > %t.rebuild.out
# RUN: %{FileCheck} --check-prefix CHECK-REBUILD-LOG --input-file %t.rebuild.out %s
# RUN: printf "Hello there, world!\n" > %t.build/expected-output
# RUNX: diff %t.build/output %t.build/expected-output
#
# CHECK-REBUILD-LOG: C.create
# CHECK-REBUILD-LOG: C.mutate

# If the output file was removed, they should both to run again.
#
# RUN: rm %t.build/output
# RUN: %{llbuild} buildsystem build --serial --chdir %t.build > %t.rebuild.out
# RUN: %{FileCheck} --check-prefix CHECK-REMOVAL-LOG --input-file %t.rebuild.out %s
# RUN: printf "Hello there, world!\n" > %t.build/expected-output
# RUNX: diff %t.build/output %t.build/expected-output
#
# CHECK-REMOVAL-LOG: C.create
# CHECK-REMOVAL-LOG: C.mutate

client:
  name: basic

targets:
  "": ["<C.mutate>"]

nodes:
  "<C.create.timestamp>":
    is-command-timestamp: true
  "output":
    is-mutated: true

commands:
  C.mutate:
    tool: shell
    inputs: ["<C.create.timestamp>"]
    outputs: ["<C.mutate>"]
    description: C.mutate
    args: test -f output && echo ", world!" >> output

  C.create:
    tool: shell
    inputs: ["input"]
    outputs: ["output", "<C.create.timestamp>"]
    description: C.create
    args: cp input output