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

Re: [PATCH 1/2] tests: Infrastructure for Git smoke testing

From
Avery Pennarun <apenwarr@gmail.com>
Date
Aug 2, 2010, 22:58 UTC
Message-ID
<AANLkTinxvMuU86=OavB4phrCOwUQ1GO2yCP562WuMagC@mail.gmail.com>
In-Reply-To
<1280780684-26344-2-git-send-email-avarab@gmail.com>

On Mon, Aug 2, 2010 at 4:24 PM, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 5 quoted lines
> The smoker might want to compile git with non-default flags, include
> bisecting functionality or run the tests under valgrind. Doing that is
> outside the scope of this patch, this just adds a report submission
> mechanism. But including a canonical smoke runner is something we'll
> want to include eventually.

You might want to play with gitbuilder: http://github.com/apenwarr/gitbuilder

It can bisect automatically and it looks like it could integrate pretty nicely with this system. (If you're running a gitbuilder, just have it submit the smoke test with each build it makes. gitbuilder will automatically bisect if 'make test' fails, so eventually you'll submit smoke tests that *don't* fail.)

Have fun,
Avery
Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 3 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.