* Failing tests with WITH_BREAKING_CHANGES
@ 2026-07-28 0:46 brian m. carlson
2026-07-28 1:00 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: brian m. carlson @ 2026-07-28 0:46 UTC (permalink / raw)
To: git
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Failing tests with WITH_BREAKING_CHANGES
2026-07-28 0:46 Failing tests with WITH_BREAKING_CHANGES brian m. carlson
@ 2026-07-28 1:00 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2026-07-28 1:00 UTC (permalink / raw)
To: brian m. carlson; +Cc: git
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 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.
Does not immediately ring a bell for me. All four integration
branches are OK in my builds.
> 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-07-28 1:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-28 0:46 Failing tests with WITH_BREAKING_CHANGES brian m. carlson
2026-07-28 1:00 ` Junio C Hamano
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.