https://bz.mercurial-scm.org/show_bug.cgi?id=6967
Bug ID: 6967
Summary: run-tests.py is affected by ~/.hgrc
Product: Mercurial project
Version: unspecified
Hardware: PC
OS: NetBSD
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: infrastructure
Assignee: bugzi...@mercurial-scm.org
Reporter: mercurial-bugzi...@campbell.mumble.net
CC: kbullock+mercur...@ringworld.org,
mercurial-de...@mercurial-scm.org
I tried running automatic tests in preparation for submitting a patch, and it
failed like so:
% time nice -n +10 env -i PATH=/bin:/usr/bin:/pkg/2024Q4/bin gmake -j4
test-diff-unified
cd tests && python3 run-tests.py test-diff-unified
fatal: fetching library from `hg` failed with 1:
*** failed to import extension "evolve": No module named 'evolve'
*** failed to import extension "topic": No module named 'topic'
/tmp/hgtests.ew_uiyh4/install/lib/python3.11/site-packages/mercurialgmake: ***
[Makefile:159: test-diff-unified] Error 4
nice -n +10 env -i PATH=/bin:/usr/bin:/pkg/2024Q4/bin gmake -j4 104.53s user
7.58s system 98% cpu 1:53.52 total
I renamed ~/.hgrc (which enables the topic and evolve extensions) and the lines
*** failed to import extension "evolve": No module named 'evolve'
*** failed to import extension "topic": No module named 'topic'
went away. It seems to me they shouldn't have been there in the first place,
though -- that the hg tests should be independent of whatever is currently in
~/.hgrc.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
