File: timestamp-collision.ninja

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 (28 lines) | stat: -rw-r--r-- 954 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
 
# Check our handling of timestamp collisions and update-if-newer behavior.

# Verify that we perform update-if-newer if the output and the input have the
# exact same timestamp (using touch -r).
#
# RUN: rm -rf %t.build
# RUN: mkdir -p %t.build
# RUN: cp %s %t.build/build.ninja
# RUN: touch -r / %t.build/input %t.build/output
# RUN: %{llbuild} ninja build --no-db --jobs 1 --chdir %t.build &> %t1.out
# RUN: %{FileCheck} --check-prefix CHECK-COLLISION --input-file %t1.out %s
#
# CHECK-COLLISION: no work to do

# Verify that we perform a stricter check in --strict mode.
#
# RUN: %{llbuild} ninja build --strict --no-db --jobs 1 --chdir %t.build &> %t2.out
# RUN: %{FileCheck} --check-prefix CHECK-STRICT --input-file %t2.out %s
#
# CHECK-STRICT: [1/{{.*}}] cat input > output


rule CAT
     command = cat ${in} > ${out}
     # We mark this as a generator command to avoid comparisons on the command hash.
     generator = 1

build output: CAT input