{"thread":{"id":"24576","subject":"[PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","startedAt":"2010-07-29T21:20:55Z","lastAt":"2010-08-09T19:56:08Z","messageCount":9,"participants":["Ævar Arnfjörð Bjarmason","Thomas Rast","Jeff King","Junio C Hamano","Heiko Voigt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"146734","messageId":"1280438455-16255-1-git-send-email-avarab@gmail.com","threadId":"24576","inReplyTo":null,"subject":"[PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-07-29T21:20:55Z","receivedAt":"2010-07-29T21:20:55Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Add the capability to send smoke reports to the Git test suite.\n\nCurrently we only notice bugs in the test suite when it's run\nmanually. Bugs in Git that only occur on obscure platforms or setups\nthat the core developers aren't using may thus go unnoticed until the\nbug makes it into a release.\n\nThis series aims to change that. With it anyone that's interested in\navoiding bitrot in Git can volunteer to run a smoke tester. A smoke\ntester periodically compiles the latest version of Git, runs the test\nsuite, and submits a report to a central server indicating how the\ntest run went.\n\nA smoke tester might run something like this in cron:\n\n    #!/bin/sh\n    cd ~/g/git\n    git fetch\n    for branch in maint master next pu; do\n        git checkout origin/$i &&\n        make clean all &&\n        cd t &&\n        make smoke_report\n    done\n\nThe smoker might want to compile git with non-default flags. A script\nwhich does that is outside the scope of this patch. But it's something\nwe'll want to include eventually.\n\nWhat this does now is add smoke and smoke_report targets to\nt/Makefile:\n\n    $ make clean smoke\n    rm -f -r 'trash directory'.* test-results\n    rm -f t????/cvsroot/CVSROOT/?*\n    rm -f -r valgrind/bin\n    rm -f .prove\n    perl ./harness --git-version=\"1.7.2.1.173.gc9b40\" \\\n                    --no-verbose \\\n                    --archive=\"test-results/git-smoke.tar.gz\" \\\n                    t0000-basic.sh t0001-init.sh t0002-gitfile.sh t0003-attributes.sh t0004-unwritable.sh t0005-signals.sh t0006-date.sh\n    t0000-basic.sh ....... ok\n    t0001-init.sh ........ ok\n    t0002-gitfile.sh ..... ok\n    t0003-attributes.sh .. ok\n    t0004-unwritable.sh .. ok\n    t0005-signals.sh ..... ok\n    t0006-date.sh ........ ok\n    All tests successful.\n\n    Test Summary Report\n    -------------------\n    t0000-basic.sh     (Wstat: 0 Tests: 46 Failed: 0)\n      TODO passed:   5\n    Files=7, Tests=134,  3 wallclock secs ( 0.06 usr  0.05 sys +  0.23 cusr  1.33 csys =  1.67 CPU)\n    Result: PASS\n\n    TAP Archive created at /home/avar/g/git/t/test-results/git-smoke.tar.gz\n\nThe smoke target uses TAP::Harness::Archive to aggregate the test\nresults into a tarball. The tarball contains two things, the output of\nevery test file that was run, and a metadata file:\n\nTarball contents:\n\n    $ tar xzvf git-smoke.tar.gz\n    t0004-unwritable.sh\n    t0001-init.sh\n    t0002-gitfile.sh\n    t0005-signals.sh\n    t0000-basic.sh\n    t0003-attributes.sh\n    t0006-date.sh\n    meta.yml\n\nA test report, this could also include --verbose output:\n\n    $ cat t0005-signals.sh\n    ok 1 - sigchain works\n    # passed all 1 test(s)\n    1..1\n\nA metadata file:\n\n    ---\n    extra_properties:\n      git:\n        version: 1.7.2.1.173.gc9b40\n    file_attributes:\n      -\n        description: t0000-basic.sh\n        end_time: 1280437324.61398\n        start_time: 1280437324.22186\n      -\n        description: t0001-init.sh\n        end_time: 1280437325.12346\n        start_time: 1280437324.62393\n      -\n        description: t0002-gitfile.sh\n        end_time: 1280437325.29428\n        start_time: 1280437325.13646\n      -\n        description: t0003-attributes.sh\n        end_time: 1280437325.59678\n        start_time: 1280437325.30565\n      -\n        description: t0004-unwritable.sh\n        end_time: 1280437325.77376\n        start_time: 1280437325.61003\n      -\n        description: t0005-signals.sh\n        end_time: 1280437325.85426\n        start_time: 1280437325.78727\n      -\n        description: t0006-date.sh\n        end_time: 1280437326.2362\n        start_time: 1280437325.86768\n    file_order:\n      - t0000-basic.sh\n      - t0001-init.sh\n      - t0002-gitfile.sh\n      - t0003-attributes.sh\n      - t0004-unwritable.sh\n      - t0005-signals.sh\n      - t0006-date.sh\n    start_time: 1280437324\n    stop_time: 1280437326\n\nThe \"extra_properties\" hash is where we'd stick Git-specific info,\nlike whether Git was compiled with gettext or the fallback regex\nengine.\n\nThe entire tarball is then submitted to a central smoke\naggregator. Currently this is done with curl over HTTP, but could also\nbe done e.g. via E-Mail:\n\n    curl \\\n        -F architecture=amd64 \\\n        -F platform=linux \\\n        -F revision=\"$(GIT_VERSION)\" \\\n        -F report_file=@test-results/git-smoke.tar.gz \\\n        http://git.smoke.example.net/submit_report\n\nThe aggregator would make both the raw test reports available, and\nmight format them with a web interface. Smolder (on CPAN) is one\nexample of the latter. Here are smoke reports for the Rakudo project\non Smolder:\n\n    http://smolder.plusthree.com/app/projects/smoke_reports/18\n\nTODO:\n\n  - Is this worthwhile. Are there developers / packagers / other\n    interested parties here who'd be interested in actually running\n    smoke testers? It should be really easy to set one up.\n\n  - How do I get things like PERL_PATH and uname_M from the top-level\n    Makefile? Currently I just hardcode e.g. \"perl\" and\n    \"architecture=amd64\". Maybe this needs to be a top-level target\n    instead?\n\n  - Set up the smoke aggregator. I was running into some issues with\n    smolder, but those are solvable given some time. I can run and\n    maintain the smoke aggregator if this gets accepted.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n t/Makefile |   20 ++++++++++++++++++++\n t/harness  |   36 ++++++++++++++++++++++++++++++++++++\n 2 files changed, 56 insertions(+), 0 deletions(-)\n create mode 100755 t/harness\n\ndiff --git a/t/Makefile b/t/Makefile\nindex 819b936..459a667 100644\n--- a/t/Makefile\n+++ b/t/Makefile\n@@ -49,4 +49,24 @@ full-svn-test:\n valgrind:\n \tGIT_TEST_OPTS=--valgrind $(MAKE)\n \n+test-results:\n+\tmkdir -p test-results\n+\n+-include ../GIT-VERSION-FILE\n+test-results/git-smoke.tar.gz:\n+\tperl ./harness --git-version=\"$(GIT_VERSION)\" \\\n+\t\t--no-verbose \\\n+\t\t--archive=\"test-results/git-smoke.tar.gz\" \\\n+\t\t$(wildcard t000[0-9]-*.sh)\n+\n+smoke: test-results/git-smoke.tar.gz\n+\n+smoke_report: smoke\n+\tcurl \\\n+\t\t-F architecture=amd64 \\\n+\t\t-F platform=linux \\\n+\t\t-F revision=\"$(GIT_VERSION)\" \\\n+\t\t-F report_file=@test-results/git-smoke.tar.gz \\\n+\t\thttp://git.smoke.example.net/submit_report\n+\n .PHONY: pre-clean $(T) aggregate-results clean valgrind\ndiff --git a/t/harness b/t/harness\nnew file mode 100755\nindex 0000000..72b4af6\n--- /dev/null\n+++ b/t/harness\n@@ -0,0 +1,36 @@\n+#!/usr/bin/perl\n+use 5.010;\n+use strict;\n+use warnings;\n+use Pod::Usage ();\n+use Getopt::Long ();\n+use TAP::Harness::Archive;\n+\n+Getopt::Long::Parser->new(\n+    config => [ qw/ pass_through / ],\n+)->getoptions(\n+    'h|help'        => \\my $help,\n+    'jobs:1'        => \\my $jobs,\n+    'verbose!'      => \\(my $verbose = 1),\n+    'git-version=s' => \\my $git_version,\n+    'archive=s'     => \\my $archive,\n+) or die \"$0: Couldn't getoptions()\";\n+\n+my @tests = @ARGV;\n+\n+my $harness = TAP::Harness::Archive->new({\n+    verbosity => 0,\n+    jobs      => $ENV{TEST_JOBS} || $jobs || 1,\n+    test_args => [\n+        ($verbose\n+         ? qw/ --verbose /\n+         : ())\n+    ],\n+    archive   => $archive,\n+    extra_properties => {\n+        git => {\n+            version => $git_version,\n+        },\n+    }\n+});\n+$harness->runtests(@tests);\n-- \n1.7.1\n"},{"id":"146738","messageId":"201007300011.50330.trast@student.ethz.ch","threadId":"24576","inReplyTo":"1280438455-16255-1-git-send-email-avarab@gmail.com","subject":"Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2010-07-29T22:11:50Z","receivedAt":"2010-07-29T22:11:50Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n>   - Is this worthwhile. Are there developers / packagers / other\n>     interested parties here who'd be interested in actually running\n>     smoke testers? It should be really easy to set one up.\n\nI'm all for it!\n\nI think I could put a cronjob on a RHEL5.4 machine, and regularly run\nit on my own openSuSE 11.3 install.\n\n> Tarball contents:\n> \n>     $ tar xzvf git-smoke.tar.gz\n>     t0004-unwritable.sh\n>     t0001-init.sh\n>     t0002-gitfile.sh\n>     t0005-signals.sh\n>     t0000-basic.sh\n>     t0003-attributes.sh\n>     t0006-date.sh\n>     meta.yml\n\nThat's the only thing I found confusing about this: why are they named\nas if they were shellscripts?\n\nAlso, installing TAP::Harness::Archive was a bit hairy but that's\nCPAN's fault...\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"146739","messageId":"201007300015.57045.trast@student.ethz.ch","threadId":"24576","inReplyTo":"1280438455-16255-1-git-send-email-avarab@gmail.com","subject":"Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2010-07-29T22:15:56Z","receivedAt":"2010-07-29T22:15:56Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n> \n> Currently we only notice bugs in the test suite when it's run\n> manually. Bugs in Git that only occur on obscure platforms or setups\n> that the core developers aren't using may thus go unnoticed until the\n> bug makes it into a release.\n\nBTW, below is the script I have devised to automatically run the tests\nunder valgrind and then bisect any offenders.  (It keeps exposing odd\ntest failures and stealing my time tracking them down...)\n\nIt gives fairly good results, but since it's also rather kludgy I want\nto test and improve it a bit more before shooting for contrib (if\nanything).\n\nNote that running this will take on the order of hours at least.\n\n---- 8< ----\n#!/bin/sh\n\nMAILTO=tr@thomasrast.ch\n\nbranch=\"${1:-next}\"\nlogfile=\"$(pwd)/bisection-log-$$\"\n\nexport DIFF=diff # stupid bug\n\ndie () {\n\t(echo \"Error message: $*\"; echo '-----'; cat \"$logfile\") |\n\tmail -s \"Testing $branch: die() called!\" \"$MAILTO\"\n\techo \"fatal: $*\" >&2\n\texit 1\n}\n\ngit fetch origin 2>&1 | tee \"$logfile\" || die \"fetch failed\"\n\n# test if we've already done this\ntest \"$(git rev-parse last_known_good_$branch)\" = \"$(git rev-parse origin/$branch)\" && exit\n\ngit checkout -f origin/\"$branch\" 2>&1 | tee \"$logfile\" || die \"checkout failed (can't happen)\"\n\nresults=\"test-results.$(git describe)\"\nmkdir \"$results\"\n\nmake -j12 2>&1 | tee -a \"$logfile\" || die \"initial compilation failed?\"\nmake -k -j8 test 2>&1 | tee -a \"$logfile\"\n\nif [ ! -d t/\"test-results\" ]; then\n    mail -s \"Valgrind-tested $branch: all good!\" \"$MAILTO\" < \"$logfile\"\n    git tag -f last_known_good_$branch origin/$branch\n    rm \"$logfile\"\n    exit\nfi\n\ncd t/\ncp -a test-results \"$results\"\n( cd $results && perl -i -ne 'print unless /^==.*execve/i' *.out )\nfailing_normally=$(cd \"$results\" && grep -L '^0$' *.exit)\nfailing_valgrind=$(cd \"$results\" && grep -lE '^==[0-9]+==' *.out)\ncd ..\n\necho \"failed (normal):\" $failing_normally | tee -a \"$logfile\"\necho \"failed (valgrind):\" $failing_valgrind | tee -a \"$logfile\"\n\nif [ -z \"$failing_normally\" -a -z \"$failing_valgrind\" ]; then\n    mail -s \"Valgrind-tested $branch: all good!\" \"$MAILTO\" < \"$logfile\"\n    git tag -f last_known_good_$branch origin/$branch\n    rm \"$logfile\"\n    exit\nfi\n\nmail -s \"Valgrind-testing $branch: starting test bisection\" \"$MAILTO\" < \"$logfile\"\n\nfor test_out in $failing_valgrind; do\n    test=\"${test_out%.out}\"\n    echo \"bisecting valgrind-failing test $test\"\n    git bisect start > t/\"$results\"/$test.bisect 2>&1\n    git bisect good last_known_good_pu last_known_good_next 2>&1 | tee t/\"$results\"/$test.bisect\n    git bisect bad origin/$branch 2>&1 | tee -a t/\"$results\"/$test.bisect\n    git bisect run sh -c \"test ! -f t/$test.sh || { make -j12 && cd t && ./$test.sh --valgrind --tee -i && ! grep -E '^==[0-9]+==' test-results/$test.out | grep -vi execve; }\" 2>&1 | tee -a t/\"$results\"/$test.bisect\n    git bisect log 2>&1 | tee -a t/\"$results\"/$test.bisect\n    git bisect reset\n    mail -s \"Bisection results for $test (valgrind)\" \"$MAILTO\" < t/\"$results\"/$test.bisect\ndone\n\nfor test_out in $failing_normally; do\n    test=\"${test_out%.exit}\"\n    case \"$failing_valgrind\" in\n\t*$test.out*)\n\t    continue\n\t    ;;\n    esac\n    echo \"bisecting failing test $test\"\n    git bisect start 2>&1 | tee t/\"$results\"/$test.bisect 2>&1\n    git bisect good last_known_good_pu last_known_good_pu 2>&1 | tee -a t/\"$results\"/$test.bisect 2>&1\n    git bisect bad origin/$branch 2>&1 | tee -a t/\"$results\"/$test.bisect 2>&1\n    git bisect run sh -c \"test ! -f t/$test.sh || { make -j12 && cd t && ./$test.sh --tee -i; }\" 2>&1 | tee -a t/\"$results\"/$test.bisect 2>&1\n    git bisect log | tee -a t/\"$results\"/$test.bisect\n    git bisect reset\n    mail -s \"Bisection results for $test\" \"$MAILTO\" < t/\"$results\"/$test.bisect\ndone\n\nrm \"$logfile\"\n---- >8 ----\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"146742","messageId":"AANLkTikg5uD27sYE-AYCYhTXXaC4LReWPxiTsxrVUqo+@mail.gmail.com","threadId":"24576","inReplyTo":"201007300011.50330.trast@student.ethz.ch","subject":"Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-07-29T22:26:25Z","receivedAt":"2010-07-29T22:26:25Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Thu, Jul 29, 2010 at 22:11, Thomas Rast <trast@student.ethz.ch> wrote:\n> Ævar Arnfjörð Bjarmason wrote:\n>>   - Is this worthwhile. Are there developers / packagers / other\n>>     interested parties here who'd be interested in actually running\n>>     smoke testers? It should be really easy to set one up.\n>\n> I'm all for it!\n>\n> I think I could put a cronjob on a RHEL5.4 machine, and regularly run\n> it on my own openSuSE 11.3 install.\n\nThat's at least three smokers there. And since your RHEL5.4 machine\nalready turned up a gettext bug..\n\n>> Tarball contents:\n>>\n>>     $ tar xzvf git-smoke.tar.gz\n>>     t0004-unwritable.sh\n>>     t0001-init.sh\n>>     t0002-gitfile.sh\n>>     t0005-signals.sh\n>>     t0000-basic.sh\n>>     t0003-attributes.sh\n>>     t0006-date.sh\n>>     meta.yml\n>\n> That's the only thing I found confusing about this: why are they named\n> as if they were shellscripts?\n\nThe output file names just match the test names, which in this case\nare shellscripts.\n\n> Also, installing TAP::Harness::Archive was a bit hairy but that's\n> CPAN's fault...\n\nThis is something we can probably make really easy if we write some\nsupporting scripts with cpanminus + local::lib. I.e. just have a\nconfig file like:\n\n  ~/.gitsmoker:\n    repository = ~/g/git\n    data       = ~/g/git-smoker\n\nWhere the git-smoker would maintain the state, dependencies etc. It\nneeds.\n"},{"id":"146777","messageId":"20100730123443.GA11936@coredump.intra.peff.net","threadId":"24576","inReplyTo":"1280438455-16255-1-git-send-email-avarab@gmail.com","subject":"Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-07-30T12:34:43Z","receivedAt":"2010-07-30T12:34:43Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Jul 29, 2010 at 09:20:55PM +0000, Ævar Arnfjörð Bjarmason wrote:\n\n>   - Is this worthwhile. Are there developers / packagers / other\n>     interested parties here who'd be interested in actually running\n>     smoke testers? It should be really easy to set one up.\n\nA few of us were running automated build/tests for a while. Check out:\n\n  http://repo.or.cz/w/git/gitbuild.git\n\nespecially:\n\n  http://repo.or.cz/w/git/gitbuild.git/tree/platform\n\nUnfortunately the SunOS and FreeBSD machines I tested on went away, so I\nam not actually running anything automated anymore. Mike Ralphson was\ntesting on AIX, but seems to have stopped, as well.\n\nI think these days Junio runs the test suite through a couple of VMs,\nbut I don't know exactly which platforms, or how often he does so.\n\n-Peff\n"},{"id":"146785","messageId":"7v39v1rlq1.fsf@alter.siamese.dyndns.org","threadId":"24576","inReplyTo":"20100730123443.GA11936@coredump.intra.peff.net","subject":"Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-07-30T16:13:58Z","receivedAt":"2010-07-30T16:13:58Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King <peff@peff.net> writes:\n\n> I think these days Junio runs the test suite through a couple of VMs,\n> but I don't know exactly which platforms, or how often he does so.\n\nThe normal \"before push-out\" procedure for me is:\n\n - On Debian5 (x86_64 -- this is my primary box): build, build docs, run\n   tests, install for all four integration branches (Dothem script from\n   'todo' branch, whose checkout I have in Meta/, is used for this).\n\n - Push the four branches and run Dothem on k.org's FC11 (x86_64).\n\n - VMs running FC11 (i386) and FBSD80 (i386) run the same \"Dothem\" script,\n   modulo that t9xxx series of tests which take too much time are skipped,\n   when all four branches passes tests on my primary box successfully.\n\nI push the result out after the four branches are Ok on my primary box and\nk.org's FC11 (iow, I do not wait for VM tests to finish).\n"},{"id":"147442","messageId":"20100808134238.GA9659@book.hvoigt.net","threadId":"24576","inReplyTo":"201007300011.50330.trast@student.ethz.ch","subject":"Re: Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2010-08-08T13:42:38Z","receivedAt":"2010-08-08T13:42:38Z","isPatch":true,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"On Fri, Jul 30, 2010 at 12:11:50AM +0200, Thomas Rast wrote:\n> Ævar Arnfjörð Bjarmason wrote:\n> >   - Is this worthwhile. Are there developers / packagers / other\n> >     interested parties here who'd be interested in actually running\n> >     smoke testers? It should be really easy to set one up.\n> \n> I'm all for it!\n\nMe too! I should be able to setup a cronjob for tests under a Windows XP\nmachine. Does that count as an obscure platform ? ;)\n\ncheers Heiko\n"},{"id":"147448","messageId":"AANLkTimdFz38gfq1oW0VQ9giaavFnqRUH8DDEeoFN=BT@mail.gmail.com","threadId":"24576","inReplyTo":"20100808134238.GA9659@book.hvoigt.net","subject":"Re: Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-08T14:54:21Z","receivedAt":"2010-08-08T14:54:21Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Sun, Aug 8, 2010 at 13:42, Heiko Voigt <hvoigt@hvoigt.net> wrote:\n> On Fri, Jul 30, 2010 at 12:11:50AM +0200, Thomas Rast wrote:\n>> Ćvar Arnfjörđ Bjarmason wrote:\n>> >   - Is this worthwhile. Are there developers / packagers / other\n>> >     interested parties here who'd be interested in actually running\n>> >     smoke testers? It should be really easy to set one up.\n>>\n>> I'm all for it!\n>\n> Me too! I should be able to setup a cronjob for tests under a Windows XP\n> machine. Does that count as an obscure platform ? ;)\n\nI think it does :)\n\nI just sent another version of the series to the list. It'd be very\nuseful if you could try sending a smoke report from Windows XP.\n\nThanks.\n"},{"id":"147541","messageId":"20100809195608.GA16478@book.hvoigt.net","threadId":"24576","inReplyTo":"AANLkTimdFz38gfq1oW0VQ9giaavFnqRUH8DDEeoFN=BT@mail.gmail.com","subject":"Re: Re: Re: [PATCH/RFC] tests: WIP Infrastructure for Git smoke testing","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2010-08-09T19:56:08Z","receivedAt":"2010-08-09T19:56:08Z","isPatch":true,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"On Sun, Aug 08, 2010 at 02:54:21PM +0000, Ævar Arnfjörð Bjarmason wrote:\n> On Sun, Aug 8, 2010 at 13:42, Heiko Voigt <hvoigt@hvoigt.net> wrote:\n> > On Fri, Jul 30, 2010 at 12:11:50AM +0200, Thomas Rast wrote:\n> >> Ćvar Arnfjörđ Bjarmason wrote:\n> >> >   - Is this worthwhile. Are there developers / packagers / other\n> >> >     interested parties here who'd be interested in actually running\n> >> >     smoke testers? It should be really easy to set one up.\n> >>\n> >> I'm all for it!\n> >\n> > Me too! I should be able to setup a cronjob for tests under a Windows XP\n> > machine. Does that count as an obscure platform ? ;)\n> \n> I think it does :)\n> \n> I just sent another version of the series to the list. It'd be very\n> useful if you could try sending a smoke report from Windows XP.\n\nI tried to do it yesterday but unfortunately some of the tests seem to\nhang on Windows so I could not complete the report. I will try to\ngenerate a skip list and run the smoke_report again later.\n\ncheers Heiko\n"}]}