public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ewlu at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113238] [14] RISC-V: gcc.dg vect-tsvc flakey test timeouts when under heavy workload
Date: Thu, 04 Jan 2024 20:02:11 +0000	[thread overview]
Message-ID: <bug-113238-4-nySsb0hK0v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113238-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113238

--- Comment #1 from Edwin Lu <ewlu at rivosinc dot com> ---
Debug log for one of the flakey tests

spawn -ignore SIGHUP
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/xgcc
-B/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/build/build-gcc-linux-stage2/gcc/
/github/patrick-postcommit-runner-2/_work/gcc-postcommit-ci/gcc-postcommit-ci/riscv-gnu-toolchain/gcc/gcc/testsuite/gcc.dg/vect/tsvc/vect-tsvc-s351.c
-march=rv64gcv -mabi=lp64d -mtune=rocket -mcmodel=medlow
-fdiagnostics-plain-output -flto -ffat-lto-objects --param riscv-vector-abi
-ftree-vectorize -fno-tree-loop-distribute-patterns -fno-vect-cost-model
-fno-common -O2 -fdump-tree-vect-details --param vect-epilogues-nomask=0 -lm -o
./vect-tsvc-s351.exe
PASS: gcc.dg/vect/tsvc/vect-tsvc-s351.c -flto -ffat-lto-objects (test for
excess errors)
spawn riscv64-unknown-linux-gnu-run ./vect-tsvc-s351.exe
WARNING: program timed out.
FAIL: gcc.dg/vect/tsvc/vect-tsvc-s351.c -flto -ffat-lto-objects execution test

  reply	other threads:[~2024-01-04 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 19:55 [Bug testsuite/113238] New: " ewlu at rivosinc dot com
2024-01-04 20:02 ` ewlu at rivosinc dot com [this message]
2024-01-04 20:47 ` [Bug testsuite/113238] " pinskia at gcc dot gnu.org

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=bug-113238-4-nySsb0hK0v@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).