[17:41] <apw> rtg, smb, in our udeb configuration is there any good reason that we don't have all modules as 'foo ?' we already are checking they don't go away without us noticing in the module-check ... so all it seems to be able to do is inflict pain on us
[17:42] <smb> apw, Never much thought about that
[17:42] <smb> They are just there
[17:42] <manjo> bjf, regarding scale testing ... we should mod the wiki... you want me to go first and update the wiki ? 
[17:42] <apw> yeah ... just trying to get armel-versatile to generate them and finding i need a lot of ?'s adding
[17:43] <apw> and really cannot understand why given we have module loss checks elsewhere what we gain by not just adding ? to them all in all cases thoughout
[17:43] <apw> (for d-i only of course)
[17:43] <manjo> bjf, I will update it with the testing info 1st and you can go with the couch db setup next ? 
[17:43] <smb> apw, Maybe those checks have been there before module checks and then stayed
[17:44] <bjf> manjo, I'm really not all that hung up on the wiki for the testing as that seems to be mostly focused on how to setup the environment for us and not pointed at users
[17:44] <apw> smb, yeah i am thinking that is likely the case
[17:44] <manjo> apw, thanks I keep forgetting 
[17:44] <bjf> manjo, though it needs to be documented, it can come later
[17:44] <manjo> bjf, needs to happen before scale so that we can have a laptop setup with the wiki for people to follow
[17:44] <manjo> anyone have any thoughts on this ? 
[17:45] <bjf> manjo, I have a laptop with it all setup
[17:45] <apw> manjo, depends if 'we' are going to be there and taking it with us?  in that case just the user instructions seem needed
[17:45] <manjo> bjf, ok I will update the wiki then... and then test the netbooks I have here... if you could update the couch DB info that will be great
[17:45] <bjf> manjo, don't let me hold you back from documenting it, it's just not my highest priority
[17:48] <manjo> bjf, the tests seem to be fine when i ran it yesterday, I am just curious about the results transfer, I have not tried that, if it works for you and JFo then I am not that worried, althjough I would like to test that as well 
[17:48] <JFo> I haven't looked at results transfer
[17:48] <JFo> just making sure the images and tests work
[17:49] <manjo> I just unboxed 3 netbooks and a fitpc2 and I would like to use those to do the testing etc 
[17:50] <bjf> manjo, I can walk you through the transfer if it doesn't "just work"
[17:51] <manjo> ok
[17:54] <bjf> JFo, I was thinking about these bugs that we try to close and then someone just reopens them
[17:54] <bjf> JFo, is it possible to mark them as "private"
[17:55] <JFo> hmmmm, that is both a good question and an idea
[17:55] <JFo> let me think upon it for a bit
[18:44] <manjo> JFo, bjf, I get "There was an error creating the child process from terminal" 
[18:45] <JFo> you need to chmod +x the tests_starter script
[18:45] <JFo> I got that earlier
[18:45] <bjf> manjo, are you testing with one partition or with two?
[18:45] <manjo> tow
[18:45] <manjo> two
[18:45] <manjo> so on the 2nd partition I put kernel-qa
[18:46] <bjf> when you copied the kernel-qa tree onto the second partition did you get all the permissions and ownerships right?
[18:46] <manjo> hmmmm I thinkI did let me check again 
[18:47] <bjf> this usually means that, as JFo mentioned, the kernel-qa/tests_starter script is not executable
[18:47] <manjo> checking now 
[18:48] <manjo> I think I forgot to chmod test_starter... 
[18:49] <manjo> let me try booting this one 
[18:49] <manjo> I just changed it 
[18:52] <bjf> manjo, did you look at the list of packages that I am uninstalling? I pasted it yesterday in #scale
[18:52] <manjo> bjf, yes
[18:52] <manjo> bjf, I get the same error 
[18:53] <bjf> manjo, then from a terminal window, run the "tests_first_stage" by hand and see what it complains about
[18:54] <manjo> looks like I don't have perms to /ukt 
[18:55] <bjf> I don't understand why you are the only one that runs into that problem
[18:57] <manjo> when I run test_first_stage I get "lnL creating symbolic link ... " files exists
[18:57] <manjo> then opens a window
[18:57] <manjo> and I get that error 
[18:57] <bjf> manjo, yesterday you were going to fix the "tests_first_stage" script if it needed to set permissions and then send it to me, I didn't get anything from you 
[18:59] <manjo> I know what the problem is 
[18:59] <bjf> manjo, what is it?
[18:59] <manjo> 1. permission missing for /ukt 2nd test_starter under kernel-qa is not executable
[19:00] <manjo> I will send you patch for missing perms 
[19:00] <manjo> or you can quickly add it to the script 
[19:00] <JFo> bjf, the only badness I see about making a bug like the ones mentioned above private would be the duplicates that would be created by the same people who keep reopening the bugs.
[19:00] <manjo> chmod +rwx /ukt 
[19:00] <bjf> manjo, I'd still like to know why only you have this issue
[19:08] <bjf> manjo, when the script makes the /ukt mount point on my system it has the correct permissions. i don't understand why yours doesn't
[19:09] <JFo> same here
[19:23] <manjo> bjf, impressive :)
[19:23] <bjf> manjo, what is?
[19:23] <manjo> bjf, I just ran the tests on the HP mini and  they passed
[19:24] <manjo> bjf, you need to pick up the new version of kernel-qa and I will send you a patch for change in perms
[19:24] <bjf> manjo, what changed with kernel-qa
[19:25] <bjf> manjo, why when I or JFo create the ukt directory in / is it created with the correct permissions and yours not?
[20:14] <bjf> manjo, I'd like to get the tests_first_stage that you've modified and that works for you
[20:19] <manjo> bjf, yes I can't find my USB stick... do you have a copy of that file you can mail it ot me ? 
[20:22] <bjf> if [ ! -e "/ukt" ]; then
[20:22] <bjf>     sudo mkdir /ukt
[20:22] <bjf>     sudo chmod +rwx /ukt
[20:22] <bjf> fi
[20:22] <manjo> bjf, looks like its not in the git tree either so its a file private to you 
[20:22] <manjo> yep
[20:22] <manjo> that works
[20:41] <pgraner> bjf, manjo: you can save a 2x commands by doing: sudo mkdir -m 755 /ukt
[20:42] <bjf> pgraner, ack
[20:45]  * manjo thinks pgraner is *amazing*... 
[20:46]  * manjo says or that is what csurbi would have said
[20:46] <manjo> pgraner, do we have a switch in the box that you gave JFo to ship ? 
[20:47] <manjo> bjf, JFo, pgraner we will also need some network cables
[20:47] <JFo> manjo, I am way ahead of you
[20:47] <bjf> manjo, since the box went out yesterday it's a little late to think of that
[20:48] <bjf> manjo, however, JFo, did think of it and has taken care of it
[20:48] <manjo> JFo, you the man
[20:48] <JFo> I know :)
[20:48]  * manjo puffs on 98 connecticut shade 
[20:51] <manjo> bjf, are you rolling the final image today ? 
[20:51] <manjo> with all the latest changes ? 
[20:51] <bjf> manjo, yes, it was already rolled until your perms change
[20:52] <bjf> manjo, I'm uploading it now
[20:52] <manjo> and the modified kernal-qa ? 
[20:52] <bjf> yes, and the modified kernel-qa
[20:52] <manjo> I checked in a small change this morning 
[20:52] <manjo> cool
[20:53] <manjo> let me know when the upload is done I will suck it down and test it on all 4 netbooks here 
[20:53] <manjo> bjf, ^
[20:53] <bjf> manjo,ack
[20:54] <manjo> bjf, JFo I think we will put on a great show ... 
[20:54] <manjo> JFo, are you going to populate the usb sticks ? 
[20:54] <JFo> done
[20:54] <manjo> ?
[20:54] <JFo> already done, but I have to redo them due to this new change
[20:54] <manjo> ah
[20:56] <manjo> bjf, oops dude I just realized something wrong 
[20:56] <manjo> have you rolled the image already ? 
[20:56] <JFo> he is uploading
[20:56] <bjf> manjo, make it quick
[20:56] <manjo> I was looking at the results and we are missing one thing 
[20:57]  * JFo chokes manjo for bjf ;)
[20:57] <JFo> heh
[20:57] <bjf> please spell it out for me
[20:57] <manjo> we need to collect dmesg after we are done running the tests 
[20:57] <manjo> we collect it before 
[20:57] <manjo> and we also need to collect log files after 
[20:58] <manjo> bjf, give me 10mts I will push that change through
[20:58] <manjo> bjf, do you agree ? 
[20:59] <bjf> manjo, do it, and test it, and let me know when it's ready
[20:59] <manjo> bjf, ack... sorry ..it will be really bad if we did not collect that info
[21:11] <manjo> bjf, I am collecting dmesg after suspend resume, video tests, what other tets do you think we should collect?
[21:12] <bjf> manjo, i'm fine with those
[21:12] <manjo> ok
[21:12] <manjo> then I will test it and push it in the next 20mts 
[21:19] <bjf> manjo, i've got to run to the store, wife is sick, will be back in a bit (30 min. max)
[21:47] <bjf> manjo, I'm back are your changes ready?
[21:52] <bjf> manjo, I need to crank that iso out, are your changes ready?
[21:53] <manjo> yep pushing now 
[21:54] <manjo> bjf, done 
[21:54] <manjo> I tested it as well on my 10v
[21:54] <manjo> phew!
[21:54] <manjo> that would have been baaaad 
[21:55] <manjo> so we are collecting dmesg 1. after the system boots, 2. after suspend/resume, video, graphics tests 3. after all the tests are run
[21:56] <manjo> we are collecing system logs before & after all the tests are run
[21:56] <manjo> XXX.log.before xxx.log.after 
[21:56] <manjo> bjf, ^ 
[21:56] <manjo> JFo, ^
[21:56] <bjf> manjo, ack
[21:56] <manjo> coo
[21:56] <manjo> l
[21:57] <JFo> ok
[21:57] <manjo> JFo, bjf, please review my changes as well
[21:57] <JFo> where are we collecting them to?
[21:57] <manjo> JFo, to results/qa-logs & results/ubuntu-logs/ 
[21:58] <JFo> ok, and how do we separate these results out by individual machine?
[21:58] <JFo> are we going to need to copy them off each time?
[21:58] <JFo> or will that be automatic?
[21:58] <manjo> in qa-log after each test in suspend/resume, video, graphics is exed you will see $TEST.dmesg
[21:58] <JFo> right
[21:58] <manjo> JFo, dmidecode will give us that 
[21:58] <JFo> but say 5 people use a USB key
[21:59] <manjo> JFo, dmidecode will have system info
[21:59] <bjf> JFo, it's covered, each run goes into a different directory
[21:59] <JFo> bjf, cool
[21:59] <manjo> yep and its by uuid
[21:59] <JFo> that was what I was needing
[21:59] <manjo> so its uniq
[22:00]  * manjo pleads someone to say I am good :)
[22:03] <manjo> bjf, I am going to work on the wiki now 
[22:14] <bjf> manjo, JFo, uploading new iso
[22:14] <manjo> bjf, ack going to zinc ? please post the link
[22:24] <bjf> manjo, it's there, same place as all the others
[22:24] <manjo> called the same ? 
[22:24] <bjf> yup
[22:24] <manjo> ok thanks 
[22:37] <JFo> pulling the ISO now
[23:00] <manjo> JFo, my link is damn slow so taking a a while 
[23:03] <manjo> JFo, https://wiki.ubuntu.com/KernelTeam/KernelCompatibilityTesting updated the wiki 
[23:03] <JFo> cool
[23:03] <manjo> pgraner, ^
[23:17] <pgraner> manjo: I added a table of contents
[23:17] <pgraner> manjo: the only thing I see missing is where to get the image?
[23:21] <manjo> pgraner, right, bjf is doing the image 
[23:21] <manjo> and he will add the part on couchdb etc 
[23:22] <manjo> pgraner, I added info on testsuite & pxe boot 
[23:22] <pgraner> manjo: cool
[23:24] <manjo> pgraner, not sure if you were around, we are collecting dmesg after some of the key tests like suspend/resume, video capture, graphics tests, and also complete log files before & after all tests 
[23:24] <manjo> and also we collect apport data when tests fail 
[23:26] <pgraner> manjo: cool
[23:57] <crimsun> manjo: are there plans to roll in the newer compat-wireless or linux-alsa-driver-modules for those test images?
[23:58] <crimsun> manjo: i.e., if any of the sound tests fail, unload ^snd* and load the newer l-a-d-m ones, and offer to retest