public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, marxin@gcc.gnu.org
Subject: Re: [PATCH] Testsuite: mark IPA test as requiring alias support
Date: Sun, 20 Aug 2023 19:42:18 +0200	[thread overview]
Message-ID: <47FE3A1C-DC0F-4B53-B23F-885981136B92@gmail.com> (raw)
In-Reply-To: <9D4788E3-0C89-4179-82A0-0FA3A0894243@googlemail.com>

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

Hi,

> IMO, changes like this qualify as obvious, so I’d go ahead (thanks for this test fail triage)

Makes sense. I’ve committed, as well as another one, attached, slightly amending the expected pattern of a sarif plugin test.

FX


[-- Attachment #2: 0001-Testsuite-plugin-make-testcase-pattern-more-flexible.patch --]
[-- Type: application/octet-stream, Size: 1525 bytes --]

From 7be59c50478462a4bba81cddb5d2af038d4c1b1a Mon Sep 17 00:00:00 2001
From: Francois-Xavier Coudert <fxcoudert@gmail.com>
Date: Sun, 20 Aug 2023 19:35:18 +0200
Subject: [PATCH] Testsuite, plugin: make testcase pattern more flexible

On Darwin, the message recorded in the sarif file contains:
  "message": {"text": "Segmentation fault: 11"}
which is different from, e.g., linux:
  "message": {"text": "Segmentation fault"}

Adjusting the testcase pattern to be a little more flexible.

gcc/testsuite/ChangeLog:
	* gcc.dg/plugin/crash-test-write-though-null-sarif.c: Update
	expected pattern.
---
 .../gcc.dg/plugin/crash-test-write-though-null-sarif.c          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c b/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c
index 83b38d2ffb5..513d66c528d 100644
--- a/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c
+++ b/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c
@@ -61,4 +61,4 @@ void test_inject_write_through_null (void)
                { dg-final { scan-sarif-file "\"startColumn\": 3" } }
                { dg-final { scan-sarif-file "\"endColumn\": 31" } }
          { dg-final { scan-sarif-file "\"message\": " } }
-           { dg-final { scan-sarif-file "\"text\": \"Segmentation fault\"" } } */
+           { dg-final { scan-sarif-file "\"text\": \"Segmentation fault" } } */
-- 
2.39.2 (Apple Git-143)


      reply	other threads:[~2023-08-20 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 12:15 FX Coudert
2023-08-20 13:55 ` Iain Sandoe
2023-08-20 17:42   ` FX Coudert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FE3A1C-DC0F-4B53-B23F-885981136B92@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=idsandoe@googlemail.com \
    --cc=marxin@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).