**** BEGIN LOGGING AT Tue Feb 09 02:59:59 2016 Feb 09 03:21:08 build #192 of brcm2708 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/192 Feb 09 03:24:35 build #214 of cobalt is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/214 Feb 09 03:30:03 build #214 of cns21xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/214 Feb 09 03:35:39 build #214 of orion is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/214 Feb 09 03:40:58 build #218 of lantiq is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/218 Feb 09 03:43:06 build #218 of ipq806x is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ipq806x/builds/218 Feb 09 03:49:12 build #217 of ramips.rt3883 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/217 Feb 09 03:54:10 build #211 of pxa is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/211 Feb 09 03:59:16 build #212 of realview is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/realview/builds/212 Feb 09 04:04:25 build #210 of imx6 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/210 Feb 09 04:04:44 build #210 of x86.64 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/x86.64/builds/210 Feb 09 04:04:46 build #213 of oxnas is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/oxnas/builds/213 Feb 09 04:09:50 build #203 of ppc40x is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/203 Feb 09 04:10:02 build #205 of malta is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/malta/builds/205 Feb 09 04:11:02 build #218 of ramips is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/218 Feb 09 04:14:38 build #199 of rb532 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/199 Feb 09 04:14:53 build #195 of x86.xen_domu is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/x86.xen_domu/builds/195 Feb 09 04:15:54 build #193 of brcm2708 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/193 Feb 09 04:19:25 build #191 of netlogic is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/netlogic/builds/191 Feb 09 04:20:01 build #173 of kirkwood is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/173 Feb 09 04:20:50 build #169 of ar71xx is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/169 Feb 09 04:21:33 build #169 of lantiq.xrx200 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq.xrx200/builds/169 Feb 09 04:24:53 build #165 of brcm47xx.mips74k is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.mips74k/builds/165 Feb 09 04:25:54 build #163 of au1000 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/163 Feb 09 04:26:19 build #168 of ramips.mt7620 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7620/builds/168 Feb 09 04:27:01 build #156 of mpc85xx is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/156 Feb 09 04:31:03 build #151 of adm5120 is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/151 Feb 09 04:31:05 build #153 of mcs814x is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/153 Feb 09 04:31:38 build #151 of mpc52xx is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/151 Feb 09 04:34:29 build #150 of gemini is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/150 Feb 09 04:35:53 build #149 of octeon is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/149 Feb 09 04:36:04 build #153 of sunxi is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/153 Feb 09 04:36:27 build #151 of omap is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/151 Feb 09 06:39:30 nbd, ping Feb 09 06:39:36 morning :) Feb 09 07:00:35 morning nitroshift Feb 09 07:02:05 plntyk, moin :) Feb 09 07:02:34 plntyk, do you know anything about dsl modules? a friend has a dsl device and wanted openwrt on it but dsl isn't working Feb 09 07:03:10 it's this device: https://wiki.openwrt.org/toh/huawei/hg655d Feb 09 07:05:03 dsl on broadcom is not supported (missing drivers) - only the lantiq target has working dsl - see mailing list or tplink W9xxx devices for examples Feb 09 07:05:42 plntyk, thanks Feb 09 07:06:49 i'll get him to use that dsl device for the dsl connection alone then hook a different router behind it running openwrt Feb 09 07:46:42 nitroshift: pong Feb 09 07:49:05 nbd, yesterday's commits *did* improve performance on mt76 :) Feb 09 07:54:09 great Feb 09 07:54:40 so how well is it working for you right now? Feb 09 07:54:46 what kind of throughput are you getting? Feb 09 07:55:05 wired or wireless? Feb 09 07:55:20 wireless Feb 09 07:55:37 i'm seeing ~30Mbps transfer speed Feb 09 07:56:02 and that's constant Feb 09 07:57:40 that's the most a .11n device can achieve anyway Feb 09 07:58:02 M*Byte*ps or M*Bit*ps ? Feb 09 08:01:04 Bit Feb 09 08:02:34 that's why i said Mbps and not MBps Feb 09 08:04:55 30 Mbps is not nearly the most that a .11n device can achieve Feb 09 08:05:12 what kind of client was that? Feb 09 08:06:32 a lenovo yoga tablet Feb 09 08:07:10 nbd, mind you, before yesterday's fixes i was getting 2Mbps Feb 09 08:07:33 flaky and spiky Feb 09 08:09:45 yeah, there are 802.11n devices that can do 600 marketing megabit/s, ie 250-300 megabit/s of real throughput. Feb 09 08:10:31 ok, i guess for a tablet 30 Mbps is fine Feb 09 08:10:35 nitroshift: I tend to write out megabit/s in full, just because a lot of people confuse the two, and some will say MB when they mean megabit, others will say Mb when they mean megabyte, etc. Feb 09 08:12:54 SwedeMike, i know what you mean Feb 09 08:14:29 nbd, same tablet gets over 60Mbps when connected to a wrt1900ac Feb 09 08:20:43 build #164 of ramips.rt305x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt305x/builds/164 Feb 09 08:34:28 what kind of test? Feb 09 08:38:13 nbd, iperf3 Feb 09 08:38:21 and speedtest.net Feb 09 08:38:59 do they show similar results? Feb 09 08:40:03 yes Feb 09 08:56:09 nbd, are you an op on openwrt channel? can you change the topic to announce that servers are in maintenance mode at the moment? Feb 09 10:26:41 build #160 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/160 Feb 09 11:09:46 what notation does json_script use? Is it something standard? Feb 09 11:19:39 txomon: no Feb 09 11:19:56 txomon: it is like a json encoded ast notation Feb 09 11:20:22 e.g. ["if", [... true block ...], [... false block ...]] Feb 09 11:20:24 jow_laptop: hmmm so no chance of finding this in the wild... :( Feb 09 11:20:35 I was looking for a python implementation Feb 09 11:20:47 there is none Feb 09 11:20:48 because this would be useful for a hackaton I am planning to go Feb 09 11:21:02 ok Feb 09 11:21:02 but should be extremely simple to do yourself Feb 09 11:21:42 ok, will try to create a python binding Feb 09 11:21:50 that way I can reuse whatever you have already implemented Feb 09 11:39:04 build #217 of brcm63xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/217 Feb 09 12:10:59 jow_laptop, thanks :) Feb 09 12:13:42 for accepting my (long-lasting) mvebu leds patch Feb 09 12:33:20 jow r48682 trunk/ package/base-files/files/lib/upgrade/common.sh package/base-files/files/sbin/sysupgrade target/linux/x86/base-files/lib/upgrade/platform.sh target/linux/x86/Makefile * x86: preserve partition table on sysupgrade Feb 09 12:33:32 jow r48683 trunk/package/system/ubox/Makefile * ubox: fix open() error handling (#21826) Feb 09 12:33:56 jow r48684 trunk/ target/linux/mvebu/profiles/linksys.mk package/kernel/linux/modules/leds.mk * mvebu: fix WRT1900AC v1 LED driver module Feb 09 12:34:10 jow r48685 trunk/package/base-files/ files/etc/iproute2/rt_tables Makefile * base-files: add netifd's default prelocal table to /etc/iproute2/rt_tables Feb 09 13:03:25 jow r48686 trunk/package/system/ubox/Makefile * ubox: fix kmodloader resource leaks (#21826) Feb 09 14:41:21 build #212 of pxa is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/212 Feb 09 14:41:28 build #215 of orion is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/215 Feb 09 14:41:40 build #215 of cns21xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/215 Feb 09 14:41:59 build #215 of cobalt is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/215 Feb 09 16:03:39 Are there any AC drivers that work rock solid on OpenWrt? Now all manufacturers are dropping 802.11a devices and replacing their devices with 802.11ac ones... so far all have seen that ath10k is not production ready and stable, is there any other 802.11ac driver/device that is stable and rock solid for production with OpenWrt? Feb 09 16:08:44 no Feb 09 16:09:03 mt76 will be the preferred choice but it is still maturing Feb 09 16:09:28 jow_laptop, thanks. So back to the drawing board... Feb 09 16:10:18 has there been some big change in tplink/atheros partnership? I see most AC devices from TPLINK now use Mediatek and not Atheros chips... Feb 09 16:15:43 valentt did you miss that atheros got swallowed by qualcomm? Feb 09 16:18:02 Are there any known problems with the Archer C5 v1.2? (Qualcomm ac) Feb 09 16:24:53 build #204 of ppc40x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/204 Feb 09 17:06:07 build #157 of adm8668 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/157 Feb 09 17:09:15 build #157 of mvebu is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/157 Feb 09 17:41:17 build #160 of ath25 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ath25/builds/160 Feb 09 18:00:14 build #219 of brcm47xx.legacy is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/219 Feb 09 18:23:28 build #215 of ramips.mt7628 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7628/builds/215 Feb 09 20:24:45 build #181 of arm64 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/arm64/builds/181 Feb 09 21:32:57 build #176 of ar7 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/176 Feb 09 21:55:52 jow_laptop: is libubox or anything else in openwrt meant to support other versions of lua at all? or only 5.1? Feb 09 21:56:14 only 5.1 is tested Feb 09 21:57:05 I'm trying to fix the libubox lua binding's cmake file to stop installing to whatever path it figures out by calling "lua" Feb 09 21:57:57 the pkg-config stuff I tried cleaning up earlier means it now at least compiles against the right version, but the install step is screwy. Feb 09 22:38:53 build #180 of x86.kvm_guest is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/x86.kvm_guest/builds/180 Feb 09 22:42:51 jow r48687 trunk/package/libs/libubox/Makefile * libubox: properly handle "null" values in blobmsg_add_json_element() Feb 09 22:44:26 build #180 of x86 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/180 Feb 09 23:08:36 jow_laptop: so, do you just manully fix up the cmake isntall to put the uloop.so into the right version lua path, or are you just always working on a system that _only_ has lua5.1, or do you just never work with lua and libubox on the host system? Feb 09 23:14:42 everytime I look at cmake it's like, "this is so good...." .... except it doesn't actually work.... Feb 09 23:15:00 karlp: I only have lua 5.1 on my host system Feb 09 23:15:48 even the FindLua51.cmake has bugs in it when there's multiple versions. it's all crap :| Feb 09 23:16:11 I'm giving up on it (again) and will just manually fix things after make install. Feb 09 23:16:15 I think part of the problem is that upstream Lua does not ship a .pc file Feb 09 23:16:24 and various distros do various things Feb 09 23:16:47 well, the pkg-config files would work, except they don't provide a variable for where to install the built lua libraries. Feb 09 23:17:10 and none of the provided cmake stuff does either actually. Feb 09 23:17:30 there's a verybuggy cmake module from luadist on github that is clearly _trying_ to, but it's super flaky too. Feb 09 23:19:38 lua -e 'for p in package.cpath:gmatch("/usr/lib/[^;?]+") do print(p) end' Feb 09 23:19:51 yeah, that first "lua" is the problem. Feb 09 23:20:02 that's lua 5.2 or 5.3 on my systems. Feb 09 23:20:19 ah Feb 09 23:20:29 so like the python debacle :) Feb 09 23:20:37 I guess. Feb 09 23:20:59 cmake has FindLua51 and FindLua modules, but they're both very buggy when multiple lua versions exist. Feb 09 23:21:33 and havnig to run lua to find out the path like that is only a workaround for pkg-config for the cmake modules not providing stuff like that you actually need. Feb 09 23:21:55 possibly, yes Feb 09 23:22:39 I usually edit the Makefiles / CmakeList.txt files on my host system because I always need nonstandard things Feb 09 23:23:04 Debian appears to deviate from what many upstreams expect wrt. Lua naming & library placement Feb 09 23:23:22 yeah, well, I was trying to put in some time to make it _work_ Feb 09 23:23:36 I've tried it briefly during the work day a few times, with no success, thought I'd try harder on my own time tonight. Feb 09 23:23:42 total waste of time. Feb 09 23:23:50 I guess I'm learning cmake... Feb 09 23:23:57 you're on debian as well? Feb 09 23:24:07 no, fedora Feb 09 23:27:38 hm Feb 09 23:27:44 debian defines a suitable install location Feb 09 23:27:50 pkg-config --variable INSTALL_CMOD lua5.1 Feb 09 23:27:51 /usr/lib/x86_64-linux-gnu/lua/5.1 Feb 09 23:28:22 and another INSTALL_LMOD for non-compiled modules Feb 09 23:28:34 hmm, yeah, I don't have those on mine :( Feb 09 23:28:45 jow, see you merged partition patch, ty. tested out ok for you? Feb 09 23:28:52 nyt: yes Feb 09 23:31:39 sweet Feb 10 00:20:16 heh, was making progress on making a jsonpath library, now problems with using libubox from c++ :) Feb 10 00:20:19 always fun... Feb 10 00:21:27 sounds more like work, than fun Feb 10 00:21:59 very much. Feb 10 01:14:11 hrm, replacing typeof with __typeof__ in libubox/list.h makes it work in C and c++. Feb 10 01:14:22 for _my_ hsot compiler at least. Feb 10 01:19:38 jow_laptop: https://github.com/karlp/jsonpath/pull/1/files is an idea, but I'm not entirely sure what the best library API really should be, whether the jsonpath expression parsing should be exposed too, because that exposes all the "export=" syntax extras and stuff? Feb 10 01:52:33 hi Feb 10 01:52:58 i need to add support for a new device in official branch(trunk) Feb 10 01:53:04 how i push the changes? Feb 10 02:03:55 hey guys Feb 10 02:04:07 i want to submit a patch that adds a device Feb 10 02:04:15 can you please help me out? Feb 10 02:07:39 Ntemis: have a look at the SubmittingPatches page on the wiki while you wait for someone knowledgeable Feb 10 02:07:57 doesnt give me anything to work on Feb 10 02:08:01 i did Feb 10 02:08:13 generic mumbo jumbo Feb 10 02:09:04 you asked how to submit a patch. that page tells you how... Feb 10 02:09:11 or are you asking how to develop the patch? Feb 10 02:10:28 nope Feb 10 02:10:46 i already have the patch Feb 10 02:10:55 and test complile it Feb 10 02:12:49 ok so Feb 10 02:13:03 i create my commit as a git patch Feb 10 02:13:25 then sent it by my email to openwrt-devel@lists.openwrt.org? Feb 10 02:20:01 use git send email; the formatting tends to get hosed otherwise. Feb 10 02:23:05 i dont have git configured to sent email Feb 10 02:45:33 it uses sendmail or whatever on the system iirc Feb 10 02:55:34 build #219 of ipq806x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ipq806x/builds/219 Feb 10 02:59:05 build #174 of avr32 is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/174 **** ENDING LOGGING AT Wed Feb 10 02:59:59 2016