Making hg 5.0 as beta release with python 3 support.
mharbison72 at gmail.com
Tue Mar 5 09:26:25 EST 2019
> On Mar 5, 2019, at 8:25 AM, Pulkit Goyal <7895pulkit at gmail.com> wrote:
>> On Tue, Mar 5, 2019 at 7:04 AM Matt Harbison <mharbison72 at gmail.com> wrote:
>> On Mon, 04 Mar 2019 11:25:14 -0500, Pulkit Goyal <7895pulkit at gmail.com>
>> > Hey everyone,
>> > I hope everything is going well.
>> > After years of work on porting mercurial to Python 3 by everyone, we are
>> > close, very close. Right now, only 5 tests fail on python 3 and there
>> > are 4
>> > regressions (tests which were passing earlier and started failing
>> > recently). Few days ago, I installed mercurial using Python 3 as default
>> > mercurial on my personal system. Things are working good. Things which I
>> > have noticed not working are:
>> This is great news! As an additional data point, Windows is lagging
>> behind with 41 failures (604 pass).
>> If there's interest, I should be able to set up a py3 buildbot on a much
>> faster Windows 10 system. The total output is ~130K, so I don't want to
>> just post that.
> There is definitely interest in having a py3 buildbot on windows. This will help people who don't have windows to look into failures and try to fix them or atleast reason why they are failing. Also it will help to catch regressions.
> It will be great if before the release, we can improve the status on windows and maybe make it as same for linux.
Ok. Augie set me up with the account info for the other 2 bots.
What I’d like to do here is figure out how to run it as a service, instead of having to manually fire up an MSYS shell, change directories, and then spin up buildbot. I haven’t figured out how to do that. WSL might make it a little easier, but I don’t have that nailed down yet either.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mercurial-devel