[Buildroot] Autobuilder Package Stats Page

[Buildroot] Autobuilder Package Stats Page

[Mark Corbin]

Hello

I've been updating package URLs based on the status information shown on the 
'package stats' page (http://autobuild.buildroot.org/stats/), but the page 
output hasn't changed to reflect these new updates.

I was wondering when/how the page is updated? I have been checking the current 
URL status of packages by running './support/scripts/pkg_stats' directly from 
the command line, but it would be useful if the web page was refreshed 
regularly to capture any changes.

Thanks

Mark Corbin

[Buildroot] Autobuilder Package Stats Page

[Thomas Petazzoni]

On Wed, 04 Dec 2019 13:24:52 +0000
Mark Corbin <mark@dibsco.co.uk> wrote:

> I've been updating package URLs based on the status information shown on the 
> 'package stats' page (http://autobuild.buildroot.org/stats/), but the page 
> output hasn't changed to reflect these new updates.
> 
> I was wondering when/how the page is updated? I have been checking the current 
> URL status of packages by running './support/scripts/pkg_stats' directly from 
> the command line, but it would be useful if the web page was refreshed 
> regularly to capture any changes.

The page is updated once a day, the last date is at the bottom of the
page, together with the commit id.

When a "next" branch exists, the page is based on data from the next
branch, so that we use the latest package versions known by Buildroot.
However, all your URL-related changes have been merged to master, so
they didn't show up in the refreshed statistics page.

But since the release of 2019.11, next has been merged into master, but
next has not been removed. So the logic still thinks next is newer than
master.

Peter, could you drop the next branch ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Autobuilder Package Stats Page

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > On Wed, 04 Dec 2019 13:24:52 +0000
 > Mark Corbin <mark@dibsco.co.uk> wrote:

 >> I've been updating package URLs based on the status information shown on the 
 >> 'package stats' page (http://autobuild.buildroot.org/stats/), but the page 
 >> output hasn't changed to reflect these new updates.
 >> 
 >> I was wondering when/how the page is updated? I have been checking the current 
 >> URL status of packages by running './support/scripts/pkg_stats' directly from 
 >> the command line, but it would be useful if the web page was refreshed 
 >> regularly to capture any changes.

 > The page is updated once a day, the last date is at the bottom of the
 > page, together with the commit id.

 > When a "next" branch exists, the page is based on data from the next
 > branch, so that we use the latest package versions known by Buildroot.
 > However, all your URL-related changes have been merged to master, so
 > they didn't show up in the refreshed statistics page.

 > But since the release of 2019.11, next has been merged into master, but
 > next has not been removed. So the logic still thinks next is newer than
 > master.

 > Peter, could you drop the next branch ?

Sure, done.

-- 
Bye, Peter Korsgaard

[Buildroot] Autobuilder Package Stats Page

[Mark Corbin]

On Wednesday, 4 December 2019 14:53:48 GMT Thomas Petazzoni wrote:
> On Wed, 04 Dec 2019 13:24:52 +0000
> 
> Mark Corbin <mark@dibsco.co.uk> wrote:
> > I've been updating package URLs based on the status information shown on
> > the 'package stats' page (http://autobuild.buildroot.org/stats/), but the
> > page output hasn't changed to reflect these new updates.
> > 
> > I was wondering when/how the page is updated? I have been checking the
> > current URL status of packages by running './support/scripts/pkg_stats'
> > directly from the command line, but it would be useful if the web page
> > was refreshed regularly to capture any changes.
> 
> The page is updated once a day, the last date is at the bottom of the
> page, together with the commit id.
> 
> When a "next" branch exists, the page is based on data from the next
> branch, so that we use the latest package versions known by Buildroot.
> However, all your URL-related changes have been merged to master, so
> they didn't show up in the refreshed statistics page.

Do any changes made to 'master' normally get committed to 'next' too when it 
exists?

[Buildroot] Autobuilder Package Stats Page

[Thomas Petazzoni]

On Wed, 04 Dec 2019 15:12:50 +0000
Mark Corbin <mark@dibsco.co.uk> wrote:

> > When a "next" branch exists, the page is based on data from the next
> > branch, so that we use the latest package versions known by Buildroot.
> > However, all your URL-related changes have been merged to master, so
> > they didn't show up in the refreshed statistics page.  
> 
> Do any changes made to 'master' normally get committed to 'next' too when it 
> exists?

No. We only merge "next" back into "master" just after the release. We
sometimes do cherry-pick some patches from master into next if they fix
some build issues that affect the autobuilders on both the master and
next branch, but for all other changes, we wait until next is merged
back until master.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com