Hello Leonardo, You are the next one on the list (https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Members) and SWAT duty will rotate from Jaga and Ross to you at EOD

Hello, Here are the statistics for last week. Minjae Kim was on SWAT duty. 268 failures were reported, * 118 were triaged by Minjae - 25 for issues with the events patch, replied on list by

While looking at the changelog, it is useful to be able to go back to the build collection editing, for example to be able to correct a note. Signed-off-by: Alexandre Belloni

Hi Jaga, <Jagadheesan_Duraisamy@...> wrote: We can tag team it - a single problem caused a *lot* of failure over the weekend that I mostly cleaned up earlier, but there's still

Hello Ross, I can take-up this week, if you are not prepared for the short notice. Regards Jaga

Hi Alexandre, I have missed seeing the email, sorry about that. Regards Jaga

The "good" news is that this didn't affect the autobuilder as it sets SSTATE_DIR to a common directory and doesn't use SSTATE_MIRRORS. I don't think we're to the bottom of this. If its not spending

<alex.kanavin@...> wrote: I forgot to mention that I did run diffoscope locally with the offending vim packages and it took about 30 seconds (same as the AB logs showed)

Hello Ross, Since I didn't get any reply from Jagadheesan and you were the next one on the list (and we discussed that on IRC), you will be on SWAT duty this week. I know this is short notice and

I’ve definitely seen diffoscope process take hours and hours and hours in local builds. Trying it with these vim packages locally should still be done. Alex

Hi All, There are a number of failures on the autobuilder in do_package with odd unknown user issues. My guess is that its related to the new buildtools tarball I configured in the helper. I'm going

<richard.purdie@...> wrote: OK, I read through the code and unfortunately found a bug: when attempting to make sure the "B" build doesn't use sstate, I misspelled the SSTATE_MIRRORS,

<richard.purdie@...> wrote: I'm not sure that diffoscope is the culprit here. If you look at the logs, you can see that there is only about 30 seconds between the "Running diffoscope"

I did a bit of work on the go reproducibility, that has been preserved here: http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/go-repro I got there, but it took quite a bit of time

I'm going to try and get diffs of the remaining big package differences and see where we stand. The two big ones I know of are go as a language for reproducibility and perf. Perf will just be a shear

Cheers :) If there's something else I could help, tell. One item is getting to the bottom of why it takes diffoscope beyond the heat death of the universe to render its verdict on some items. Alex

Regular users of the autobuilder will note that I've split the reproducible builds test out of the main oe-selftest build and into its own target build. This is because that test tends to run for a

Hello Jagadheesan, You are the next one on the list (https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Members) and SWAT duty will rotate from Minjae to you at EOD 2012-02-12. Please

Hello, Here are the statistics for last week. Jon Mason was on SWAT duty. 413 failures were reported, * 145 were triaged by Jon - 6 were not to be triaged - 7 were due to out of disk space

Hi, The autobuilder controller (typhoon) ran out of disk space and I ended up having to restart buildbot after clearing some space with a temporary fix until Michael can look at it. That meant the