public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Add comprehensive C++ operator linespec/location/completion tests
Date: Sat, 25 Nov 2017 08:52:00 -0000	[thread overview]
Message-ID: <6a3c6ee41898743234d8fd9f9cab15f2ecdaba49@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 6a3c6ee41898743234d8fd9f9cab15f2ecdaba49 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6a3c6ee41898743234d8fd9f9cab15f2ecdaba49

Add comprehensive C++ operator linespec/location/completion tests

This exercises the special handling C++ operators require in several
places in the linespec parser, both the linespec and explicit location
completers, symbol lookup, etc.  Particularly, makes sure all that
works without quoting.

Note that despite the apparent smallish size, this adds thousands of
tests to the testsuite, due to combination explosion (linespecs,
explicit locations, tab completion, complete command, completion at
different points in each function, etc.)

Grows the gdb.linespec/ tests like this:

 -# of expected passes           3464
 +# of expected passes           7823

gdb/testsuite/ChangeLog:
2017-11-25  Pedro Alves  <palves@redhat.com>

	* gdb.linespec/cpls-ops.cc: New file.
	* gdb.linespec/cpls-ops.exp: New file.
	* lib/completion-support.exp (test_complete_prefix_range_re): New,
	factored out from ...
	(test_complete_prefix_range): ... this.


             reply	other threads:[~2017-11-25  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  8:52 sergiodj+buildbot [this message]
2017-11-25  8:52 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot
2017-11-25  9:00 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-25  9:04 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-11-25  9:08 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-11-25  9:16 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-11-25  9:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-25 20:11 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-25 20:34 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-11-25 20:49 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-11-25 21:27 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot

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=6a3c6ee41898743234d8fd9f9cab15f2ecdaba49@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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).