search for: originalname

I expect that there is something simple that I am missing, but if I set a file to "ensure => absent", puppet is actually just renaming it to "${ORIGINALNAME}puppet" (i.e., appending puppet to the name). Did I forget to turn off a debug flag somewhere? The file definition that I am using is just: file { "/usr/lib/xen-tools/debian.d/55-create-dev": ensure => absent } After puppet runs, there ends up being a file in that directory nam...

> 1. In a CHECK-DAG group, don't let the matches for patterns overlap. > 2. Add a new CHECK-DAG-N directive, where N is some integer, to express > that a pattern must have N non-overlapping matches. I think #1 is much more intuitive and easy to describe/document than #2. Changing the meaning of DAG in that way is highly unlikely to affect any existing test, IMO. And if it does, my

Hi, Using FileCheck, I have not found a way to make a group of CHECK-DAG directives match multiple occurrences of a string. For example, I naively thought the following would match successfully: ``` $ cat checks.txt // CHECK: start // CHECK-DAG: foo // CHECK-DAG: foo // CHECK-DAG: bar // CHECK-NEXT: end $ cat input.txt start foo bar foo end $ FileCheck --input-file=input.txt checks.txt

...erlapping is permitted, Y also matches Y's intended match, and X's intended match is quietly ignored. This case is clearly unintentional. One fix is to move X after Y. A cleaner fix is to somehow make X distinct. Another example of this scenario: * test/Bitcode/thinlto-function-summary-originalnames.ll S3. Wrong number of identical patterns -------------------------------------- This scenario is just an incorrect attempt at the original use case I wanted to address. For example, projects/openmp/runtime/test/ompt/parallel/not_enough_threads.c repeats the following three times: ``` // CHECK...