Skip to content

Feature: "error: CHECK-NEXT: is on the same line as previous match" #7

Open
@stanislaw

Description

@stanislaw

This has to be implemented.

See also: https://reviews.llvm.org/D28896.

Activity

changed the title [-]error: CHECK-NEXT: is on the same line as previous match[/-] [+]Feature: "error: CHECK-NEXT: is on the same line as previous match"[/+] on Nov 19, 2019
stanislaw

stanislaw commented on Nov 19, 2019

@stanislaw
MemberAuthor

One way to trigger:

; CHECK-NEXT: {{^<stdin>:.*:.*: note: possible intended match here$}}
; CHECK: {{^.*$}}
; CHECK: {{^.*$}}
; CHECK-EMPTY:

error: CHECK-EMPTY: is not on the line after the previous match

stanislaw

stanislaw commented on Dec 13, 2019

@stanislaw
MemberAuthor

#52 seems to be a base for this behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @stanislaw

        Issue actions

          Feature: "error: CHECK-NEXT: is on the same line as previous match" · Issue #7 · mull-project/FileCheck.py