{"thread":{"id":"24608","subject":"[PATCH 0/2] Smoke testing for Git","startedAt":"2010-08-02T20:24:42Z","lastAt":"2010-08-02T22:58:14Z","messageCount":14,"participants":["Ævar Arnfjörð Bjarmason","Sverre Rabbelier","A Large Angry SCM","Jonathan Nieder","Junio C Hamano","Avery Pennarun"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"146985","messageId":"1280780684-26344-1-git-send-email-avarab@gmail.com","threadId":"24608","inReplyTo":null,"subject":"[PATCH 0/2] Smoke testing for Git","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-02T20:24:42Z","receivedAt":"2010-08-02T20:24:42Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Here's a non-RFC version of the smoke testing for Git series. It's\nlike v2 of the RFC aside from a s/sever/server/ typo noted by Junio:\n\nÆvar Arnfjörð Bjarmason (2):\n tests: Infrastructure for Git smoke testing\n t/README: Document the Smoke testing\n\n t/Makefile | 35 ++++++++++++++++++++++++++++++-\n t/README | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n t/harness | 21 +++++++++++++++++++\n 3 files changed, 121 insertions(+), 1 deletions(-)\n create mode 100755 t/harness\n"},{"id":"146986","messageId":"1280780684-26344-2-git-send-email-avarab@gmail.com","threadId":"24608","inReplyTo":"1280780684-26344-1-git-send-email-avarab@gmail.com","subject":"[PATCH 1/2] tests: Infrastructure for Git smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-02T20:24:43Z","receivedAt":"2010-08-02T20:24:43Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Add the capability to send smoke reports from 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 can thus go unnoticed.\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, include\nbisecting functionality or run the tests under valgrind. Doing that is\noutside the scope of this patch, this just adds a report submission\nmechanism. But including a canonical smoke runner is something we'll\nwant to include eventually.\n\nWhat this does now is add smoke and smoke_report targets to t/Makefile\n(this example only uses a few tests for demonstration):\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:\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 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'll stick Git-specific info,\nlike whether Git was compiled with gettext or the fallback regex\nengine, and what branch we're compiling. Currently no metadata like\nthis is included.\n\nThe entire tarball is then submitted to a central smokebox at\nsmoke.git.nix.is. This is done with curl(1) via the \"smoke_report\"\ntarget:\n\n $ make smoke_report\n curl \\\n -H \"Expect: \" \\\n -F project=Git \\\n -F architecture=x86_64 \\\n -F platform=Linux \\\n -F revision=\"1.7.2.1.173.gc9b40\" \\\n -F report_file=@test-results/git-smoke.tar.gz \\\n http://smoke.git.nix.is/app/projects/process_add_report/1 \\\n | grep -v ^Redirecting\n % Total % Received % Xferd Average Speed Time Time Time Current\n Dload Upload Total Spent Left Speed\n 100 117k 100 63 100 117k 3 6430 0:00:21 0:00:18 0:00:03 0\n Reported #8 added.\n\nReports are then made available on the smokebox via a web interface:\n\n http://smoke.git.nix.is/app/projects/smoke_reports/1\n\nThe smoke reports are also mirrored to a Git repository hosted on\nGitHub:\n\n http://github.com/gitsmoke/smoke-reports\n\nThe Smolder SQLite database that contains metadata about the reports\nis also made available:\n\n http://github.com/gitsmoke/smoke-database\n\nSigned-off-by: Ævar Arnfjörð Bjarmason \n---\n t/Makefile | 35 ++++++++++++++++++++++++++++++++++-\n t/harness | 21 +++++++++++++++++++++\n 2 files changed, 55 insertions(+), 1 deletions(-)\n create mode 100755 t/harness\n\ndiff --git a/t/Makefile b/t/Makefile\nindex 819b936..169097d 100644\n--- a/t/Makefile\n+++ b/t/Makefile\n@@ -49,4 +49,37 @@ full-svn-test:\n valgrind:\n \tGIT_TEST_OPTS=--valgrind $(MAKE)\n \n-.PHONY: pre-clean $(T) aggregate-results clean valgrind\n+# Smoke testing targets\n+-include ../GIT-BUILD-OPTIONS\n+-include ../GIT-VERSION-FILE\n+uname_S := $(shell sh -c 'uname -s 2>/dev/null || echo unknown')\n+uname_M := $(shell sh -c 'uname -m 2>/dev/null || echo unknown')\n+\n+test-results:\n+\tmkdir -p test-results\n+\n+test-results/git-smoke.tar.gz:\n+\t$(PERL_PATH) ./harness \\\n+\t\t--archive=\"test-results/git-smoke.tar.gz\" \\\n+\t\t$(T)\n+\n+smoke: test-results/git-smoke.tar.gz\n+\n+SMOKE_UPLOAD_FLAGS =\n+ifdef SMOKE_USERNAME\n+\tSMOKE_UPLOAD_FLAGS += -F username=$(SMOKE_USERNAME) -F password=$(SMOKE_PASSWORD)\n+endif\n+\n+smoke_report: smoke\n+\tcurl \\\n+\t\t-H \"Expect: \" \\\n+\t\t-F project=Git \\\n+\t\t-F architecture=$(uname_M) \\\n+\t\t-F platform=$(uname_S) \\\n+\t\t-F revision=\"$(GIT_VERSION)\" \\\n+\t\t-F report_file=@test-results/git-smoke.tar.gz \\\n+\t\t$(SMOKE_UPLOAD_FLAGS) \\\n+\t\thttp://smoke.git.nix.is/app/projects/process_add_report/1 \\\n+\t| grep -v ^Redirecting\n+\n+.PHONY: pre-clean $(T) aggregate-results clean valgrind smoke smoke_report\ndiff --git a/t/harness b/t/harness\nnew file mode 100755\nindex 0000000..f5c02f4\n--- /dev/null\n+++ b/t/harness\n@@ -0,0 +1,21 @@\n+#!/usr/bin/perl\n+use strict;\n+use warnings;\n+use Getopt::Long ();\n+use TAP::Harness::Archive;\n+\n+Getopt::Long::Parser->new(\n+\tconfig => [ qw/ pass_through / ],\n+)->getoptions(\n+\t'jobs:1' => \\(my $jobs = $ENV{TEST_JOBS}),\n+\t'archive=s' => \\my $archive,\n+) or die \"$0: Couldn't getoptions()\";\n+\n+TAP::Harness::Archive->new({\n+\tjobs => $jobs,\n+\tarchive => $archive,\n+\t($ENV{GIT_TEST_OPTS}\n+\t ? (test_args => [ split /\\s+/, $ENV{GIT_TEST_OPTS} ])\n+\t : ()),\n+\textra_properties => {},\n+})->runtests(@ARGV);\n-- \n1.7.1\n"},{"id":"146987","messageId":"1280780684-26344-3-git-send-email-avarab@gmail.com","threadId":"24608","inReplyTo":"1280780684-26344-1-git-send-email-avarab@gmail.com","subject":"[PATCH 2/2] t/README: Document the Smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-02T20:24:44Z","receivedAt":"2010-08-02T20:24:44Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Git now has a smoke testing service at http://smoke.git.nix.is that\nanyone can send reports to. Change the t/README file to mention this.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason \n---\n t/README | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n 1 files changed, 66 insertions(+), 0 deletions(-)\n\ndiff --git a/t/README b/t/README\nindex e957d4f..69af05f 100644\n--- a/t/README\n+++ b/t/README\n@@ -574,3 +574,69 @@ Then, at the top-level:\n That'll generate a detailed cover report in the \"cover_db_html\"\n directory, which you can then copy to a webserver, or inspect locally\n in a browser.\n+\n+Smoke testing\n+-------------\n+\n+The Git test suite has support for smoke testing. Smoke testing is\n+when you submit the results of a test run to a central server for\n+analysis and aggregation.\n+\n+Running a smoke tester is an easy and valuable way of contributing to\n+Git development, particularly if you have access to an uncommon OS on\n+obscure hardware.\n+\n+After building Git you can generate a smoke report like this in the\n+\"t\" directory:\n+\n+ make clean smoke\n+\n+You can also pass arguments via the environment. This should make it\n+faster:\n+\n+ GIT_TEST_OPTS='--root=/dev/shm' TEST_JOBS=10 make clean smoke\n+\n+The \"smoke\" target will run the Git test suite with Perl's\n+\"TAP::Harness\" module, and package up the results in a .tar.gz archive\n+with \"TAP::Harness::Archive\". The former is included with Perl v5.10.1\n+or later, but you'll need to install the latter from the CPAN. See the\n+\"Test coverage\" section above for how you might do that.\n+\n+Once the \"smoke\" target finishes you'll see a message like this:\n+\n+ TAP Archive created at /t/test-results/git-smoke.tar.gz\n+\n+To upload the smoke report you need to have curl(1) installed, then\n+do:\n+\n+ make smoke_report\n+\n+To upload the report anonymously. Hopefully that'll return something\n+like \"Reported #7 added.\".\n+\n+If you're going to be uploading reports frequently please request a\n+user account by E-Mailing gitsmoke@v.nix.is. Once you have a username\n+and password you'll be able to do:\n+\n+ SMOKE_USERNAME= SMOKE_PASSWORD= make smoke_report\n+\n+Once the report is uploaded it'll be made available at\n+http://smoke.git.nix.is, here's an overview of Recent Smoke Reports\n+for Git:\n+\n+ http://smoke.git.nix.is/app/projects/smoke_reports/1\n+\n+The reports will also be mirrored to GitHub every few hours:\n+\n+ http://github.com/gitsmoke/smoke-reports\n+\n+The Smolder SQLite database is also mirrored and made available for\n+download:\n+\n+ http://github.com/gitsmoke/smoke-database\n+\n+Note that the database includes hashed (with crypt()) user passwords\n+and E-Mail addresses. Don't use a valuable password for the smoke\n+service if you have an account, or an E-Mail address you don't want to\n+be publicly known. The user accounts are just meant to be convenient\n+labels, they're not meant to be secure.\n-- \n1.7.1\n"},{"id":"146989","messageId":"AANLkTim2EY7AACe=UzbG-k7oteV6UMmfPAQMEOFn0iZ7@mail.gmail.com","threadId":"24608","inReplyTo":"1280780684-26344-3-git-send-email-avarab@gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-08-02T20:54:41Z","receivedAt":"2010-08-02T20:54:41Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Mon, Aug 2, 2010 at 15:24, Ævar Arnfjörð Bjarmason wrote:\n> Git now has a smoke testing service at http://smoke.git.nix.is that\n> anyone can send reports to. Change the t/README file to mention this.\n\nCan't we run this somewhere a little less \"shabby\"? I'd hate to\nintroduce Yet Another Official Git Site (I'm really glad for example\nthat the Git Wiki is now on kernel.org). Is it not possible to move\nthis to git-scm.com, kernel.org, or something like that?\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"146992","messageId":"4C5732CE.10906@gmail.com","threadId":"24608","inReplyTo":"AANLkTim2EY7AACe=UzbG-k7oteV6UMmfPAQMEOFn0iZ7@mail.gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"A Large Angry SCM","fromEmail":"gitzilla@gmail.com","sentAt":"2010-08-02T21:04:14Z","receivedAt":"2010-08-02T21:04:14Z","isPatch":true,"sender":{"key":"gitzilla@gmail.com","avatar":"https://gravatar.com/avatar/354625c442439908ff3dd99757dee330e29e9df7847472384faf7a00add247fb?d=mp&s=160"},"body":"On 08/02/2010 04:54 PM, Sverre Rabbelier wrote:\n> Heya,\n>\n> On Mon, Aug 2, 2010 at 15:24, Ævar Arnfjörð Bjarmason wrote:\n>> Git now has a smoke testing service at http://smoke.git.nix.is that\n>> anyone can send reports to. Change the t/README file to mention this.\n>\n> Can't we run this somewhere a little less \"shabby\"? I'd hate to\n> introduce Yet Another Official Git Site (I'm really glad for example\n> that the Git Wiki is now on kernel.org). Is it not possible to move\n> this to git-scm.com, kernel.org, or something like that?\n>\n\nAnd what's on the site tells us almost nothing about the tested systems.\n"},{"id":"147000","messageId":"AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com","threadId":"24608","inReplyTo":"4C5732CE.10906@gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-02T22:00:26Z","receivedAt":"2010-08-02T22:00:26Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM wrote:\n> On 08/02/2010 04:54 PM, Sverre Rabbelier wrote:\n>>\n>> Heya,\n>>\n>> On Mon, Aug 2, 2010 at 15:24, Ævar Arnfjörð Bjarmason\n>>  wrote:\n>>>\n>>> Git now has a smoke testing service at http://smoke.git.nix.is that\n>>> anyone can send reports to. Change the t/README file to mention this.\n>>\n>> Can't we run this somewhere a little less \"shabby\"? I'd hate to\n>> introduce Yet Another Official Git Site (I'm really glad for example\n>> that the Git Wiki is now on kernel.org). Is it not possible to move\n>> this to git-scm.com, kernel.org, or something like that?\n\nDo you not like the domain, that the domain's A record points to a\nLinode box, or both?\n\nI don't mind where a smoke server gets hosted, I just want it to be\nthere. But someone's going to have to host it and maintain it.\n\nUnless someone else wants to do that it's going to have to either be\nat a box I control, or someone else will need to give me shell access.\n\nOf course just changing the domain would be trivial, just a matter of\nsomeone setting up an A record somewhere, or delegating a zone to me.\n\nAn alternative would be to change how this works, e.g. making\nsubmissions go by E-Mail to a public list, or having smokers push them\nto public Git repositories which would be registered somewhere.\n\nBut that'd require more development and setup work. The current system\nisn't optimal, but it works. It can always me moved somewhere else\nlater if smoke testing for Git takes off.\n\n> And what's on the site tells us almost nothing about the tested systems.\n\nCan you be more specific? What information do you find lacking at\nhttp://smoke.git.nix.is/app/projects/smoke_reports/1 ?\n"},{"id":"147002","messageId":"AANLkTinNwUsYuB0Wb3aT5ZpnzT24YpmphCEE_TwTPgsG@mail.gmail.com","threadId":"24608","inReplyTo":"AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-08-02T22:05:50Z","receivedAt":"2010-08-02T22:05:50Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\n[+Warthog9]\n\nOn Mon, Aug 2, 2010 at 17:00, Ævar Arnfjörð Bjarmason wrote:\n> Do you not like the domain, that the domain's A record points to a\n> Linode box, or both?\n\nThe former.\n\n> I don't mind where a smoke server gets hosted, I just want it to be\n> there. But someone's going to have to host it and maintain it.\n\nAgreed.\n\n> Of course just changing the domain would be trivial, just a matter of\n> someone setting up an A record somewhere, or delegating a zone to me.\n\nJohn, is it possible to have smoke.git.kernel.org (or such a domain)\neither point at a server Ævar controls, or to give him a shell account\nthere? The point is to have http://smoke.git.nix.is/ hosted on a more\n\"Gitty\" domain.\n\n> An alternative would be to change how this works, e.g. making\n> submissions go by E-Mail to a public list, or having smokers push them\n> to public Git repositories which would be registered somewhere.\n\nI like the idea of having it be a public Git repo since that would\nprobably make it easier to do maintenance on the repo (e.g., revert\n\"vandalism\"), but there still needs to be a frontend of sorts\nsomewhere :).\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"147004","messageId":"20100802221328.GA3826@burratino","threadId":"24608","inReplyTo":"AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2010-08-02T22:13:28Z","receivedAt":"2010-08-02T22:13:28Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n> On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM wrote:\n\n>> And what's on the site tells us almost nothing about the tested systems.\n>\n> Can you be more specific? What information do you find lacking at\n> http://smoke.git.nix.is/app/projects/smoke_reports/1 ?\n\nOperating system (i.e., distro). Precise CPU architecture. Number of\nCPUs. Available memory. Which tests were skipped and which had expected\nfailures. Configuration used to build git.\n\n(I understand that requiring all that information could prevent people\nfrom running smoke servers, so I don’t mean to say it all should be\nrequired.)\n"},{"id":"147005","messageId":"4C5743D9.108@gmail.com","threadId":"24608","inReplyTo":"AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"A Large Angry SCM","fromEmail":"gitzilla@gmail.com","sentAt":"2010-08-02T22:16:57Z","receivedAt":"2010-08-02T22:16:57Z","isPatch":true,"sender":{"key":"gitzilla@gmail.com","avatar":"https://gravatar.com/avatar/354625c442439908ff3dd99757dee330e29e9df7847472384faf7a00add247fb?d=mp&s=160"},"body":"On 08/02/2010 06:00 PM, Ævar Arnfjörð Bjarmason wrote:\n> On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM wrote:\n[...]\n>> And what's on the site tells us almost nothing about the tested systems.\n>\n> Can you be more specific? What information do you find lacking at\n> http://smoke.git.nix.is/app/projects/smoke_reports/1 ?\n\nThe only information available there is that the tested system was some \nLinux on an x86_64 and the particular git version tested. My complaint \nis that \"Linux\" is _way_ too generic to be useful when trying to get an \nidea of where things are known to work and where they are known not to work.\n"},{"id":"147008","messageId":"AANLkTinLSdp5TLjrisbX27UrRGGZq+D1-84kwOpHCR3p@mail.gmail.com","threadId":"24608","inReplyTo":"AANLkTinNwUsYuB0Wb3aT5ZpnzT24YpmphCEE_TwTPgsG@mail.gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-02T22:28:57Z","receivedAt":"2010-08-02T22:28:57Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Aug 2, 2010 at 22:05, Sverre Rabbelier wrote:\n> On Mon, Aug 2, 2010 at 17:00, Ævar Arnfjörð Bjarmason wrote:\n>> Do you not like the domain, that the domain's A record points to a\n>> Linode box, or both?\n>\n> The former.\n>\n>> I don't mind where a smoke server gets hosted, I just want it to be\n>> there. But someone's going to have to host it and maintain it.\n>\n> Agreed.\n>\n>> Of course just changing the domain would be trivial, just a matter of\n>> someone setting up an A record somewhere, or delegating a zone to me.\n>\n> John, is it possible to have smoke.git.kernel.org (or such a domain)\n> either point at a server Ævar controls, or to give him a shell account\n> there? The point is to have http://smoke.git.nix.is/ hosted on a more\n> \"Gitty\" domain.\n\nNote that that may be a bit premature, since Junio hasn't commented on\nwhether he wants this at all yet.\n\n>> An alternative would be to change how this works, e.g. making\n>> submissions go by E-Mail to a public list, or having smokers push them\n>> to public Git repositories which would be registered somewhere.\n>\n> I like the idea of having it be a public Git repo since that would\n> probably make it easier to do maintenance on the repo (e.g., revert\n> \"vandalism\"), but there still needs to be a frontend of sorts\n> somewhere :).\n\nNote that all the data is already in Git[1] it just isn't used as the\nsubmission mechanism.\n\n1. http://github.com/gitsmoke\n"},{"id":"147009","messageId":"AANLkTimv7XKoTG1y=5RcUGmCmwpqyj=xVmT78F1OxNsw@mail.gmail.com","threadId":"24608","inReplyTo":"20100802221328.GA3826@burratino","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-08-02T22:32:36Z","receivedAt":"2010-08-02T22:32:36Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Aug 2, 2010 at 22:13, Jonathan Nieder wrote:\n> Ævar Arnfjörð Bjarmason wrote:\n>> On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM wrote:\n>\n>>> And what's on the site tells us almost nothing about the tested systems.\n>>\n>> Can you be more specific? What information do you find lacking at\n>> http://smoke.git.nix.is/app/projects/smoke_reports/1 ?\n>\n> Operating system (i.e., distro).  Precise CPU architecture.  Number of\n> CPUs.  Available memory. Configuration used to build git.\n\nThat'd be nice. We could detect that and include it later in\nextra_properties in t/harness. It'd need some fancy detection code\nthough.\n\n> Which tests were skipped and which had expected failures.\n\nThat's actually already there.\n"},{"id":"147012","messageId":"7v39uwk52s.fsf@alter.siamese.dyndns.org","threadId":"24608","inReplyTo":"AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-08-02T22:44:27Z","receivedAt":"2010-08-02T22:44:27Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ævar Arnfjörð Bjarmason writes:\n\n> On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM wrote:\n>> On 08/02/2010 04:54 PM, Sverre Rabbelier wrote:\n>>> Can't we run this somewhere a little less \"shabby\"?\n\n\"shabby\" is not a good word to describe a service somebody volunteered to\nmaintain for the public good. Be civil, please.\n\n>> And what's on the site tells us almost nothing about the tested systems.\n>\n> Can you be more specific? What information do you find lacking at\n> http://smoke.git.nix.is/app/projects/smoke_reports/1 ?\n\n\"Platform Linux\" does not tell much about the tested systems, no?\n"},{"id":"147014","messageId":"AANLkTi=QxWzYG0Pv2Cc=rmTB1vECWCdh=W=_8vsRsfnC@mail.gmail.com","threadId":"24608","inReplyTo":"7v39uwk52s.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH 2/2] t/README: Document the Smoke testing","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-08-02T22:47:53Z","receivedAt":"2010-08-02T22:47:53Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Mon, Aug 2, 2010 at 17:44, Junio C Hamano wrote:\n> \"shabby\" is not a good word to describe a service somebody volunteered to\n> maintain for the public good.  Be civil, please.\n\nThat's why I quoted it, I didn't mean to put Ævar's work down and I\nthink he understood what I meant, judging from his reply. On that\nnote, thanks Ævar for reading what I meant, not what I said :).\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"147016","messageId":"AANLkTinxvMuU86=OavB4phrCOwUQ1GO2yCP562WuMagC@mail.gmail.com","threadId":"24608","inReplyTo":"1280780684-26344-2-git-send-email-avarab@gmail.com","subject":"Re: [PATCH 1/2] tests: Infrastructure for Git smoke testing","fromName":"Avery Pennarun","fromEmail":"apenwarr@gmail.com","sentAt":"2010-08-02T22:58:14Z","receivedAt":"2010-08-02T22:58:14Z","isPatch":true,"sender":{"key":"apenwarr@gmail.com","avatar":"https://avatars.githubusercontent.com/u/20592?v=4"},"body":"On Mon, Aug 2, 2010 at 4:24 PM, Ævar Arnfjörð Bjarmason\n wrote:\n> The smoker might want to compile git with non-default flags, include\n> bisecting functionality or run the tests under valgrind. Doing that is\n> outside the scope of this patch, this just adds a report submission\n> mechanism. But including a canonical smoke runner is something we'll\n> want to include eventually.\n\nYou might want to play with gitbuilder:\nhttp://github.com/apenwarr/gitbuilder\n\nIt can bisect automatically and it looks like it could integrate\npretty nicely with this system. (If you're running a gitbuilder, just\nhave it submit the smoke test with each build it makes. gitbuilder\nwill automatically bisect if 'make test' fails, so eventually you'll\nsubmit smoke tests that *don't* fail.)\n\nHave fun,\n\nAvery\n"}]}