Re: [PATCH v3 0/3] Use default values from settings instead of config

2 messages, 2 authors, 2021-10-11 · open the first message on its own page

Re: [PATCH v3 0/3] Use default values from settings instead of config

From: Junio C Hamano <hidden>
Date: 2021-10-11 20:08:33

Glen Choo [off-list ref] writes:
Junio C Hamano [off-list ref] writes:
quoted
With this merged to 'seen', the CI job with the extra set of
GIT_TEST_X settings fail.  When this topic is excluded, with
all the other topics in flight in 'seen', everything seems to
be OK.
Thanks for the feedback, I did two CI runs on my fork in response:

* [1] uses the same tree as seen. Looks like osx-clang passes but
  linux-gcc fails.
* [2] is rebased onto master. Again, osx-clang passes but linux-gcc
  fails.

This should be enough for me to hunt down the issue, though I would
appreciate any hints if anyone has any :)
Using the set of GIT_TEST_FOO... settings I cited in the
Reference#1, in the message you are responding to, will let you
reproduce the issue locally on glinux boxes.

Re: [PATCH v3 0/3] Use default values from settings instead of config

From: Glen Choo <hidden>
Date: 2021-10-11 20:48:39

Junio C Hamano [off-list ref] writes:
Using the set of GIT_TEST_FOO... settings I cited in the
Reference#1, in the message you are responding to, will let you
reproduce the issue locally on glinux boxes.
Ah, I didn't notice that ci/run-build-and-tests.sh uses different
settings for different environments. With those settings, I can
reproduce the failure on my OS X machine.

Thanks so much!
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help