| *** jwadas1 has joined #baserock | 02:21 | |
| jwadas1 | Hey all. Anyone home? | 02:21 |
|---|---|---|
| *** Walkerdine has joined #baserock | 02:53 | |
| Walkerdine | My morph seems to be broken now | 03:30 |
| *** gtristan has quit IRC | 03:31 | |
| *** gtristan has joined #baserock | 04:06 | |
| *** gtristan has quit IRC | 04:41 | |
| *** gtristan has joined #baserock | 04:42 | |
| *** zoli__ has joined #baserock | 05:24 | |
| *** zoli__ has joined #baserock | 05:26 | |
| *** zoli__ has quit IRC | 05:30 | |
| *** gtristan has quit IRC | 05:48 | |
| *** gtristan has joined #baserock | 06:00 | |
| *** zoli__ has joined #baserock | 06:26 | |
| *** zoli__ has quit IRC | 06:30 | |
| *** paulwaters_ has joined #baserock | 06:35 | |
| *** jwadas1 has quit IRC | 06:50 | |
| gtristan | Ok so... ubuntu lts version of btrfs-tools; segfaults when mkfs.btrfs is given the --features options to unflag some features | 07:04 |
| gtristan | it segfaults, it does not print the unrecognized option message checked for in extensions/writeexts.py | 07:05 |
| * gtristan is checking if it's one of the particular 3 options passed, or any of them | 07:06 | |
| gtristan | if all three are omitted... image is almost created... fails on smth else (/me collects log for that one) | 07:06 |
| *** ssam2 has joined #baserock | 07:07 | |
| *** ChanServ sets mode: +v ssam2 | 07:07 | |
| gtristan | ah, the other error is lack of extlinux tool | 07:25 |
| gtristan | looks like definitions/extensions uses various system tools... are those dependencies declared somewhere ? so that, e.g., tools like ybd can check for them before blindly running the scripts ? | 07:26 |
| gtristan | aha, now I have a gnome-system-x86_64.img which I dont expect to boot :) | 07:33 |
| * gtristan tries | 07:33 | |
| gtristan | boots into a shell, that's a start | 07:40 |
| *** zoli__ has joined #baserock | 07:42 | |
| *** zoli__ has quit IRC | 07:46 | |
| ssam2 | gtristan: they aren't declared in any machine-readable way at present | 07:52 |
| ssam2 | the original idea was that everything would run in a Baserock system/chroot, which would have all the deps available | 07:53 |
| ssam2 | hi by the way :-) | 07:53 |
| gtristan | Nice to meet here :) | 07:53 |
| *** toscalix__ has joined #baserock | 07:54 | |
| wdutch | hello all concerned with CIAT, the history has vanished from the frontend but I did back it up | 07:54 |
| gtristan | I'm taking down notes of all the brute force hacks I needed (not SO many btw) to get where I did with ybd on ubuntu 14.04 | 07:54 |
| wdutch | I'm experimenting with the new pipeline methods, I tried to get it all done last night while nobody was looking but it took a long time due to a change in an upstream for foundation | 07:55 |
| wdutch | pdar: deploy seems to be breaking at the lines | 08:00 |
| wdutch | # Remove the artifacts | 08:00 |
| wdutch | sudo rm -rf "$ybd_base"/artifacts/"$s_n".* | 08:00 |
| wdutch | here's a log http://ciat.baserock.org:8010/builders/genivi-demo-platform-x86_64%20Deploy/builds/1/steps/shell_1/logs/stdio | 08:01 |
| wdutch | I have no idea why :( | 08:01 |
| wdutch | possibly it's not that but the command after it when control is returned to the python wrapper | 08:01 |
| gtristan | jjardon, around ? | 08:03 |
| wdutch | pdar: ignore me | 08:05 |
| pedroalvarez | wdutch: we don't have arm pipeline anymore? | 08:05 |
| wdutch | pedroalvarez: not currently! sorry | 08:05 |
| wdutch | it's a bit chaotic | 08:05 |
| wdutch | but should be super easy to spin up new pipelines once I'm done debugging | 08:06 |
| * pedroalvarez looks a the new names of the columns | 08:06 | |
| wdutch | the names are generated from the name of the pipeline + the 'step', which is one of Build, Deploy, Test, Publish | 08:07 |
| wdutch | Integration is special for now | 08:07 |
| pedroalvarez | aha! | 08:07 |
| *** zoli__ has joined #baserock | 08:08 | |
| pedroalvarez | i liked the word "generated" | 08:08 |
| wdutch | :) | 08:08 |
| * wdutch needs a test pipeline that isn't subject to the whims of upstream | 08:17 | |
| *** mariaderidder has joined #baserock | 08:21 | |
| wdutch | "TypeError: coercing to Unicode: need string or buffer, bool found" | 08:21 |
| wdutch | http://ciat.baserock.org:8010/builders/genivi-demo-platform-x86_64%20Deploy/builds/3/steps/shell_1/logs/stdio | 08:21 |
| wdutch | I feel like we've seen that before | 08:21 |
| pedroalvarez | uff | 08:22 |
| pedroalvarez | could we keep triggering builds O;) | 08:26 |
| wdutch | we could | 08:26 |
| pedroalvarez | oh, json gives you a "eta" | 08:30 |
| pedroalvarez | "-9.5367431640625e-07" | 08:31 |
| rjek | Soon, then. | 08:31 |
| pedroalvarez | I was using the time of the previous build | 08:31 |
| *** jonathanmaw has joined #baserock | 08:36 | |
| wdutch | right lets get an arm pipeline | 08:44 |
| pedroalvarez | yay! | 08:46 |
| *** gtristan has quit IRC | 08:46 | |
| * pedroalvarez has progress bars for the builds :) | 08:47 | |
| wdutch | nice | 08:48 |
| pedroalvarez | if the build is taking more than the previous build, it will stay at 90% | 08:49 |
| wdutch | hmm | 08:52 |
| pedroalvarez | http://ciat.baserock.org:8888/#/ | 08:52 |
| toscalix__ | pedroalvarez: what is the criteria used to define "progress"? | 08:53 |
| toscalix__ | in the progress bar? | 08:54 |
| *** toscalix__ is now known as toscalix | 08:54 | |
| pedroalvarez | ("time of actual run" *100) / "time of last build" | 08:55 |
| toscalix | is it possible to change the "time of last build" by "average time of a build" in the context of the demo? | 08:59 |
| toscalix | I mean, the demo will be a controlled environment, so is it possible to define an average time that we can be confident on? | 08:59 |
| wdutch | the average will be a vast over estimate | 09:00 |
| toscalix | I think your equation is good for uncontrolled enviromnments, that is, when we cannot stablish a good reference | 09:00 |
| toscalix | I wonder if we can in the context of the demo | 09:00 |
| wdutch | the data is skewed by the rare builds which can take >3hours | 09:01 |
| toscalix | so what you are saying is that we cannot define a reference time in the context of the demo? | 09:01 |
| wdutch | we could define one | 09:01 |
| wdutch | the average would be a bad way to define it | 09:01 |
| toscalix | do you have a better suggestion then? | 09:01 |
| pedroalvarez | it should be possible to hardcode a "time of last build" yes | 09:02 |
| Zara | median vs mean? | 09:02 |
| toscalix | we could use the median, yes | 09:02 |
| toscalix | of some values, if the distribution of values is a tall gauss chamber or similar function | 09:03 |
| pedroalvarez | getting more than one value of previous build times, will be a pain | 09:03 |
| toscalix | pedroalvarez: understood | 09:03 |
| pedroalvarez | (from my non-js experience POV) | 09:04 |
| toscalix | so we will use the "time of last build" because getting data for a better reference is too painful | 09:04 |
| toscalix | correct? | 09:04 |
| pedroalvarez | it, of course, can be done | 09:05 |
| * pedroalvarez triggers a build, and looks at the status bar | 09:05 | |
| toscalix | We have other tasks to do, so good enough for me now | 09:05 |
| toscalix | pedroalvarez pdar let me know when you consider the progress bar done so we talk about the dialogs. I am taking a look at them | 09:07 |
| pedroalvarez | If we only want progress bars in the builds column, then I think it's done | 09:08 |
| pedroalvarez | toscalix: pdar is not around yet. I think we can start talking about the dialogs | 09:09 |
| pdar | i had imagined them in the builder box | 09:09 |
| pedroalvarez | oh, he is! | 09:09 |
| pedroalvarez | pdar: what exactly? | 09:10 |
| pdar | i am! | 09:10 |
| pdar | oh the progree bar itself | 09:10 |
| toscalix | pdar: that is a good idea | 09:11 |
| toscalix | instead of having a different dialog, we include the info in the box itself | 09:11 |
| toscalix | pedroalvarez: how do you see that? | 09:12 |
| pedroalvarez | done :) | 09:12 |
| wdutch | may I quickly reboot orchestration? | 09:13 |
| toscalix | ah, you mean the profgrees bar | 09:13 |
| toscalix | I also like it better, yes | 09:13 |
| wdutch | going once | 09:13 |
| wdutch | going twice | 09:13 |
| wdutch | going down | 09:13 |
| toscalix | We only need to be carefull with colours | 09:13 |
| pedroalvarez | when built, green, when building orange | 09:14 |
| toscalix | If it will be green, the contrast need to be high. Remember than people will see the screen from 1 or 2 meters of distance | 09:14 |
| rjek | Have bloody great tick or cross | 09:14 |
| toscalix | pedroalvarez can you use the same color that the logo, and instead of white, the same color than the background? | 09:15 |
| toscalix | in the progress bar? | 09:15 |
| pedroalvarez | for the bars, I think I only have 4 choices | 09:16 |
| pedroalvarez | (of colors) | 09:16 |
| pedroalvarez | (using the twitter bootstrap library) | 09:16 |
| toscalix | which are? | 09:17 |
| SotK | pedroalvarez: you can override the css in your local stylesheet | 09:17 |
| pedroalvarez | yes, I can try to do that :) | 09:18 |
| pedroalvarez | toscalix: so, different colors when building and finished building is ok? | 09:18 |
| wdutch | we have an arm pipeline but I can't push to the candidate ref :( | 09:19 |
| wdutch | "error: src refspec cu010-trove/arm-base does not match any." | 09:19 |
| SotK | I think something like `.pass > .progress { background-color: #77ee77; }` would work to change the background to green when in a green box | 09:19 |
| * pedroalvarez is still trying to understand "use the same color that the logo, and instead of white, the same color than the background" | 09:19 | |
| *** gtristan has joined #baserock | 09:19 | |
| toscalix | pedroalvarez: in my opinion, there are two options: 1.- Going for green, ensuring a high contrast between the box color and the bar 2.- going for the calors we are already using, that is, dark (background) and red/white | 09:19 |
| toscalix | calors/colors | 09:20 |
| rjek | colours ;-) | 09:20 |
| toscalix | colours | 09:20 |
| pedroalvarez | colors | 09:20 |
| pedroalvarez | artifact | 09:20 |
| pedroalvarez | USA | 09:20 |
| pedroalvarez | o/ | 09:20 |
| toscalix | analize/analise ... and my favorite one: virtualization - virtualisation | 09:21 |
| pedroalvarez | :) | 09:21 |
| rjek | toscalix: analize does not mean what I think you think it means. | 09:21 |
| rjek | artefact only became the more popular spelling in British English in the past ~20 years or so | 09:21 |
| toscalix | pedroalvarez: we don't have such a problem in the Canary Islands, neither in South/central america :-) | 09:21 |
| pedroalvarez | toscalix: ooh, yes we have it | 09:22 |
| toscalix | artifat (english) artefacto (spanish) from the latin arte facto - done with art | 09:23 |
| pedroalvarez | heh | 09:23 |
| pedroalvarez | toscalix: I'll be having a meeting soon, I'll ping you when I'm done | 09:24 |
| toscalix | so the british are becoming more influenced by latin lately..... strange | 09:24 |
| toscalix | and cool at the same time | 09:24 |
| toscalix | ok | 09:24 |
| rjek | artifact and artefact have been used interchangably in English for hundreds of years | 09:25 |
| rjek | But it appears that the British have recently decided that the e-form is more beautiful. | 09:25 |
| toscalix | ah | 09:25 |
| toscalix | nowadays everything is e- | 09:26 |
| toscalix | electronic | 09:26 |
| *** ssam2 has quit IRC | 09:28 | |
| wdutch | taking orchestration down briefly | 09:31 |
| pedroalvarez | wdutch: publish is not being triggered | 09:32 |
| pedroalvarez | wdutch: I guess it's my fault | 09:33 |
| wdutch | it's my fault | 09:33 |
| wdutch | will deal with it hopefully before lunch | 09:33 |
| wdutch | sorry! | 09:33 |
| wdutch | yay arm build | 09:35 |
| pedroalvarez | good! | 09:35 |
| toscalix | this is why we always need to set up a dev and production instances. When the deadline is close..... we block each other | 09:35 |
| wdutch | I tried to set one up but buildbot and nebula didn't get on | 09:36 |
| wdutch | also I have no idea how to set up a trove | 09:36 |
| pedroalvarez | wdutch: I could have helped, 10 minutes of my time | 09:38 |
| wdutch | pedroalvarez: feel free to give it a go if you have time, the problem was when running orchestration buildbot timed out | 09:38 |
| * pedroalvarez is here again | 09:49 | |
| * wdutch wishes chinese addresses would stop trying "GET /manager/html" | 09:49 | |
| pedroalvarez | haha | 09:50 |
| pedroalvarez | you only realise how dangerous is internet when you put something on production | 09:51 |
| pedroalvarez | an public | 09:51 |
| pedroalvarez | and* | 09:51 |
| wdutch | like when we were DoS'd by a russian the other day ... | 09:51 |
| rjek | I wish russian IP addresses would listen to my mail server when it says "AUTH used when not advertised." | 09:51 |
| rjek | But, wooyay fail2ban | 09:51 |
| pedroalvarez | I need to learn how to configure it | 09:52 |
| rjek | It's hateful and surprisingly complex | 09:53 |
| rjek | But it does work | 09:53 |
| pedroalvarez | toscalix: I'm back | 09:53 |
| pedroalvarez | I don't really like how the status bars are right now | 09:53 |
| pdar | It would be good if they only appeared when the builder was active | 09:55 |
| * rjek can't see any progress bars, and feels he is missing out on all the excitement. | 09:56 | |
| pdar | rjek: http://ciat.baserock.org:8888/#/ | 09:56 |
| rjek | MOAR EIGHTS | 09:57 |
| rjek | Ta | 09:57 |
| wdutch | rjek: if you want to see the progress bars don't use a terminal | 09:57 |
| toscalix | pdar: agree | 09:58 |
| pedroalvarez | only if active, ok | 09:58 |
| SotK | +1, also can they lose the 20px margin they have underneath them? :) | 09:59 |
| pedroalvarez | SotK: I can try :) | 09:59 |
| rjek | Or put the text "This space intentionally left blank" there | 09:59 |
| pedroalvarez | SotK: I'd like to solve what happens when you make the screen small | 09:59 |
| SotK | pedroalvarez: what do you mean? | 10:00 |
| SotK | how everything goes vertical? | 10:00 |
| pedroalvarez | goes vertical, but only using the 20% of the screen | 10:00 |
| pedroalvarez | because I'm crap at css | 10:01 |
| SotK | use col-xs-2 rather than col-md-2 on the lane divs | 10:01 |
| pedroalvarez | yay, an expert in tha house | 10:01 |
| wdutch | anybody around who knows ybd? | 10:06 |
| wdutch | I need help with http://ciat.baserock.org:8010/builders/genivi-demo-platform-x86_64%20Deploy/builds/11/steps/shell_1/logs/stdio | 10:06 |
| SotK | cache.get_cache() appears to return False if cachedir doesn't exist | 10:08 |
| rjek | That's a surprising API | 10:08 |
| gtristan | wdutch, I wont claim to 'know' it... but I've just spent a few days arm wrestling with it ;-) ... you have linux-user-chroot I presume ? | 10:09 |
| wdutch | gtristan: there is no linux-user-chroot on the host but it's worked in the past without it | 10:10 |
| gtristan | yeah I see, it should pass without it... I insisted to install it myself | 10:11 |
| gtristan | wdutch, latest stable tag ? | 10:11 |
| wdutch | 15.39 | 10:11 |
| gtristan | hmmm thats what I'm using too... HEAD had problems | 10:12 |
| SotK | wdutch: is "genivi-demo-platform-x86_64-generic.190a24b09d38856cc5cf128b55c25b2d4ae72fa08dcfea85171ad2e9f0c6af1a" in your cache? | 10:12 |
| * wdutch looks | 10:13 | |
| * wdutch twiddles thumbs | 10:14 | |
| wdutch | there is quite a lot of cache | 10:14 |
| wdutch | SotK: it looks like it's not there | 10:16 |
| SotK | hm, are you using a remote cache too at all? | 10:17 |
| wdutch | I have no idea, how would I know?> | 10:17 |
| * SotK has no idea :) | 10:17 | |
| wdutch | pdar: Idon't suppose you have any insight into this problem? | 10:18 |
| pdar | eyeballing | 10:19 |
| pdar | no insight | 10:21 |
| pdar | sorry | 10:21 |
| pdar | can look into it though | 10:21 |
| pedroalvarez | wdutch: maybe the artefact is in there, but ybd can't open it? (permissions) | 10:21 |
| * SotK doesn't see how deployment could be attempted before assembly, so assumes that either something deleted it between assembly finding it and deployment not, or its in a remote cache somewhere so assembly finished fine | 10:21 | |
| pdar | its not in a remote cache i dont think | 10:22 |
| wdutch | pedroalvarez: ybd is being run as root afaik | 10:22 |
| wdutch | yup it's run as rot | 10:22 |
| pedroalvarez | heh, OK | 10:23 |
| wdutch | *root | 10:23 |
| SotK | there is a kbas-url set in your config, is kbas actually running? | 10:24 |
| pdar | it is, I am looking at why it aint working now | 10:24 |
| SotK | is the artifact I mentioned earlier in kbas's cache? | 10:25 |
| pdar | it isnt | 10:25 |
| SotK | o.o | 10:25 |
| pdar | ybd doesnt seem to be talking to kbas | 10:26 |
| *** CTtpollard has joined #baserock | 10:26 | |
| wdutch | pedroalvarez: where is the code for ' curl -X POST -F ... http://127.0.0.1:8080/testing_complete' | 10:27 |
| pedroalvarez | wdutch: in the testing_trigger.sh | 10:28 |
| wdutch | thanks | 10:28 |
| pedroalvarez | or whatever is under the triggers/ folder | 10:28 |
| *** toscalix has quit IRC | 10:31 | |
| pdar | ho hum, when trying to use the same kbas server from my baserock dev machine I get the following: | 10:32 |
| pdar | 15-10-01 00:00:06 [libvorbis] WARNING: remote artifact server is not working | 10:32 |
| *** gtristan has quit IRC | 10:47 | |
| *** gtristan has joined #baserock | 10:52 | |
| * pdar fixes the remote caching problem | 10:57 | |
| wdutch | that's good because this build is 90% done according to the bar! | 10:57 |
| pedroalvarez | wdutch: hahahah | 10:59 |
| pedroalvarez | wdutch: shhh! | 10:59 |
| * wdutch isn't sure what to do while waiting for this build | 11:00 | |
| pedroalvarez | trigger a test, and make it trigger publish | 11:01 |
| wdutch | okay | 11:01 |
| wdutch | huh testing finished an no publish :( | 11:12 |
| pedroalvarez | see!!!!! | 11:13 |
| pedroalvarez | :) | 11:13 |
| pedroalvarez | as I said, probably my fault | 11:13 |
| wdutch | I thought I'd fixed it | 11:13 |
| wdutch | 127.0.0.1 - - [01/Oct/2015 11:11:35] "POST /testing_complete HTTP/1.1" 200 0 | 11:13 |
| *** bwh_ is now known as bwh | 11:13 | |
| wdutch | it's pinging bottlerock c'rectly | 11:13 |
| wdutch | '%s Pulbish' ... | 11:14 |
| * wdutch finds the problem | 11:14 | |
| CTtpollard | heh bottlerock, nice name | 11:14 |
| wdutch | CTtpollard: Thanks! :D although I regret it ... | 11:14 |
| *** ssam2 has joined #baserock | 11:26 | |
| *** ChanServ sets mode: +v ssam2 | 11:26 | |
| wdutch | publish is now being triggered | 11:28 |
| wdutch | phew | 11:28 |
| pedroalvarez | wdutch: thanks!!! | 11:34 |
| pedroalvarez | nicer progress bars now | 11:34 |
| pedroalvarez | http://ciat.baserock.org:8888/#/ | 11:34 |
| wdutch | red? :( | 11:34 |
| * wdutch finds the in progress boxes being red quite distressing | 11:35 | |
| pedroalvarez | orange? | 11:35 |
| wdutch | then it's the same as the bar | 11:35 |
| SotK | wdutch: red means last build failed | 11:35 |
| pedroalvarez | aahh | 11:35 |
| pedroalvarez | indeed | 11:35 |
| pedroalvarez | well, red now means "not success" | 11:35 |
| SotK | pulsing yellow outline means in-progress | 11:36 |
| wdutch | personally I think that's misleading but okay | 11:36 |
| pedroalvarez | I can go with purple for interrupted builds ;) | 11:36 |
| jmacs | I think the pulsing yellow should be accompanied by a low frequency throbbing noise | 11:36 |
| wdutch | +1 | 11:36 |
| SotK | wdutch: why is it misleading? | 11:37 |
| SotK | pedroalvarez: that would be nice | 11:37 |
| pedroalvarez | I think it may be confusing | 11:37 |
| wdutch | SotK: I interpret the box as being the current build | 11:37 |
| tiagogomes | what's provisioning? deploying? | 11:38 |
| pedroalvarez | progress bar is the current build, color of box, previous build | 11:38 |
| SotK | pedroalvarez: yeah, I guess purple doesn't have an obvious meaning like red/green | 11:38 |
| pedroalvarez | tiagogomes: yes, deploying images for the tests | 11:38 |
| pdar | could make a key? | 11:39 |
| pedroalvarez | we could make a key, yes | 11:39 |
| jmacs | Mouseover text, perhaps? | 11:40 |
| pedroalvarez | mouseover is an antipattern :) | 11:40 |
| pedroalvarez | (smartphones can't do that) | 11:40 |
| nowster | I wonder how xkcd looks on a phone... | 11:41 |
| tlsa | pedroalvarez: I'd s/Automatic test/Test/ | 11:41 |
| tiagogomes | pedroalvarez so why not deploying? :) Also why some verbs are on the gerund and others on the infinitive? | 11:42 |
| nowster | sort of works with a long press in Chrome... not at all well in Firefox. | 11:42 |
| nowster | (That's the ALT text on the image) | 11:43 |
| tlsa | And s/C.I.A.T.:/CIAT:/ | 11:44 |
| tiagogomes | Also, the website is making my computer sweat a bit (on firefox) | 11:45 |
| pedroalvarez | tlsa: I'll ponder that change | 11:46 |
| pedroalvarez | tiagogomes: deploying may mean another different thing | 11:47 |
| pedroalvarez | we are not doing "deployments" to anywhere, just generating disk images | 11:47 |
| tiagogomes | you mean you are 'deploying' a tarball or raw image | 11:48 |
| tiagogomes | I don't think 'provision' would be better if that's the case. Deployment is the vocabulary that we use in Baserock, so I think we should stick to it | 11:49 |
| tlsa | pedroalvarez: the trouble with "Automated test" is it wraps in narrow windows, which makes the blocks get missaligned | 11:55 |
| *** zoli__ has quit IRC | 12:04 | |
| *** zoli___ has joined #baserock | 12:04 | |
| * Kinnison notes that if the tests aren't automated, the CIAT system can't run them anyway | 12:25 | |
| Kinnison | so I'm all for 'Test' | 12:25 |
| *** gtristan has quit IRC | 12:32 | |
| *** gtristan has joined #baserock | 12:46 | |
| pedroalvarez | hehe, I guess that "Automated" makes it sound better | 12:47 |
| *** zoli___ has quit IRC | 13:12 | |
| pedroalvarez | oops, I made the status bar flash too | 13:21 |
| SotK | :D | 13:22 |
| *** zoli__ has joined #baserock | 13:22 | |
| pedroalvarez | http://ciat.baserock.org:8888/#/ | 13:23 |
| pedroalvarez | it is of course an error, but it doesn't look bad | 13:23 |
| Kinnison | hmm | 13:23 |
| *** toscalix__ has joined #baserock | 13:26 | |
| * SotK wonders what the intended effect was | 13:27 | |
| rjek | hypnotic nested pulsation | 13:28 |
| *** zoli__ has quit IRC | 14:32 | |
| *** gtristan has quit IRC | 15:02 | |
| pedroalvarez | rjek: I think in 24h the world will be mine | 15:03 |
| rjek | :D | 15:04 |
| wdutch | boo failed build | 15:18 |
| wdutch | looks like my terminal running bottle got eaten | 15:20 |
| *** paulwaters_ has quit IRC | 15:23 | |
| *** edcragg has quit IRC | 15:31 | |
| *** gtristan has joined #baserock | 15:32 | |
| Kinnison | screen | 15:33 |
| Kinnison | screen is your friend | 15:33 |
| wdutch | I forgot | 15:35 |
| myself | set it to your login shell :) | 15:35 |
| rjek | heh | 15:36 |
| myself | http://stackoverflow.com/questions/11068965/how-can-i-make-tmux-be-active-whenever-i-start-a-new-shell-session | 15:36 |
| wdutch | it was messy anyway because I'd restarted bottlerock midflight so as not to interupt that epic build | 15:37 |
| wdutch | ironic in the end | 15:37 |
| Kinnison | heh | 15:37 |
| *** persia has quit IRC | 15:38 | |
| *** persia_ has quit IRC | 15:38 | |
| *** Lachlan1975 has joined #baserock | 15:47 | |
| *** zoli__ has joined #baserock | 15:48 | |
| *** ssam2 has quit IRC | 15:49 | |
| *** zoli__ has quit IRC | 15:50 | |
| wdutch | there's a red thing flashing at me | 15:51 |
| wdutch | it makes me think there's an emergency | 15:51 |
| wdutch | well more pulsing than flashing | 15:52 |
| Kinnison | awooooooga | 15:52 |
| nowster | abandon shop | 16:04 |
| Kinnison | tempting | 16:05 |
| rjek | this is not a daffodil | 16:05 |
| *** zoli__ has joined #baserock | 16:11 | |
| *** zoli__ has quit IRC | 16:12 | |
| *** jonathanmaw has quit IRC | 16:41 | |
| *** mariaderidder has quit IRC | 16:49 | |
| *** persia has joined #baserock | 16:57 | |
| *** zoli__ has joined #baserock | 17:18 | |
| *** zoli__ has quit IRC | 17:23 | |
| *** toscalix__ has quit IRC | 17:30 | |
| *** zoli__ has joined #baserock | 17:35 | |
| *** zoli__ has joined #baserock | 17:44 | |
| *** tiagogomes has quit IRC | 18:05 | |
| *** Lachlan1975 has quit IRC | 18:43 | |
| *** zoli__ has joined #baserock | 19:43 | |
| *** zoli__ has quit IRC | 20:09 | |
| *** paulwaters_ has joined #baserock | 20:23 | |
| *** paulwaters_ has quit IRC | 20:52 | |
| Walkerdine | Does the baserock system on the jetson have access to GPIO? | 21:31 |
| *** jwadas1 has joined #baserock | 21:45 | |
| *** jwadas2 has joined #baserock | 21:48 | |
| *** jwadas1 has quit IRC | 21:52 | |
| *** zoli__ has joined #baserock | 21:56 | |
| myself | gah, of course you'd ask right after I leave where my board is sitting | 22:10 |
| myself | does /sys/class/gpio exist? | 22:11 |
| *** jwadas2 has quit IRC | 22:21 | |
| Walkerdine | It does not | 22:24 |
| Walkerdine | myself: I'm guessing thats a problem | 22:30 |
| myself | Yeah, though I don't have my head around enough of that to confidently give further advice, it looks like that's probably because the kernel needs to be built with support, and then there may be some interaction with a devicetree, but I'm not sure how those pieces fit together | 22:39 |
| Walkerdine | Would you happen to know where I could find out more about how these peice together | 22:42 |
| myself | not off the top of my head, but some better-documented platforms like beaglebone might be instructive, as I think the OMAP folks were pretty heavily involved in devicetree's early days. | 23:47 |
| Walkerdine | You dont think there would be a difference between the dev image and the genivi demo platform do you | 23:50 |
| Walkerdine | In terms of having the GPIO show up | 23:50 |
| Walkerdine | in /sys/class/gpio | 23:50 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!