Delete gdb/testsuite/dg-extract-results.py
authorPedro Alves <palves@redhat.com>
Mon, 9 Mar 2015 17:47:18 +0000 (17:47 +0000)
committerPedro Alves <palves@redhat.com>
Mon, 9 Mar 2015 17:47:18 +0000 (17:47 +0000)
commitb2df3cefb124e3cab3a4bf0ba2f25fe8e1d25283
tree585995f23429708d7d3b0f988f9e2d113dc5df71
parentef878e5310ed154450b84cdedd4dd248c7697a2c
Delete gdb/testsuite/dg-extract-results.py

Unfortunately, the Python version of the dg-extract-results.sh script
doesn't produce stable-enough results for GDB.  The test messages
appear to end up alpha sorted (losing the original sequence) and also
sorting changes between runs for some reason.  That may be tolerable
for GCC, but for GDB, it often renders test results diffing between
different revisions unworkable.

Until that is fixed upstream, delete the script from the GDB tree.

testsuite/ChangeLog:
2015-03-09  Pedro Alves  <palves@redhat.com>

* dg-extract-results.py: Delete.
gdb/testsuite/ChangeLog
gdb/testsuite/dg-extract-results.py [deleted file]