public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: dwz@sourceware.org, Mark Wielaard <mark@klomp.org>
Subject: [RFC] External testsuite using binaries
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <3ed89fb7-ae0c-23de-a6c5-78cc7c370083@suse.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

Hi,

since large files tend to be a problem in git, I've created a testsuite
containing binaries, that can be downloaded from ftp and plugged into
the dwz sources.

It contains the following executables:
...
272M    cc1
223M    cc1.dwz-processed
16K     dw2-restrict
16K     dw2-skip-prologue
9,1M    etcd
8,2M    etcdctl
16K     multidictionary
8,0K    py-section-script.debug
...

Is it ok to move some of these (based on a size limit) to dwz.git, or do
we want to keep these separate?

Or, is there some large file support I should be using to integrate this
into dwz.git?

Any other comments?

Thanks,
- Tom


[-- Attachment #2: 0001-Add-external-tests-scripts.patch --]
[-- Type: text/x-patch, Size: 2529 bytes --]

Add external-tests scripts

We keep test-cases using binaries rather than sources in a seperate test
directory dwz-external.tests.  The directory currently has a size of ~512MB.

This directory can be installed using the scripts in this patch:
...
$ ./scripts/fetch-external-tests.sh
$ ./scripts/untar-external-tests.sh
$ ls testsuite
dwz-external.tests  dwz.tests  lib  scripts
...

Result with current (md5sum 09cd309b8e720242cfc79d8de75c8563)
dwz-external-tests.tgz:
...
$ cat dwz.sum
Test run by vries on Wed Mar  6 15:56:13 2019
Native configuration is x86_64-pc-linux-gnu

                === dwz tests ===

Schedule of variations:
    unix

Running target unix
Running testsuite/dwz-external.tests/dwz-external-tests.exp ...
FAIL: testsuite/dwz-external.tests/pr24169.sh
FAIL: testsuite/dwz-external.tests/pr24171.sh
FAIL: testsuite/dwz-external.tests/pr24170.sh
FAIL: testsuite/dwz-external.tests/pr24172.sh
FAIL: testsuite/dwz-external.tests/pr24173.sh
FAIL: testsuite/dwz-external.tests/pr24195.sh
FAIL: testsuite/dwz-external.tests/pr24204.sh
Running testsuite/dwz.tests/dwz-tests.exp ...
PASS: testsuite/dwz.tests/low-mem.sh
PASS: testsuite/dwz.tests/multifile.sh
PASS: testsuite/dwz.tests/regular.sh
PASS: testsuite/dwz.tests/too-many-dies.sh
PASS: testsuite/dwz.tests/hardlink.sh
PASS: testsuite/dwz.tests/multifile-name.sh
PASS: testsuite/dwz.tests/multifile-relative.sh
PASS: testsuite/dwz.tests/regular-o.sh

                === dwz Summary ===

nr of expected passes            8
nr of unexpected failures        7
...

---
 scripts/fetch-external-tests.sh | 5 +++++
 scripts/tar-external-tests.sh   | 6 ++++++
 scripts/untar-external-tests.sh | 5 +++++
 3 files changed, 16 insertions(+)

diff --git a/scripts/fetch-external-tests.sh b/scripts/fetch-external-tests.sh
new file mode 100755
index 0000000..6a521ef
--- /dev/null
+++ b/scripts/fetch-external-tests.sh
@@ -0,0 +1,5 @@
+#!/bin/sh
+
+wget \
+    http://ftp.suse.com/pub/people/tdevries/dwz/dwz-external-tests.tgz
+
diff --git a/scripts/tar-external-tests.sh b/scripts/tar-external-tests.sh
new file mode 100755
index 0000000..9fe87fa
--- /dev/null
+++ b/scripts/tar-external-tests.sh
@@ -0,0 +1,6 @@
+#!/bin/sh
+
+tar \
+    cvfz \
+    ../dwz-external-tests.tgz \
+    testsuite/dwz-external.tests
diff --git a/scripts/untar-external-tests.sh b/scripts/untar-external-tests.sh
new file mode 100755
index 0000000..7193725
--- /dev/null
+++ b/scripts/untar-external-tests.sh
@@ -0,0 +1,5 @@
+#!/bin/sh
+
+tar \
+    xvfz \
+    dwz-external-tests.tgz

             reply	other threads:[~2019-03-07 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 Tom de Vries [this message]
2019-01-01  0:00 ` Mark Wielaard

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=3ed89fb7-ae0c-23de-a6c5-78cc7c370083@suse.de \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=mark@klomp.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).