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] Make tests expect [ \t]+ pattern instead of \t for "info reg" command Date: Fri, 19 Jan 2018 06:21:00 -0000 [thread overview] Message-ID: <adf8243ba9220966bbb8f67460b2d323e00cbfdb@gdb-build> (raw) *** TEST RESULTS FOR COMMIT adf8243ba9220966bbb8f67460b2d323e00cbfdb *** Author: Ruslan Kabatsayev <b7.10110111@gmail.com> Branch: master Commit: adf8243ba9220966bbb8f67460b2d323e00cbfdb Make tests expect [ \t]+ pattern instead of \t for "info reg" command This will allow to format output of "info reg" command as we wish, without breaking the tests. In particular, it'll let us correctly align raw and natural values of the registers using spaces instead of current badly-working approach with tabs. This change is forwards- and backwards-compatible, so that the amended tests will work in the same way before and after reformatting patches (unless the tests check formatting, of course, but I've not come across any such tests). Some tests already used this expected pattern, so they didn't even have to be modified. Others are changed by this patch. I've checked this on a i386 system, with no noticeable differences in test results, so at least on i386 nothing seems to be broken by this. gdb/testsuite/ChangeLog: * gdb.arch/powerpc-d128-regs.exp: Replace expected "\[\t\]*" from "info reg" with "\[ \t\]*". * gdb.arch/altivec-regs.exp: Replace expected "\t" from "info reg" with "\[ \t\]+". * gdb.arch/s390-multiarch.exp: Ditto. * gdb.base/pc-fp.exp: Ditto. * gdb.reverse/i386-precsave.exp: Ditto. * gdb.reverse/i386-reverse.exp: Ditto. * gdb.reverse/i387-env-reverse.exp: Ditto. * gdb.reverse/i387-stack-reverse.exp: Ditto.
next reply other threads:[~2018-01-19 6:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-19 6:21 sergiodj+buildbot [this message] 2018-01-19 6:21 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot 2018-01-19 6:36 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-01-19 6:46 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2018-01-19 6:50 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-01-19 7:22 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2018-01-19 7:54 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-01-19 8:07 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-01-19 8:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-01-19 8:59 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-01-19 20:17 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-01-19 20:50 ` Failures on Ubuntu-AArch32-native-gdbserver-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=adf8243ba9220966bbb8f67460b2d323e00cbfdb@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: linkBe 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).