Ouch, and we have https://buildbot.buildbot.net/ which is down
(probably because of that )
looking at it..
Pierre
Le mar. 21 mai 2019 à 15:57, Rajdeep Bharati
a écrit :
>
> Hi
>
> I am having one issue with the buildbot (I think it's happening after the new
> webpack PR, but not sure).
> In the
Can you please make a PR?
Thanks
Pierre
Le mar. 21 mai 2019 à 16:21, Rajdeep Bharati
a écrit :
>
> There's a bug in
> https://github.com/buildbot/buildbot/blob/master/www/base/src/app/app.module.js
> Changes haven't been `require`d.
> These lines need to be added:
> require('./changes/changes.c
I re-up buildbot.buildbot.net
But the console view is broken.
https://github.com/buildbot/buildbot/issues/4777
Can you also have a look at this?
I can also see that buildbot_travis do not build anymore
https://github.com/buildbot/buildbot/issues/4778
probably I did merge the webpack PR a bit to
Hi,
I have made many improvements to existing code.[1]
As for the latest details, in test file [2], where I have created 4 threads
and inputted 18,228 strings as arguments, it took
0.44 seconds for both insert and search 18228 threads at the same time and
3.5 MB memory (which is 4 times less as p
uh oh.
Somebody better take quick peek that this last commit, please.
Best,
Ken
Hi,
Its a merge commit, i.e. the committer at some point pulled in changes to a
branch which they subsequently pushed to master without rebasing.
Its ‘OK’ in that its not a real commit. The changes you see in GitHub won’t
really happen (if you look in detail they are commits already in master
Thanks for checking. My git-fu was not sufficient to make sure we didn't wind
up somewhere we didn't belong with this.
Ken
On 2019-05-21, at 4:06 PM, Christopher Jones wrote:
>
> Hi,
>
> Its a merge commit, i.e. the committer at some point pulled in changes to a
> branch which they subseque
