Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2017-08-27

00:26:18 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.")
00:48:44***Saving seen data "./dancer.seen"
00:55:41 Quit ender` (Quit: You this read wrong.)
01:04:19 Join grandeoreilles [0] (5b4a3b02@gateway/web/freenode/ip.
01:10:24 Quit grandeoreilles (Quit: Page closed)
01:17:35 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 55.0.3/20170824053622])
01:22:44 Quit ZincAlloy (Quit: Leaving.)
01:27:42 Quit cc___ (Ping timeout: 255 seconds)
01:32:01 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627)
02:15:39 Join PurlingNayuki [0] (~Thunderbi@
02:20:13 Quit PurlingNayuki (Ping timeout: 248 seconds)
02:24:33 Quit _meg (Ping timeout: 240 seconds)
02:25:30 Join _meg [0] (~notsure@
02:45:24 Quit cc___ (Quit: WeeChat 1.9)
02:48:48***Saving seen data "./dancer.seen"
03:09:28 Quit __builtin (Remote host closed the connection)
03:34:57 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739)
03:49:03 Quit _meg (Ping timeout: 240 seconds)
03:50:45 Join _meg [0] (~notsure@
04:05:16 Join JanC_ [0] (~janc@lugwv/member/JanC)
04:06:35 Quit JanC (Killed ( (Nickname regained by services)))
04:06:35 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
04:18:42 Quit dovber__ (Ping timeout: 246 seconds)
04:39:57 Quit bray90820_ (Remote host closed the connection)
04:45:34 Quit _meg (Ping timeout: 240 seconds)
04:48:51***Saving seen data "./dancer.seen"
04:48:56 Join _meg [0] (~notsure@
04:56:51 Quit JanC (Remote host closed the connection)
05:03:57 Join JanC [0] (~janc@lugwv/member/JanC)
06:06:18 Quit TheSeven (Ping timeout: 276 seconds)
06:06:51 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
06:14:18 Join Strife89 [0] (
06:19:48 Quit TheSeven (Ping timeout: 246 seconds)
06:20:18 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
06:20:43 Join dovber__ [0] (~dovber@2600:8801:3180:de:beee:7bff:fee3:335f)
06:48:54***Saving seen data "./dancer.seen"
06:49:16 Quit dys (Ping timeout: 240 seconds)
07:24:54 Quit _meg (Ping timeout: 246 seconds)
07:25:56 Join _meg [0] (~notsure@
07:43:51 Join bray90820 [0] (
07:55:11 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:ec44:9bee:6941:b170)
08:47:58 Join PurlingNayuki [0] (~Thunderbi@
08:48:58***Saving seen data "./dancer.seen"
08:57:58 Join ender` [0] (
09:09:34 Quit jhMikeS (Ping timeout: 240 seconds)
09:24:39 Quit ZincAlloy (Quit: Leaving.)
09:30:38 Quit _meg (Ping timeout: 248 seconds)
09:34:17 Join _meg [0] (~notsure@
09:47:55 Quit Ruhan (Quit: Connection closed for inactivity)
09:49:30 Join xorly [0] (
10:18:05 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
10:20:19 Join jhMikeS [0] (
10:24:45 Quit jhMikeS (Ping timeout: 240 seconds)
10:49:00***Saving seen data "./dancer.seen"
10:53:52 Quit PurlingNayuki (Ping timeout: 248 seconds)
10:54:52 Join lebellium [0] (
11:02:19 Join dys [0] (
11:21:16 Quit _meg (Ping timeout: 255 seconds)
11:24:46 Quit xorly (Ping timeout: 248 seconds)
11:25:08 Join _meg [0] (~notsure@
12:34:46 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan)
12:49:04***Saving seen data "./dancer.seen"
12:59:22 Quit _meg (Ping timeout: 255 seconds)
12:59:34 Join iceCalt [0] (~iceCalt@
13:02:57 Join _meg [0] (~notsure@
13:47:21 Quit bray90820 (Ping timeout: 260 seconds)
13:48:15 Join bray90820 [0] (
14:13:09 Quit robertd1 (Read error: Connection reset by peer)
14:14:51 Join robertd1 [0] (
14:30:53 Join jhMikeS [0] (
14:32:46 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:2458:8d93:5a20:2498)
14:33:58 Quit _meg (Ping timeout: 246 seconds)
14:34:34 Join _meg [0] (~notsure@
14:40:42 Quit robertd1 (Quit: Leaving.)
14:41:10 Join robertd1 [0] (
14:43:34 Part ZincAlloy
14:45:46 Quit robertd1 (Remote host closed the connection)
14:46:54 Quit iceCalt (Quit: Leaving)
14:49:08***Saving seen data "./dancer.seen"
14:49:42 Quit Bilgus (Ping timeout: 268 seconds)
14:50:28 Join robertd1 [0] (~root@
14:53:19 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus)
15:00:00 Join Bilgus_ [0] (~Bilgus@gateway/tor-sasl/bilgus)
15:03:16 Quit Bilgus (Ping timeout: 268 seconds)
15:22:19 Quit pamaury (Remote host closed the connection)
15:24:45 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
16:20:48 Join xorly [0] (
16:22:15 Join LjL-Alplet [0] (~ljl@unaffiliated/ljl)
16:33:49 Join __builtin [0] (
16:33:49 Quit __builtin (Changing host)
16:33:49 Join __builtin [0] (~alpha@rockbox/developer/builtin)
16:49:09***Saving seen data "./dancer.seen"
16:57:32 Join PurlingNayuki [0] (~Thunderbi@
17:07:38 Join kbelyea [0] (
17:13:02 Quit xorly (Ping timeout: 248 seconds)
17:25:51 Quit PurlingNayuki (Remote host closed the connection)
17:25:57 Join PurlingNayuki1 [0] (~Thunderbi@
17:28:19 Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@
17:34:35pamaurythe build system is stuck, how do we unstuck it?
17:35:03pamauryand also why is it stuck?
17:36:15 Join Ruhan [0] (uid76353@gateway/web/
17:37:56pamauryapparently is says 4 builds remainings but it does not say which ones
17:46:40 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.")
17:55:01 Quit _meg (Ping timeout: 255 seconds)
17:56:37 Join _meg [0] (~notsure@
18:00:17__builtinpamaury: poke zagor?
18:00:51__builtinI remember last time it got unstuck when I pushed a new commit
18:03:21__builtinwhere did you see that there were 4 remaining?
18:07:38pamauryI sent him an email. In the log of my build client, the server sent a message "4 builds remaining" and that's it
18:07:48pamauryI pushed some new commits but still stuck
18:15:27 Join iceCalt [0] (~iceCalt@
18:15:34 Quit LjL-Alplet (Ping timeout: 240 seconds)
18:28:57 Part ender`
18:33:49 Quit kbelyea (Quit: WeeChat 1.6)
18:34:29 Join kbelyea [0] (
18:36:30__builtinyou should be able to tell from
18:37:00__builtinmost devices have the SHA 492dda0 listed, but some don't
18:41:49pamauryyeah but the others don't make much sense. I would expect to see 28ae700, the commit before the one being built but it's not there. Also for some reason the ibasso and ypr0/r1 are not built anymore
18:42:43pamaurymaybe there is a problem with omsk-gevaerts, that's the one that usually builds those
18:42:46pamaurygevaerts: ping
18:44:13*gevaerts has a look
18:44:32pamauryyour build client (omsk-gevaerts) is the one that does ibasso and ypr0 builds usually, but recently it has done 0 builds, I wonder if it has a problem
18:45:37gevaertsI don't see anything wrong right away
18:46:16gevaertsThe hex-gevaerts isn't running. Shouldn't cause the problem (omsk has the same toolchains I think), but it should run
18:46:43gevaertsAh, it got ypr1 right away. Not sure why omsk didn't get that
18:48:01pamauryI wonder why the ypr1 builds were not done in past 6/7 commits. Sounds like a bug with the server
18:49:13***Saving seen data "./dancer.seen"
18:49:22gevaertsI'm also restarting omsk, but that's going to take a while (it's on a VM, and I decided to reboot because that's easier than figuring out how to just restart the build client, and now it decided it needs to run fsck)
18:50:06gevaertsOK, hex finished ypr1 and is now doing ypr0
18:50:14fs-bluebotBuild Server message: Build round completed after 409758 seconds.
18:50:18fs-bluebotBuild Server message: Revision 492dda0 result: 4 errors 6 warnings
18:50:19fs-bluebotBuild Server message: New build round started. Revision c7f897f, 255 builds, 12 clients.
18:50:46pamauryyay \o/
18:51:13gevaertsI'm assuming omsk's connection got stuck at a weird state and that the server has a race condition
18:51:55 Join lebellium_ [0] (
18:52:27__builtin0% efficiency!
18:52:41__builtinanother thing even debian can't beat us at
18:52:48gevaertsAt least the next build will be a lot faster than expected!
18:54:11 Quit lebellium (Ping timeout: 260 seconds)
18:54:24 Nick lebellium_ is now known as lebellium (
18:56:43*pamaury tried to fix the ZEN LCD once again but failed
18:57:09pamauryI might finally push the Sony NWZ port, but that will mean adding a new toolchain and updating the build server so that it knows about it I think.
18:57:37iceCaltThe new Rockbox build I put over my 10y/o one is doing great.
18:58:01iceCaltMaybe had once a serious system crash. Can't remember what it said on it as my phone was dead that day (around Tuesday)
19:07:17fs-bluebotBuild Server message: Build round completed after 1017 seconds.
19:07:18fs-bluebotBuild Server message: Revision c7f897f result: 490 errors 75 warnings
19:09:47pamaurysomething bad happened :-/
19:11:17pamaurysounds like an option disappeared on recent gcc
19:11:31 Quit kbelyea (Ping timeout: 246 seconds)
19:11:36 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627)
19:12:20pamauryhum but that's weird because -Wimplicit-fallthrough is a new option, not an old one, also we don't set it anywhere I think, odd
19:12:43__builtinoh, my fault :(
19:13:31__builtinit's a result of b13f6e5b67abda2e466731f39d221eec2c9eb576
19:14:15fs-bluebotBuild Server message: New build round started. Revision 99e467e, 255 builds, 13 clients.
19:14:22__builtinshould be reverted
19:15:28pamauryI can't find this commit
19:16:03pamauryah I missed that commit
19:16:13__builtin"Silence GCC 7.x warnings when building simulator"
19:17:08pamauryI guess you can first run GCC to find its version and if it's >=7 then add those
19:18:40pamauryyou can use gcc -dumpversion for that
19:19:08pamauryactually we already get the version in configure, in $gccver
19:20:13pamauryat line ~4200 we have a bunch of tests against gcc versions
19:24:00*pamaury will fix the yellow because of sokoban
19:25:41__builtinit'd be so nice if gerrit could have some way to build patch sets before they're merged
19:26:41pamauryyeah, it's one of those things our build systemd and patch tracker sucks at
19:27:03pamaurymaybe if we move our infrastructure to something else it could be implemented
19:27:33 Quit _meg (Ping timeout: 240 seconds)
19:28:12 Join _meg [0] (~notsure@
19:29:57__builtinI suppose it does open up some security holes
19:30:11 Join LjL-Laplet [0] (~ljl@unaffiliated/ljl)
19:31:33pamauryour infrastructure is not exact super secure
19:31:57*__builtin glances at the wiki spambots
19:32:31__builtinsome kind of button on gerrit for committers to "build this patch" or something would be nice
19:33:05fs-bluebotBuild Server message: Build round completed after 1131 seconds.
19:33:07fs-bluebotBuild Server message: Revision 99e467e result: 0 errors 25510 warnings
19:33:07fs-bluebotBuild Server message: New build round started. Revision b31ae45, 255 builds, 11 clients.
19:38:04 Quit cc___ (Ping timeout: 255 seconds)
19:38:21__builtinthere is already a CGI script in the www repo that seems to allow release candidate builds to be initiated with a password and SHA
19:50:37fs-bluebotBuild Server message: Build round completed after 1051 seconds.
19:50:38fs-bluebotBuild Server message: Revision b31ae45 result: 0 errors 36 warnings
19:55:46 Quit Ruhan (Quit: Connection closed for inactivity)
20:30:37 Join kbelyea [0] (
20:35:59 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan)
20:49:17***Saving seen data "./dancer.seen"
21:00:05 Join xorly [0] (
21:02:45 Join MrZeus [0] (~MrZeus@2a02:c7f:7066:fb00:c13f:53b9:fb5e:5b6d)
21:35:06__builtinhmm, this smells like a bug to me
21:35:21__builtinapps/plugins/keybox.c:317:21: warning: comparison between pointer and zero character constant [-Wpointer-compare]
21:35:29__builtinif (entry->name != '\0')
21:35:55__builtinwhere entry->name is a statically allocated array
21:37:43TheLemonMansombody forgot a * (or a [0])
21:38:53pamauryyeah I think there should be a [0]
21:39:16pamauryespecially since the code in delete_entry does entry2->name[0] = '\0';
21:43:20fs-bluebotBuild Server message: New build round started. Revision 1cd96b4, 255 builds, 13 clients.
21:44:21__builtinI'm going to see I can't get it to be all green
21:55:40fs-bluebotBuild Server message: Build round completed after 740 seconds.
21:55:41fs-bluebotBuild Server message: Revision 1cd96b4 result: 0 errors 43 warnings
22:03:31__builtinhmm, what's wrong with this line?
22:03:32__builtinconst uint8_t const *table;
22:03:57__builtingcc warns, "apps/plugins/mp3_encoder.c:75:17: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]"
22:04:08__builtinbut isn't it just a constant pointer to constant data?
22:05:12pamaury__builtin: it's redundant, it shoule be const X * const
22:06:20LjL-Lapletalexbobp, did you see what happened to Gadgetbridge a while ago copyright-wise, by the way?
22:06:45__builtinah, I see
22:26:57alexbobpLjL-Laplet: nope :o
22:31:33 Quit dys (Ping timeout: 240 seconds)
22:33:03 Quit kbelyea (Ping timeout: 248 seconds)
22:39:38 Join dys [0] (
22:48:09 Quit _meg (Ping timeout: 246 seconds)
22:49:21***Saving seen data "./dancer.seen"
22:50:01 Quit alexweissman (Remote host closed the connection)
22:50:22 Join _meg [0] (~notsure@
22:55:04 Join alexweissman [0] (
23:14:21 Quit iceCalt (Read error: Connection reset by peer)
23:14:53 Join iceCalt [0] (~iceCalt@
23:16:15 Quit pamaury (Ping timeout: 248 seconds)
23:18:57 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 55.0.3/20170824053622])
23:29:11 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.")
23:40:04 Join shai [0] (
23:40:46 Quit shai (Read error: Connection reset by peer)
23:48:40 Quit iceCalt (Quit: Leaving)

Previous day | Next day