#qi-hardware IRC log for Friday, 2012-03-09

qi-botThe build was FAILED: http://fidelio.qi-hardware.com/~xiangfu/building/Nanonote/Ben/openwrt-xburst.full_system-20120309-0026 01:03
whitequarkDocScrutinizer: about the GSM modules02:16
whitequarksuddenly, some holidays happened, so I'd probably won't send them this week02:16
whitequark(pesky holidays. they always get in the way between me and electronics. New Year, then Chinese New Year, then something, then this. :/)02:18
rz2kno holidays for nerds! :302:18
whitequarkmy schedule isn't significantly affected by holidays nor weekends02:19
whitequarkthe fact that others' schedules are sucks.02:19
wolfspraulwhitequark: found this site recently about notebook schematics http://laptop-schematics.com02:50
whitequarkwolfspraul: interesting. a russian site03:03
whitequarkwell, it mostly does not work03:14
wolfspraulwhat does not work?03:25
whitequarkI've tried to get schematics for several Samsung notebooks03:30
whitequarknone of the ones I've selected worked, both random and those who I have03:30
qi-botThe build was FAILED: http://fidelio.qi-hardware.com/~xiangfu/building/Nanonote/Ben/openwrt-xburst.full_system-20120309-0213 03:45
whitequarkIT HAS FAILED!!111one03:49
rz2kgrammar nazis in da channel03:53
whitequarker, I didn't even notice the "was"03:57
whitequarkjust was joking stupidly on the capitalization03:57
Action: rz2k compromised himself03:57
xiangfuwhitequark, it continue compile now. :-) some package fail to build :(04:37
wolfspraulno worries all fine :-)04:38
wolfspraulserver access is available for anyone who wants to help04:38
whitequarkwell, tuxbrain still did not manage to deliver anything04:49
wpwrakwhitequark: that FAILED repeated over and over has a touch of this one, doesn't it ? http://www.smbc-comics.com/index.php?db=comics&id=8305:01
wolfspraulwhitequark: [tuxbrain] we are scramling everywhere. I have writing to you in my todo list, but it keeps slipping from the top, urgh05:08
wolfsprauljust one more thing before...05:08
kyaki swear it used to be "has FAILED" :)06:39
DocScrutinizeranybody heard of solar storm that hits us just this moment?06:45
xiangfukyak, so the correct is 'has FAILED' not 'was FAILED' ?06:46
kyakxiangfu: as far as my English grammar skills go, yes :)06:46
kyakDocScrutinizer: oh! and i thought i had a headache because of yesterday's party..06:49
DocScrutinizerhehe, same here, though actually I don't recall any party yesterday06:49
DocScrutinizerI just heard the storm is almost over and had no negative impact yet on COMSATs or power grids - but it will continue another few hours and may still get worse during that time06:51
qi-bot[commit] Xiangfu: compile-openwrt-xburst.sh: fix English grammar error (master) http://qi-hw.com/p/openwrt-packages/8eefa4b06:51
DocScrutinizerthe scary part in that sidenote in TV news was that this allegedly been known since 3 days, and I completely missed it06:52
kyakyeah, i actually heard it several times on TV, even though i watch TV only during breakfast :) it was like top news here06:53
DocScrutinizerand such an even at least potentially could cause EU wide blackouts06:53
DocScrutinizerwhich - for unclear reasons - makes me remember the fact that the sun twice a year(?) passes by exactly behind any arbitrary TV geostationary sat, which usually should cause massive interference in all dishes pointing at that sat and potentially even can fry LNBs06:56
DocScrutinizerfunny coincidence: 1 year Fucku anniversary, nice date for an EU wide blackout07:00
DocScrutinizerwhich would also be a nice hard test for all nuclear power plants' powerless shutdown resilience07:01
wpwrakkyak: "was failed" would be the passive form. like in "several human rights activists were disappeared by the military regime"07:03
wpwrakkyak: so that would suggest some sort of sabotage that breaks our builds. now, combine this with the solar storm and you have a nice conspiracy story ;-)07:04
DocScrutinizeranyway could somebody kick that job outa the buildqueue please?07:04
DocScrutinizerseems it's triggered to rebuild and fail each time *anything* builds on the buildhost07:05
DocScrutinizeror is it that actually somebody adds this job over and over again, and never gets it right?07:07
kyakwpwrak: haha :)07:07
wpwrakDocScrutinizer: i think it's just some endless loop. maybe with some rate limit.07:08
kyakyeah, just an endless loop to build the whole image from scratch.. usually takes mor ethan one day07:09
kyakbut if it fails early, it can become annoying :)07:09
DocScrutinizerdoes it make sense to compile that stuff again and again on an automated schedule, until eventually random bittoggles on HDD fix the errors?07:12
kyakit's supposed that someone will have a look and fix it ocasionally :)07:14
wolfspraulI fail to see the problem with that 1-line. just ignore the bot if you don't like it, but there are definitely people interested in regularly maintained and updated nanonote and milkymist software.07:15
wolfspraulmaybe we can remove some redundancy?07:15
DocScrutinizergive me the URL and ssh credentials, I know the 2-letter cmd to fix it ;-)07:15
wolfspraulyou don't use a nanonote and don't care about software updates for it07:15
wolfspraulthat could explain your impatience with those log lines :-)07:16
kyakyeah, i'm also with the 1 line.. you can add the "Has FAILED" pattern to your IRC client, if you wish07:16
kyaks/also/also fine07:16
DocScrutinizerI'm just concerned about the abstract waste of time and resources to build the obviously unchanged package over and over again07:16
wolfspraulthat i agree with, if there is redundancy/noise, we should improve that07:17
DocScrutinizerthat doesn't feel right07:17
kyakthis is perhaps a good idea. the build bot should check if the repo has changed and it makes sense to rebuild07:17
wolfspraulbut I think xiangfu is actively working on a new ben image right now, with testing, rebuilds, etc.07:17
wolfspraulkyak: yes but I think that may already be the case07:17
wolfspraulbut if not - yes, fully agree07:18
xiangfukyak, (check repo) not in nanonote image build.07:18
kyakxiangfu: do you think it can be easily done, while you are on it? (check if the repo has changed since last FAILED build)07:18
xiangfukyak, since the upstream package change every day.07:19
DocScrutinizerisn't it as simple as "rm /build-this" ?07:19
xiangfukyak, that is easy. I already done that in milkymist stuff build (milkymist have 10 repos to check :)07:19
DocScrutinizerand ">build-this" when you edit something07:19
xiangfuDocScrutinizer, you mean disable/enable the build?07:20
xiangfuI am done that by a 'compile.sh'07:20
xiangfuDocScrutinizer, : http://fidelio.qi-hardware.com/~xiangfu/bin/compile.sh07:21
xiangfuDocScrutinizer, comment lines means disable :)07:21
xiangfuonce I found a good openwrt package svn revision. I will stick to that revision for release. then debug the error for our side. 07:22
DocScrutinizerwell, that isn't disabling the build once the compiler barfed up on it07:22
DocScrutinizerthe "rm /build-this" was meant to be done by the buoldhost automatically07:22
DocScrutinizerand you even could do the "touch /build-this" by inotifywatch or inotifywait (dunno which of both is the more suited one)07:24
xiangfukyak, http://fidelio.qi-hardware.com/~xiangfu/bin/compile-openwrt-milkymist.sh this file have the code that check if there new commit. we can just use that one for openwrt-xburst.07:24
DocScrutinizeror you actually use "find /$buildpackage -cnewer /$buildpackage/last-built"07:25
xiangfu( that isn't disabling the build once the compiler barfed up on it) yes. don't have that feature 07:28
DocScrutinizerif find /$buildpackage -cnewer /$buildpackage/last-built; then build-it; else echo "nothing changed in $buildpackage since last build, skipping"; fi;07:28
xiangfuand it's hard to kill all process if the build already start. every time I have to manually to that by using htop07:28
DocScrutinizerif find /$buildpackage -cnewer /$buildpackage/last-built >/$buildpkg/changed-files; then echo "either those files changed: $(cat /$buildpkg/changed-files) or pkg never been built or compiler missed to create /$buildpkg/last-built tagfile. Building now"; build-it; else echo "nothing changed in $buildpackage since last build, skipping"; fi;07:32
xiangfuevery build we want start from scratch. 07:33
DocScrutinizersure, it does07:33
DocScrutinizerdepending on what you do in build-it07:33
DocScrutinizerit just doesn't start at all if there's already been a build that created the tagfile by "touch ./last-built" abd no file in the package changed since then07:34
DocScrutinizerobviously you want to touch ./last-built *after* the compiler created any new logfiles, *.o and whatnot else07:35
xiangfuwhat is the different on compare svn revision of openwrt packages repo?07:36
DocScrutinizerI.E. add "touch last-built" as very last line of your build-it job 07:36
xiangfuif there is new commit rebuild from scratch.  that is simple for me :-)07:37
DocScrutinizerquite obviously there's been no new commit for that openwrt pkg for the last few days07:38
DocScrutinizeryet it's rebuilt every day it seems07:38
DocScrutinizerthe above sketched two shellscript lines would deal with that in a very convenient manner07:39
DocScrutinizerwait, you can make that one line, in one place:07:40
DocScrutinizerif find /$buildpackage -cnewer /$buildpackage/last-built >/$buildpkg/changed-files; then echo "either those files changed: $(cat /$buildpkg/changed-files) or pkg never been built or compiler missed to create /$buildpkg/last-built tagfile. Building now"; build-it; touch /$buildpkg/last-built; else echo "nothing changed in $buildpackage since last build, skipping"; fi;07:41
DocScrutinizerwhatever build-it is for you, I guess it's the command that shall execute one line out of http://fidelio.qi-hardware.com/~xiangfu/bin/compile-openwrt-milkymist.sh07:42
DocScrutinizerooh, not really07:42
DocScrutinizererr, what, did that file change?07:43
DocScrutinizeraah no, I meant http://fidelio.qi-hardware.com/~xiangfu/bin/compile.sh07:43
xiangfuconfuse :-). $buildpackage you mean openwrt package svn repo? 07:47
DocScrutinizeraah, I see I missed your comment about the http://fidelio.qi-hardware.com/~xiangfu/bin/compile-openwrt-milkymist.sh. Yeah it checks if new version exists in git07:47
xiangfuDocScrutinizer, yes. that one have new commit check. but compile-openwrt-xburst.sh don't have and I don't have plan add it :-)07:48
xiangfuthe step I work on nanonote is : 1. make sure the kernel compilef ine. 2. leave all other build to buildhost. 07:48
DocScrutinizerwell, I didn't even think of git, I just thought of some structure where a master script parses across a couple of $builpkg directories in something like /var/sources/all-packages/*07:49
DocScrutinizer#!/bin/sh\n #this is the master script that gets invoked once a day e.g. by cron\n  \n  cd /var/sources/all-packages; for buildpkg in *; do if find /$buildpackage -cnewer /$buildpackage/last-built >/$buildpkg/changed-files; then echo "either those files changed: $(cat /$buildpkg/changed-files) or pkg never been built or compiler missed to create /$buildpkg/last-built tagfile. Building now"; build-it; touch /$buildpkg/last-built; else 07:53
DocScrutinizerecho "nothing changed in $buildpackage since last build, skipping"; fi; done07:53
DocScrutinizer#!/bin/sh\n #this is the master script that gets invoked once a day e.g. by cron\n  \n  cd /var/sources/all-packages; mkdir ../build-date; for buildpkg in *; do if find ./$buildpkg -cnewer ../build-date/$buildpackage >/tmp/${buildpkg}-changed-files; then echo "either those files changed: $(cat /tmp/${buildpkg}-changed-files) or pkg never been built or compile-job missed to create $(pwd)/../build-date/$buildpackage tagfile. Building 08:07
DocScrutinizernow"; build-it $buildpkg; touch ../build-date/$buildpkg ; else echo "nothing changed in $buildpkg since last build, skipping"; fi; done08:07
DocScrutinizerof course you have to check what find does when file referenced in -cnewer <file> doesn't exist08:10
DocScrutinizero/, daywork (WinXP :-S )08:11
xiangfu if the $buildpackage mean openwrt package svn repo. that repo delete and checkout from scratch in every build.08:11
xiangfuWinXP. there is Win 8 now. :-)08:11
DocScrutinizerwell, that tells sth about confidence of big companies in that new crap from Redmond08:12
xiangfuDocScrutinizer, the openwrt make distclean , delete everything. include all package source(Makefiles)08:12
DocScrutinizeryeah, but only if HEAD != $whatever, AIUI your script. You could touch ../build-date/$packagename in that case08:13
DocScrutinizeranyway, my suggestion wasn't meant for git based infra. So nevermind08:14
xiangfuI have saved your script to my memo folder just in case :-)08:15
DocScrutinizerHEAD_OLD=`cat ${IMAGES_DIR}/../openwrt-HEAD`08:15
DocScrutinizerif [ "${HEAD_NEW}" == "${HEAD_OLD}" ]; then08:15
DocScrutinizerecho "No new commit, ignore build"08:15
DocScrutinizershould be done like that for all pkg 08:16
lindi-be careful with "==". does that work with dash?08:17
DocScrutinizero/, now for real, already late08:17
qi-bot[commit] Xiangfu: flite: update to 1.5.5 (master) http://qi-hw.com/p/openwrt-packages/1a751fb08:36
qi-bot[commit] Xiangfu: bard: udpate to 0.7 (master) http://qi-hw.com/p/openwrt-packages/20b0b7708:36
xiangfuwpwrak, you code on WPAN work out of box in linux v3.2.1. 13:44
xiangfuwpwrak, no luck on ks7010. everytime update kernel. have to modify ks7010 driver. 13:44
viricwhat is ks7010?13:46
wolfspraulviric: history :-)13:49
kristian1aulthat one started tuesday?13:49
wpwrak(wpan working out of the box)  yippee! :)13:51
kristianpaulwpwrak: testing last image build? :-)13:56
wpwrakkristianpaul: just commenting on what xiangfu wrote14:09
wolfspraulwe should officially drop ks7010 support and focus on ben-wpan, we just don't have the resources for ks7010 and it's a dead-end14:09
wolfspraulunless an avid ks7010 user speaks up...14:10
wolfspraullet me know, I'll read the backlog to face the ks7010 uprising :-)14:10
xiangfumy plan is will try 1 or 2 hours to fix the ks7010. if no luck. will stop working on that. keep test image. :-)14:12
viricxiangfu: 17:20
viricI can't build xbursttools...17:20
viricCan you check http://hydra.nixos.org/build/2261269 ?17:20
viriclibusb should be there17:21
viric1.0.0!? ok!17:21
viricwhat an outdated libusb we have..17:21
viricthank you for your help! ;)17:23
kristianpaulfrom Takuji Ebinuma http://www.dynamics.co.nz/media/DOCUMENTS/SOFTWARE_RELATED/Namuru-GPL-port-06.pdf18:33
qi-bot[commit] Werner Almesberger: m1r4/dsv/: updated for Adam's "official" BOM (master) http://qi-hw.com/p/wernermisc/b2954b619:49
qi-bot[commit] Werner Almesberger: m1r4/dsv/milkymist_one_bom_r4.csv: removed duplicate C19 and C21 (master) http://qi-hw.com/p/wernermisc/75509e519:49
qi-bot[commit] Werner Almesberger: Merge branch 'master' of projects.qi-hardware.com:wernermisc (master) http://qi-hw.com/p/wernermisc/81078fc19:49
whitequarkviric: 1.0.0 is like 4 years old already20:58
whitequarkbut there's really nothing to add20:59
--- Sat Mar 10 201200:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!