public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30289] New: [gdb/testsuite] Test run with editing off
Date: Thu, 30 Mar 2023 02:52:28 +0000	[thread overview]
Message-ID: <bug-30289-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30289

            Bug ID: 30289
           Summary: [gdb/testsuite] Test run with editing off
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I wrote a board file (copied from readnow.exp) setting editing to off by
default:
...
$ cat gdb/testsuite/boards/editing-off.exp 
  ...
load_board_description "local-board"

# Run all tests with editing off.
set GDBFLAGS "${GDBFLAGS} -iex \"set editing off\""

# This is based on baseboards/unix.exp.
# At the moment we only support systems that unix.exp supports.
load_generic_config "unix"
process_multilib_options ""
set found_gcc [find_gcc]
set found_gxx [find_g++]
set_board_info compiler "$found_gcc"
...

Results:
...
FAIL: gdb.ada/access_to_packed_array.exp: set logging enabled on (timeout)
FAIL: gdb.ada/access_to_packed_array.exp: maint print symbols (timeout)
FAIL: gdb.base/page-logging.exp: set logging enabled on (timeout)
FAIL: gdb.base/page-logging.exp: printf without paging (timeout)
FAIL: gdb.base/trace-commands.exp: nested trace-commands test (pattern 2)
FAIL: gdb.base/trace-commands.exp: depth resets on error part 1 (pattern 2)
FAIL: gdb.base/ui-redirect.exp: redirect: set logging enabled on (timeout)
FAIL: gdb.base/ui-redirect.exp: redirect: save breakpoints cmds.txt (timeout)
FAIL: gdb.base/ui-redirect.exp: redirect: userdefined (timeout)
FAIL: gdb.base/ui-redirect.exp: redirect logging and debuging: set logging
enabled on (timeout)
FAIL: gdb.python/tui-window-factory.exp: msg_3: check for python output
FAIL: gdb.threads/threadapply.exp: thread_set=all: try remove: define remove
(timeout)
FAIL: gdb.threads/threadapply.exp: thread_set=all: try remove 2: define
remove-again (timeout)
FAIL: gdb.tui/basic.exp: scroll up
FAIL: gdb.tui/basic.exp: check main is where we expect on the screen
FAIL: gdb.tui/basic.exp: scroll right
FAIL: gdb.tui/basic.exp: scroll down
FAIL: gdb.tui/basic.exp: asm window shows main
FAIL: gdb.tui/completion.exp: check focus completions
FAIL: gdb.tui/info-win.exp: info win, layout src
FAIL: gdb.tui/info-win.exp: info win, layout h
FAIL: gdb.tui/new-layout.exp: layout=cmd_only {cmd 1} {} {}: info win output
FAIL: gdb.tui/scroll.exp: check cmd window
FAIL: gdb.tui/scroll.exp: check cmd window in flip layout
FAIL: gdb.tui/tui-focus.exp: check test2 focus message
FAIL: gdb.tui/tui-focus.exp: check ambiguous focus message
FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll failed)
FAIL: gdb.tui/tui-nl-filtered-output.exp: check printf output
FAIL: gdb.tui/winheight.exp: check error message about src size 100
FAIL: gdb.tui/winheight.exp: check error message about src +1
...

Related PRs:
- PR22454 - "logging sometimes prints prompt"
- PR30288 - "[gdb/cli, editing off] FAIL: gdb.base/trace-commands.exp: nested
  trace-commands test (pattern 2)"

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-03-30  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  2:52 vries at gcc dot gnu.org [this message]
2023-03-30 11:06 ` [Bug testsuite/30289] " vries 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-30289-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).