git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] t/README: Document the Smoke testing

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 2, 2010, 22:13 UTC
Message-ID
<20100802221328.GA3826@burratino>
In-Reply-To
<AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM <gitzilla@gmail.com> wrote:
>> And what's on the site tells us almost nothing about the tested systems.
>
> Can you be more specific? What information do you find lacking at
> http://smoke.git.nix.is/app/projects/smoke_reports/1 ?

Operating system (i.e., distro). Precise CPU architecture. Number of CPUs. Available memory. Which tests were skipped and which had expected failures. Configuration used to build git.

(I understand that requiring all that information could prevent people from running smoke servers, so I don’t mean to say it all should be required.)

Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 10 of 14 in “Smoke testing for Git”
  1. 0/2 Smoke testing for GitÆvar Arnfjörð Bjarmason, Aug 2, 2010
  2. 1/2 tests: Infrastructure for Git smoke testingÆvar Arnfjörð Bjarmason, Aug 2, 2010
  3. Avery PennarunAug 2, 2010
  4. 2/2 t/README: Document the Smoke testingÆvar Arnfjörð Bjarmason, Aug 2, 2010
  5. Sverre RabbelierAug 2, 2010
  6. A Large Angry SCMAug 2, 2010
  7. Ævar Arnfjörð BjarmasonAug 2, 2010
  8. Sverre RabbelierAug 2, 2010
  9. Ævar Arnfjörð BjarmasonAug 2, 2010
  10. Jonathan NiederAug 2, 2010
  11. Ævar Arnfjörð BjarmasonAug 2, 2010
  12. A Large Angry SCMAug 2, 2010
  13. Junio C HamanoAug 2, 2010
  14. Sverre RabbelierAug 2, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.