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

Failing tests with WITH_BREAKING_CHANGES

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jul 28, 2026, 00:46 UTC
Message-ID
<amf76F4wxlboLz_A@fruit.crustytoothpaste.net>
I have the following in `config.mak`:

---- DEVELOPER=1 CC=clang GENERATE_COMPILATION_DATABASE=yes WITH_RUST=1 USE_ASCIIDOCTOR=1 WITH_BREAKING_CHANGES=1 ----

In this configuration, I've noticed some tests failing:
----
t0014-alias.sh                                   (Wstat: 256 (exited 1) Tests: 23 Failed: 2)
  Failed tests:  4, 8
  Non-zero exit status: 1
t1517-outside-repo.sh                            (Wstat: 256 (exited 1) Tests: 404 Failed: 2)
  Failed tests:  248-249
  Non-zero exit status: 1
----

These don't occur if I remove `WITH_BREAKING_CHANGES=1`, so they appear to be related to that option. However, I know we have a CI job for that case, so it's unclear to me why these tests are failing; perhaps the CI job is not testing what we think it's testing.

I noticed this because I plan to send out a series soon based on that option and obviously I want to run the testsuite first.

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Next: Junio C Hamano
Message 1 of 16 in “Failing tests with WITH_BREAKING_CHANGES”
  1. brian m. carlsonJul 28, 2026
  2. Junio C HamanoJul 28, 2026
  3. Phillip WoodJul 28, 2026
  4. Jeff KingJul 28, 2026
  5. 0/2 fix serial tests without/with breaking-changesJeff King, Jul 28, 2026
  6. 1/2 t0014: factor out choice of deprecated commandsJeff King, Jul 28, 2026
  7. Junio C HamanoJul 28, 2026
  8. 2/2 t0014: generate deprecated command names dynamicallyJeff King, Jul 28, 2026
  9. Junio C HamanoJul 28, 2026
  10. Jeff KingJul 28, 2026
  11. brian m. carlsonJul 28, 2026
  12. Phillip WoodJul 29, 2026
  13. Makefile: read configuration earlierbrian m. carlson, Jul 29, 2026
  14. Junio C HamanoJul 30, 2026
  15. Jeff KingJul 30, 2026
  16. Jeff KingJul 30, 2026

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.