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

Re: [PATCH] do not set GIT_TEST_MAINT_SCHEDULER where it does not matter

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 29, 2024, 05:38 UTC
Message-ID
<xmqqsf09vbqf.fsf@gitster.g>
In-Reply-To
<CAPig+cStHRX-wZKwdcO33wCjd4UU3MO-rVisyOFZ1vPbGaN51Q@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 7 quoted lines
> Clearly the idea was to protect the scheduler-configuration of the
> person running the test in the event that the test author forgot to
> set GIT_TEST_MAINT_SCHEDULER to one of the legitimate "testing values"
> before invoking a "destructive" command, such as `git maintenance
> start`. By defaulting to `none:exit 1`, the problem would be caught
> and reported before any damage could be done to the configuration of
> the person running the tests.

Yeah, if the variable were exported. So I am OK with a fix in the opposite direction.

Previous: Eric SunshineNext: Eric Sunshine
Message 3 of 5 in “do not set GIT_TEST_MAINT_SCHEDULER where it does not matter”
  1. do not set GIT_TEST_MAINT_SCHEDULER where it does not matterJunio C Hamano, Mar 29, 2024
  2. Eric SunshineMar 29, 2024
  3. Junio C HamanoMar 29, 2024
  4. test-lib: fix non-functioning GIT_TEST_MAINT_SCHEDULER fallbackEric Sunshine, Mar 29, 2024
  5. Eric SunshineMar 31, 2024

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.