Can you please make a PR? Thanks Pierre
Le mar. 21 mai 2019 à 16:21, Rajdeep Bharati <rajdeepbharat...@gmail.com> 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.controller.js'); > require('./changes/changes.route.js'); > It's working after adding them > > Rajdeep > > On Tue, May 21, 2019 at 7:33 PM Pierre Tardy <tar...@gmail.com> wrote: >> >> 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 >> <rajdeepbharat...@gmail.com> 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 navigation menu, `Last Changes` isn't displayed. I have used the >> > same buildmaster that I was using before >> > (also tried polling different repositories). >> > >> > Could you tell me whether everything is okay on my side? >> > >> > Thanks >> > Rajdeep >> > >> > On Sat, May 18, 2019 at 1:32 PM Rajdeep Bharati >> > <rajdeepbharat...@gmail.com> wrote: >> >> >> >> Thank you. Now it's working >> >> >> >> Rajdeep >> >> >> >> On Sat, May 18, 2019 at 12:29 PM Pierre Tardy <tar...@gmail.com> wrote: >> >>> >> >>> Hi, >> >>> >> >>> The buildbot_badges plugin is using cairo. You can try to uninstall >> >>> that to move forward >> >>> Pierre >> >>> >> >>> Le sam. 18 mai 2019 à 07:58, Rajdeep Bharati >> >>> <rajdeepbharat...@gmail.com> a écrit : >> >>> > >> >>> > Hi, >> >>> > I was trying out the webpack PR. Here's what I did: >> >>> > >> >>> > clone the branch git clone --single-branch --branch www-webpack >> >>> > https://github.com/p12tic/buildbot.git buildbotwebpack >> >>> > cd, make virtualenv, activate >> >>> > make frontend >> >>> > Then outside the directory, I did: >> >>> > >> >>> > buildbot create-master wpmaster >> >>> > >> >>> > Now I got the following error: >> >>> > >> >>> > raise OSError("dlopen() failed to load a library: %s" % ' / >> >>> > '.join(names)) >> >>> > >> >>> > OSError: dlopen() failed to load a library: cairo / cairo-2 / >> >>> > cairo-gobject-2 / cairo.so.2 >> >>> > >> >>> > This is the full stack trace: https://pastebin.com/eDk9GVRK >> >>> > There are some answers on SO, but they are using homebrew python (I'm >> >>> > using macports py). I guess that's why they didn't work? >> >>> > Could you please help? >> >>> > >> >>> > Thank you. >> >>> > Rajdeep >> >>> > >> >>> > On Wed, May 15, 2019 at 5:20 PM Rajdeep Bharati >> >>> > <rajdeepbharat...@gmail.com> wrote: >> >>> >> >> >>> >> Ok cool! >> >>> >> >> >>> >> Thanks >> >>> >> Rajdeep >> >>> >> >> >>> >> On Wed, May 15, 2019 at 1:29 PM Pierre Tardy <tar...@gmail.com> wrote: >> >>> >>> >> >>> >>> Hi Rajdeep, >> >>> >>> >> >>> >>> Buildbot calculates the version number based on tags. You you have to >> >>> >>> fetch all the tags so that the version is correctly calculated. >> >>> >>> >> >>> >>> git fetch --tags --all >> >>> >>> >> >>> >>> then you can re-do the make virtualenv >> >>> >>> >> >>> >>> Regards >> >>> >>> Pierre >> >>> >>> >> >>> >>> Le mar. 14 mai 2019 à 11:39, Rajdeep Bharati >> >>> >>> <rajdeepbharat...@gmail.com> a écrit : >> >>> >>> > >> >>> >>> > Thanks for the feedback! >> >>> >>> > >> >>> >>> > I had a doubt in buildbot: >> >>> >>> > When I install buildbot from source (github), then why is it >> >>> >>> > showing version 2.1.1dev... installed? Shouldn't it show the >> >>> >>> > latest version (2.3.0)? It is up to date with the master branch. >> >>> >>> > >> >>> >>> > Thank you. >> >>> >>> > Rajdeep >> >>> >>> > >> >>> >>> > On Fri, May 10, 2019 at 3:17 AM Mojca Miklavec >> >>> >>> > <mo...@macports.org> wrote: >> >>> >>> >> >> >>> >>> >> On Wed, 8 May 2019 at 21:00, Rajdeep Bharati wrote: >> >>> >>> >> > >> >>> >>> >> > Hi, >> >>> >>> >> > >> >>> >>> >> > I created some issues and found some which would be relevant >> >>> >>> >> > for the project (as discussed in the IRC meeting): >> >>> >>> >> > >> >>> >>> >> > https://github.com/buildbot/buildbot/issues/4760 >> >>> >>> >> > https://github.com/buildbot/buildbot/issues/4761 >> >>> >>> >> > https://github.com/buildbot/buildbot/issues/4709 >> >>> >>> >> > https://github.com/buildbot/buildbot/issues/3471 >> >>> >>> >> > https://github.com/buildbot/buildbot/issues/3470 >> >>> >>> >> > https://github.com/buildbot/buildbot/issues/4750 >> >>> >>> >> >> >>> >>> >> Thank you. >> >>> >>> >> (Nice to see that I'm not the first one requesting these :) >> >>> >>> >> >> >>> >>> >> I assume that we'll also want to add other items for the rest of >> >>> >>> >> the >> >>> >>> >> summer to that list? >> >>> >>> >> >> >>> >>> >> > @Mojca Miklavec Yesterday you mentioned: >> >>> >>> >> >> >> >>> >>> >> >> 16:33:15 <mojca> regarding the features of the default >> >>> >>> >> >> waterfall view, another problem I saw was that unless one of >> >>> >>> >> >> the builds was done recently, the builder doesn't even show in >> >>> >>> >> >> waterfall; for example, there is no texlive or pplib displayed >> >>> >>> >> >> on https://build.contextgarden.net/#/waterfall >> >>> >>> >> >> >>> >>> >> And later Pierre said this was a feature :) >> >>> >>> >> >> >>> >>> >> > However, I am unable to find this problem in >> >>> >>> >> > https://nine.buildbot.net/#/waterfall (it's showing the >> >>> >>> >> > builders not having recent builds). I'm not sure (it might have >> >>> >>> >> > been configured in that manner in nine.buildbot, and not >> >>> >>> >> > present by default). >> >>> >>> >> > >> >>> >>> >> > I will try to replicate this issue in my local setup. >> >>> >>> >> >> >>> >>> >> If you look at >> >>> >>> >> https://build.contextgarden.net/#/console >> >>> >>> >> you can see that there is a huge number of "fake commits" from one >> >>> >>> >> project (from periodic scheduler) after the last build of another >> >>> >>> >> project was done. Maybe there's a setting which tells you how many >> >>> >>> >> latest builds / commits to fetch when drawing the waterfall view. >> >>> >>> >> I >> >>> >>> >> didn't try to investigate what limits the number of displayed >> >>> >>> >> builders. >> >>> >>> >> >> >>> >>> >> Now: for me by far more important missing feature is in fact >> >>> >>> >> support >> >>> >>> >> for filtering on both console and waterfall. Once filtering and >> >>> >>> >> removal of old builders gets implemented, this particular issue >> >>> >>> >> will >> >>> >>> >> be less important. >> >>> >>> >> >> >>> >>> >> Mojca
