Autobuilder reporting old build issues
Hello Matt,
Is there something special going on with your autobuilder setup? Indeed, it very often reports build results that are based on Buildroot versions that are a few days old, as if you're not testing the latest Buildroot.
For example, if you look at the attached screenshot, all autobuilder instances reported results based on Buildroot 05827480 (the strace commit I made yesterday evening), except your autobuilder results, which were based on 704db158 (a commit made on July 10, i.e 4-5 days ago).
This is annoying because when we solve an issue, your autobuilder continues to report the problem for several days.
Have you tweaked your autobuild-run script? Are you caching results before reporting them?
Could you see what you can do to address this problem?
Thanks,
Thomas Petazzoni
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Hello,
Quoted 5 lines · Thomas Petazzoni
For example, if you look at the attached screenshot, all autobuilder instances reported results based on Buildroot 05827480 (the strace commit I made yesterday evening), except your autobuilder results, which were based on
704db158(a commit made on July 10, i.e 4-5 days ago).
Forgot the screenshot. Here it is:
http://free-electrons.com/~thomas/autobuilder-results.png
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Hello Matt,
Quoted 10 lines · Thomas Petazzoni
Is there something special going on with your autobuilder setup? Indeed, it very often reports build results that are based on Buildroot versions that are a few days old, as if you're not testing the latest Buildroot.
For example, if you look at the attached screenshot, all autobuilder instances reported results based on Buildroot 05827480 (the strace commit I made yesterday evening), except your autobuilder results, which were based on
704db158(a commit made on July 10, i.e 4-5 days ago).
Since your autobuilder is still reporting build results that date back from commit 704db158, I've disabled your account so that build results from your autobuilder are no longer accepted.
Let me know when the problem is fixed, so that I can re-enable your account.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Thomas,
Quoted 15 lines · Thomas Petazzoni
Hello Matt,
Quoted 10 lines · Thomas Petazzoni
Is there something special going on with your autobuilder setup? Indeed, it very often reports build results that are based on Buildroot versions that are a few days old, as if you're not testing the latest Buildroot.
For example, if you look at the attached screenshot, all autobuilder instances reported results based on Buildroot 05827480 (the strace commit I made yesterday evening), except your autobuilder results, which were based on
704db158(a commit made on July 10, i.e 4-5 days ago).
Quoted 7 lines
Since your autobuilder is still reporting build results that date back from commit
704db158, I've disabled your account so that build results from your autobuilder are no longer accepted.Let me know when the problem is fixed, so that I can re-enable your account.
Apologize for the delay, I was on vacation.
I had pointed the Buildroot git remote at our internal mirror because of network issues fetching (this could lead to a delay of ~12hrs or longer if the mirrors can't fetch). I'll take a look at the autobuilder script and instead of pointing at the mirror, I'll improve error handling of when the remote fails to fetch. Once this is tested out, I'll respond back.
Matt
Hello,
Quoted 6 lines · Matthew Weber
I had pointed the Buildroot git remote at our internal mirror because of network issues fetching (this could lead to a delay of ~12hrs or longer if the mirrors can't fetch). I'll take a look at the autobuilder script and instead of pointing at the mirror, I'll improve error handling of when the remote fails to fetch. Once this is tested out, I'll respond back.
Have you tried using the github.com mirror instead ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Thomas,
Quoted 4 lines · Thomas Petazzoni
Hello,
On Mon, 17 Jul 2017 06:18:54 -0500, Matthew Weber wrote:
Quoted 9 lines
Quoted 6 lines
I had pointed the Buildroot git remote at our internal mirror because of network issues fetching (this could lead to a delay of ~12hrs or longer if the mirrors can't fetch). I'll take a look at the autobuilder script and instead of pointing at the mirror, I'll improve error handling of when the remote fails to fetch. Once this is tested out, I'll respond back.
Have you tried using the github.com mirror instead ?
I could definitely try it. How often does it sync?
Hello,
Quoted 3 lines · Matthew Weber
Quoted 1 line
Have you tried using the github.com mirror instead ?
I could definitely try it. How often does it sync?
Every 10 minutes.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Thomas,
Quoted 10 lines · Thomas Petazzoni
Hello,
Quoted 3 lines · Matthew Weber
Quoted 1 line
Have you tried using the github.com mirror instead ?
I could definitely try it. How often does it sync?
Every 10 minutes.
I've updated to use the github mirror and a test run looks good. When my builder cron starts later this evening (11pm UTC), it will be using this new config.
Thanks for pointing this out, it was on my list to revisit but I needed a push :-) This is obviously good to have fixed and I've got a couple more idle machines that will start contributing next month once I get them setup.
Matt
Hello,
Quoted 13 lines · Matthew Weber
Quoted 10 lines · Thomas Petazzoni
Hello,
Quoted 3 lines · Matthew Weber
Quoted 1 line
Have you tried using the github.com mirror instead ?
I could definitely try it. How often does it sync?
Every 10 minutes.
Quoted 8 lines
I've updated to use the github mirror and a test run looks good. When my builder cron starts later this evening (11pm UTC), it will be using this new config.
Thanks for pointing this out, it was on my list to revisit but I needed a push :-) This is obviously good to have fixed and I've got a couple more idle machines that will start contributing next month once I get them setup.
Thanks! I've re-enabled your account, we'll see how it goes.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com