00:57:00 | rb-bluebot | Build Server message: New build round started. Revision 0d355a9c47, 303 builds, 7 clients. |
01:00 |
01:14:55 | rb-bluebot | Build Server message: Build round completed after 1076 seconds. |
01:14:57 | rb-bluebot | Build Server message: Revision 0d355a9c47 result: All green |
01:15:27 | | Join dys [0] (~dys@user/dys) |
01:22:16 | rb-bluebot | Build Server message: New build round started. Revision 0c7f66ab5f, 303 builds, 7 clients. |
01:48:49 | rb-bluebot | Build Server message: Build round completed after 1593 seconds. |
01:48:51 | rb-bluebot | Build Server message: Revision 0c7f66ab5f result: All green |
01:48:55 | rb-bluebot | Build Server message: New build round started. Revision f242b0ec6c, 303 builds, 7 clients. |
01:53:28 | *** | No seen item changed, no save performed. |
02:00 |
02:03:56 | | Join fourHZ [0] (~fourHZ@92-52-40-121.dynamic.orange.sk) |
02:10:41 | rb-bluebot | Build Server message: Build round completed after 1306 seconds. |
02:10:43 | rb-bluebot | Build Server message: Revision f242b0ec6c result: All green |
02:57:17 | | Join mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae) |
03:00 |
03:53:32 | *** | No seen item changed, no save performed. |
04:00 |
04:39:39 | | Quit ats (Read error: Software caused connection abort) |
04:39:55 | | Join ats [0] (~ats@cartman.offog.org) |
05:00 |
05:28:24 | | Quit larbob (Read error: Software caused connection abort) |
05:30:12 | | Join larbob [0] (~larbob@159.65.42.191) |
05:53:34 | *** | Saving seen data "./dancer.seen" |
07:00 |
07:05:06 | Fishbyte | CH23_M: Yes, it is now, it wasn't set for write perms for other users, but it's still not in Rockbox, and I still can't find a way to tell rockbox where it is |
07:06:03 | Fishbyte | hold on it my change didn't effect it |
07:24:01 | Fishbyte | I unmount it, and then change the mount location's permission to read and write, and then mount it and it switches back. I know this is round-about, but I don't quite know how to mount this with permissons for everyone |
07:25:00 | Fishbyte | It switching back is the permissions to drwxr-xr-x from drwxr-xrwx |
07:34:40 | | Join massiveH [0] (~massiveH@2600:4040:a993:4900:2ded:6339:3fac:b071) |
07:40:21 | Fishbyte | Ok I remounted with some options and now it's rw to everyone |
07:47:47 | CH23 | Fishbyte, does arch use fstab? |
07:51:22 | CH23 | if so, try setting an entry like this for the iPod: /dev/disk/by-label/IPOD /media/ipod/ vfat defaults,suid,user,noauto,iocharset=utf8 0 0 |
07:52:04 | Fishbyte | Yeah it does, I'll add that then, thanks for pointing this all out, I'll try to set it up in a second |
07:53:38 | *** | No seen item changed, no save performed. |
07:54:58 | CH23 | make sure to change the first location and second location to the actual device label, and the actual mountpoint :) |
07:58:55 | Fishbyte | CH23: Ok well I went to install, and I got the error could not open ipod: permisson denied |
07:59:22 | Fishbyte | but other users have full access and I can confirm it |
08:00 |
08:02:19 | Fishbyte | does it being owned by root not allow it |
08:05:12 | CH23 | Fishbyte, on my laptop the iPod directory has the following rights and is owned by my user: drwxr-xr-x 12 ch23 ch23 16K Jan 1 1970 ipod |
08:07:05 | Fishbyte | mine is drwxrwxrwx 17 root root 16K Dec 31 1969 ipod |
08:07:27 | Fishbyte | how would I change a file system to be owned by me |
08:09:40 | CH23 | first unmount it, then do sudo chown [your user]: [directory] |
08:10:25 | CH23 | uhh |
08:10:54 | CH23 | for me it's: sudo chown ch23: /media/ipod/ |
08:11:01 | fourHZ | and maybe put an -R to do it recursive? |
08:11:23 | CH23 | fourHZ, not needed, the ipod file structure will be mounted as whatever |
08:11:30 | fourHZ | ok |
08:12:17 | Fishbyte | I do sudo mount -o rw,users,umask=000 /dev/sdg2 ~/ipod and it over writes any permission changes I do to the device, so now it's back to root root but has all 777 |
08:12:20 | Fishbyte | still |
08:13:34 | CH23 | Fishbyte, that's because you do it as sudo |
08:14:13 | Fishbyte | yeah that's what I figured, but it won't let me mount it as non su |
08:15:14 | CH23 | Fishbyte, did you add the fstab entry? |
08:15:25 | Fishbyte | no I'll do that |
08:20:59 | CH23 | after doing that, you should be able to mount the ipod by doing: mount /media/ipod |
08:21:12 | CH23 | (in my case, i don't know where your mountpoint is) |
08:21:23 | CH23 | no sudo, no long commands |
08:24:38 | Fishbyte | yup, it's mounted just like yours |
08:28:46 | Fishbyte | rockbox is giving the same error of "Could not open Ipod: permission denied" 3 times in the progress window |
08:29:04 | Fishbyte | it has the mount location |
08:29:44 | Fishbyte | it looks like drwxr-xr-x 18 fishbyte fishbyte 16K Dec 31 1969 ipod |
08:30:26 | CH23 | Fishbyte, did you restart the rockbox program? |
08:31:33 | Fishbyte | I did graphically, I'll try to kill it |
08:31:56 | CH23 | at this point the program should totally have access to it |
08:32:07 | Fishbyte | I'll probably just reboot |
08:32:13 | CH23 | might work |
08:32:14 | Fishbyte | Thank you guys a ton |
08:32:20 | CH23 | de nada :) |
08:33:29 | | Quit Fishbyte (Remote host closed the connection) |
08:38:43 | | Join Fishbyte [0] (~Fishbyte@2601:985:200:291::7a91) |
08:39:42 | Fishbyte | Ok one more question (hopefully) I don't get the permission error anymore, I get "Error: could not retrieve device name" |
08:41:07 | Fishbyte | If you aren't familiar with it, or know a solution, I'll just go to a windows machine and install itunes to format it |
08:45:45 | CH23 | Fishbyte, did you format it previously? |
08:45:50 | CH23 | if so, how? |
08:46:35 | Fishbyte | No this was a family members, is formatting a required step |
08:48:01 | CH23 | Fishbyte, not usually. what's in the root of your iPod? should be something like: Calendars Contacts iPod_Control Music Notes Photos Playlists Podcasts Recordings |
08:49:16 | Fishbyte | Yeah all that is there |
08:51:35 | CH23 | can you manually select the correct device in the rockbox utility? |
08:51:49 | Fishbyte | Yes I can |
08:51:57 | CH23 | then i'd just try that |
08:52:20 | Fishbyte | Well I do, and then I get that error when going to install |
08:52:57 | CH23 | ah sorry that wasn't clear to me. then perhaps a reinstall would be better |
08:53:44 | Fishbyte | Roger that, Ok *now* thanks for helping |
08:53:51 | | Quit Fishbyte (Quit: Leaving) |
09:00 |
09:00:10 | | Quit massiveH (Quit: Leaving) |
09:25:09 | | Quit CH23_M (Ping timeout: 260 seconds) |
09:28:02 | | Join CH23_M [0] (~CH23@revspace/participant/ch23) |
09:29:55 | | Quit CH23_M (Read error: Connection reset by peer) |
09:30:40 | | Join CH23_M [0] (~CH23@revspace/participant/ch23) |
09:42:12 | | Join amachronic [0] (~amachroni@user/amachronic) |
09:44:27 | rb-bluebot | Build Server message: New build round started. Revision 9368844ad1, 303 builds, 7 clients. |
09:47:42 | | Join chris_s [0] (~chris_s@ip-078-094-233-058.um19.pools.vodafone-ip.de) |
09:51:54 | chris_s | Anyone else recently getting "Error accessing playlist file" messages when playback is stopped after opening a playlist and both Load to Ram (for the DB) and dir cache are activated? |
09:52:07 | chris_s | Looks like it occurs during background scanning in the playlist_thread for the SYS_TIMEOUT case, when get_filename is called |
09:52:15 | chris_s | I think I used to just disable that. |
09:52:24 | chris_s | Not sure what's up with that... |
09:52:46 | chris_s | only seems to happen on the iPod and not the M3K for some reason |
09:53:40 | *** | Saving seen data "./dancer.seen" |
09:57:59 | chris_s | but I remember seeing this in the past at some point |
10:00 |
10:06:21 | speachy | I haven't seen one of those for a long time. |
10:06:46 | rb-bluebot | Build Server message: Build round completed after 1340 seconds. |
10:06:52 | rb-bluebot | Build Server message: Revision 9368844ad1 result: All green |
10:07:12 | rb-bluebot | Build Server message: New build round started. Revision 830436a282, 303 builds, 7 clients. |
10:08:11 | | Quit fourHZ (Quit: Client closed) |
10:09:20 | chris_s | it's probably the "hack" I applied to my own build that disabled dircache_search.. didn't think about that. I should replicate it on the official build before opening my mouth the next time... :D |
10:24:49 | rb-bluebot | Build Server message: Build round completed after 1057 seconds. |
10:24:52 | rb-bluebot | Build Server message: Revision 830436a282 result: All green |
10:25:02 | rb-bluebot | Build Server message: New build round started. Revision 3815ef8050, 303 builds, 7 clients. |
10:29:23 | | Quit chris_s (Quit: Connection closed) |
10:43:01 | rb-bluebot | Build Server message: Build round completed after 1080 seconds. |
10:43:03 | rb-bluebot | Build Server message: Revision 3815ef8050 result: All green |
10:43:08 | rb-bluebot | Build Server message: New build round started. Revision ec1611dfa6, 303 builds, 7 clients. |
10:46:08 | amachronic | speachy, do you think the autobuilder page should show RAM deltas in the table instead of binsize deltas? |
10:46:27 | speachy | there's an argument for that, yeah |
10:47:15 | amachronic | i was thinking of it since one of bilgus recent commits (e7e20fab) actually added RAM usage but shows reduced binsize. |
10:47:16 | speachy | but RAM size doesn't shrink nearly as easily, unless you nuke static tables. |
10:47:33 | amachronic | RAM size = bin size + BSS? |
10:47:59 | speachy | unless we're running out of NV storage, yeah |
10:49:03 | amachronic | since we try to keep the memory footprint low it makes sense to account for BSS in the table as well |
10:49:27 | amachronic | it's less misleading that way |
10:51:29 | | Quit CH23_M (Ping timeout: 260 seconds) |
10:51:49 | speachy | the www script pulls the 'Binary size' out of rockbox-info.txt. There's also 'RAM usage' there as well, which (generally) includes the binary size. |
10:52:15 | | Join fourHZ [0] (~fourHZ@92-52-40-121.dynamic.orange.sk) |
10:52:15 | | Join CH23_M [0] (~CH23@revspace/participant/ch23) |
10:52:16 | speachy | then again I don't think we have any execute-from-flash targets any more? |
10:52:35 | speachy | (wait, the old m58k irivers technically support it I think..) |
10:53:07 | amachronic | I thought they did something like that but I'm not sure how they work. |
10:54:13 | amachronic | the www script already scrapes RAM usage so it's just a matter of switching what shows up in the table |
10:54:14 | speachy | the "RAM usage" includes all fixed allocations too (eg plugin/codec scratch space) |
10:54:59 | speachy | yeah it displays RAM delta too if you hover over the text |
10:55:38 | amachronic | usually the ram delta is same as the binsize delta |
10:56:39 | amachronic | except if a static buffer gets added or removed |
10:58:18 | speachy | I forgot that when I rewrote that binsize script I put in the provisions for showing either, though I left the main display the binsize |
11:00 |
11:00:05 | speachy | ok, when this one finishes it should show RAM deltas instead, but both are displayed. |
11:01:08 | speachy | it wuold be really cool to include stack utilization in there too, but I don't think there's any way to get that out of the current tooling. |
11:03:37 | amachronic | -fstack-usage works at least on mips |
11:04:28 | speachy | I think we're going to need LTO (at minimum) to have meaningful stack usage |
11:04:35 | speachy | across compilation units I mean |
11:06:49 | speachy | but there's no way to report actual usage, just if it exceeds some threshold, correct? |
11:07:46 | amachronic | it outputs an .su file that tells you the stack usage of individual functions |
11:08:19 | amachronic | for doing CI like "whoops that last commit might blow the stack with this call tree" you need a more advanced whole-program analyzer |
11:08:39 | speachy | ah, ok |
11:09:20 | amachronic | i don't think there are any stack usage analyzers like that in GCC or clang unfortunately. |
11:09:29 | _bilgus | amachronic, that was because of the static maxpath but its probably ok I to not be static but I was afraid of blowing the stack depending on the caller |
11:10:36 | rb-bluebot | Build Server message: Build round completed after 1648 seconds. |
11:10:38 | rb-bluebot | Build Server message: Revision ec1611dfa6 result: All green |
11:10:43 | rb-bluebot | Build Server message: New build round started. Revision 8379c6eb07, 303 builds, 7 clients. |
11:10:48 | amachronic | _bilgus: i don't mind, it just made me think the table's a little misleading :) |
11:12:28 | amachronic | come to think of it, wouldn't that static buffer need a mutex in case multiple callers get blocked in open()? |
11:13:31 | speachy | whoops, left a line out. |
11:14:51 | speachy | next build will display the correct data. |
11:16:15 | speachy | would it perhaps make more sense to just display both ramdelta and bindelta tables? |
11:17:43 | amachronic | i was thinking maybe a button to toggle between them |
11:18:25 | _bilgus | amachronic, wouldn't you need to yield I guess on hosted might be possible |
11:18:51 | speachy | hmm, that shouldn't be too bad. ain't going to happen today though |
11:18:57 | amachronic | _bilgus open() itself yields by disk access |
11:19:25 | speachy | maybe I can work on that while the server is offline for the upgrade. |
11:20:38 | _bilgus | ah it only locks for writers then? |
11:21:49 | amachronic | you can have a context switch any time a thread has to block on a mutex or semaphore |
11:22:12 | amachronic | unlocking a mutex or releasing a semaphore in a low priority thread can also cause a switch to a higher priority thread |
11:23:05 | _bilgus | with it being in tagcache that would be a concern then I'll look at it this eve |
11:24:09 | amachronic | i wish we had preemptive threading :-/ |
11:24:26 | _bilgus | might be better to just put it on the stack I didn't notice any ill effect in tests but I started worrying that it might blow the stack after |
11:30:41 | rb-bluebot | Build Server message: Build round completed after 1199 seconds. |
11:30:42 | rb-bluebot | Build Server message: Revision 8379c6eb07 result: All green |
11:33:27 | | Quit amachronic (Quit: amachronic) |
11:40:28 | speachy | ok, that worked |
11:53:44 | *** | Saving seen data "./dancer.seen" |
11:59:46 | | Quit speachy (Quit: WeeChat 3.6) |
12:00 |
12:12:24 | | Join chris_s [0] (~chris_s@ip-095-223-073-217.um35.pools.vodafone-ip.de) |
12:16:47 | chris_s | If anyone can provide insight into g4827 (a "one-liner"), I'd appreciate the input. I'm obviously missing something... |
12:19:01 | | Quit mink (Ping timeout: 252 seconds) |
12:32:01 | chris_s | or maybe it doesn't actually work – just tried it with Roblox again. Oh well, at least that makes sense... not my day today. |
12:34:46 | | Quit chris_s (Quit: Connection closed) |
12:42:14 | | Quit CH23_M (Read error: Connection reset by peer) |
12:43:25 | | Join CH23_M [0] (~CH23@revspace/participant/ch23) |
13:00 |
13:06:14 | | Join chris_s [0] (~chris_s@ip-095-223-073-217.um35.pools.vodafone-ip.de) |
13:06:58 | chris_s | turns out in Rockblox's case, it was just a misspelled ifdef.. |
13:10:46 | chris_s | so then, maybe, my dumb question remains if the other patch could *possibly* fix anything |
13:12:25 | | Quit chris_s (Quit: Connection closed) |
13:33:02 | | Join lebellium [0] (~lebellium@2a01cb040109a60057484dad52b1f739.ipv6.abo.wanadoo.fr) |
13:44:16 | | Quit jacobk (Ping timeout: 252 seconds) |
13:47:39 | | Quit CH23_M (Ping timeout: 260 seconds) |
13:48:10 | | Join CH23_M [0] (~CH23@revspace/participant/ch23) |
13:53:47 | *** | Saving seen data "./dancer.seen" |
14:00 |
14:02:20 | | Quit CH23_M (Read error: Connection reset by peer) |
14:03:25 | | Join CH23_M [0] (~CH23@revspace/participant/ch23) |
15:00 |
15:12:50 | | Join jacobk [0] (~quassel@47-186-81-17.dlls.tx.frontiernet.net) |
15:53:49 | *** | Saving seen data "./dancer.seen" |
16:00 |
16:54:07 | | Join othello7 [0] (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
17:00 |
17:17:04 | | Quit othello7 (Ping timeout: 260 seconds) |
17:53:52 | *** | Saving seen data "./dancer.seen" |
18:00 |
18:29:36 | | Quit fourHZ (Quit: Ping timeout (120 seconds)) |
18:48:21 | | Join massiveH [0] (~massiveH@2600:4040:a993:4900:2ded:6339:3fac:b071) |
19:00 |
19:21:34 | | Quit massiveH (Quit: Leaving) |
19:28:59 | | Join massiveH [0] (~massiveH@2600:4040:a993:4900:4d19:ff30:6855:9606) |
19:43:19 | | Quit lebellium (Quit: Leaving) |
19:44:22 | | Join othello7 [0] (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
19:53:54 | *** | Saving seen data "./dancer.seen" |
20:00 |
20:03:10 | | Join othello8 [0] (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
20:04:49 | | Quit othello7 (Ping timeout: 260 seconds) |
20:04:49 | | Nick othello8 is now known as othello7 (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
21:00 |
21:15:05 | rb-bluebot | Build Server message: New build round started. Revision 80b8b13544, 303 builds, 7 clients. |
21:29:39 | | Quit othello7 (Ping timeout: 260 seconds) |
21:31:32 | | Join othello7 [0] (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
21:36:41 | rb-bluebot | Build Server message: Build round completed after 1296 seconds. |
21:36:43 | rb-bluebot | Build Server message: Revision 80b8b13544 result: All green |
21:50:33 | | Quit othello7 (Ping timeout: 268 seconds) |
21:53:55 | *** | Saving seen data "./dancer.seen" |
21:55:32 | | Join othello7 [0] (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
21:58:38 | | Quit jacobk (Ping timeout: 256 seconds) |
22:00 |
22:12:45 | rb-bluebot | Build Server message: New build round started. Revision 3745c813f9, 303 builds, 7 clients. |
22:19:43 | | Join jacobk [0] (~quassel@47-186-81-17.dlls.tx.frontiernet.net) |
22:30:37 | | Join dconrad [0] (~dconrad@152.117.104.235) |
22:39:48 | rb-bluebot | Build Server message: Build round completed after 1624 seconds. |
22:39:50 | rb-bluebot | Build Server message: Revision 3745c813f9 result: All green |
22:42:43 | | Quit othello7 (Ping timeout: 252 seconds) |
23:00 |
23:12:24 | | Join othello7 [0] (~Thunderbi@pool-173-49-130-165.phlapa.fios.verizon.net) |
23:16:58 | rb-bluebot | Build Server message: New build round started. Revision 97a82ee3ec, 303 builds, 7 clients. |
23:25:31 | | Quit othello7 (Ping timeout: 268 seconds) |
23:36:58 | rb-bluebot | Build Server message: Build round completed after 1199 seconds. |
23:37:01 | rb-bluebot | Build Server message: Revision 97a82ee3ec result: 92 errors 0 warnings |
23:37:12 | | Quit m01 (Quit: Konversation terminated.) |
23:39:21 | | Join m01 [0] (~quassel@vps-b172b88b.vps.ovh.net) |
23:53:56 | *** | Saving seen data "./dancer.seen" |
23:56:46 | rb-bluebot | Build Server message: New build round started. Revision 1e6d643cfb, 303 builds, 7 clients. |
23:57:05 | _bilgus | well ruined that nice green board |