Nothing_Much | oh darn | 02:24 |
---|---|---|
Nothing_Much | I don't have previous QA work | 02:24 |
Nothing_Much | What should I do about not having previous QA work? | 02:26 |
=== _salem is now known as salem_ | ||
Nothing_Much | What should I do about not having previous QA work? | 03:28 |
Nothing_Much | Pardon my question for the third time, but.. | 03:53 |
Nothing_Much | What should I do about not having previous QA work? | 03:53 |
=== chihchun_afk is now known as chihchun | ||
jibel | good morning | 06:54 |
=== salem_ is now known as _salem | ||
dkessel_ | good morning jibel | 07:15 |
dkessel_ | good morning quality ;) | 07:15 |
elfy | morning all | 07:17 |
jibel | good morning dkessel_ | 07:22 |
pitti | jibel: erk -- http://d-jenkins.ubuntu-ci:8080/view/Utopic/view/AutoPkgTest/job/utopic-adt-setup-testbed/ didn't actually run for two weeks; did the trigger get broken? we do have current cloud images | 07:27 |
* pitti runs it | 07:27 | |
jibel | err, checking | 07:28 |
pitti | jibel: that also explains why dist-upgrade takes so long | 07:29 |
jibel | pitti, the url trigger is broken on d-jenkins | 07:30 |
pitti | jibel: http://d-jenkins.ubuntu-ci:8080/view/Utopic/view/AutoPkgTest/job/utopic-adt-setup-testbed/urltriggerPollLog/? -- does that look goo? | 07:30 |
* pitti starts a build | 07:31 | |
pitti | jibel: should we perhaps switch to daily build then? even if it's an old image that will do the dist-upgrade once instead of per-test | 07:55 |
jibel | pitti, right, if CI doesn't today, I'll change it to daily build. | 08:26 |
jibel | doesn't fix | 08:26 |
jibel | +it | 08:26 |
jibel | pfff typing is hard :) | 08:26 |
=== chihchun is now known as chihchun_afk | ||
=== _salem is now known as salem_ | ||
Nothing_Much | What should I do about not having previous QA work? | 15:01 |
gQuigs | Nothing_Much: what do you want to learn to do? triage bugs? | 15:02 |
Nothing_Much | gQuigs: Test and Triage through a VM | 15:18 |
Nothing_Much | I read through the QATeam wiki | 15:18 |
Nothing_Much | It's just that the "previous QA work" throws me off a little | 15:19 |
gQuigs | Nothing_Much: hmm.. maybe rephrase to - what's your previous experience dealing with bugs? | 15:21 |
gQuigs | or general troubleshooting might fit in there too | 15:22 |
gQuigs | Nothing_Much: any specific applications you want to help triage? | 15:23 |
Nothing_Much | gQuigs: Not yet, I'm still reading on how to use testdrive | 15:24 |
gQuigs | Nothing_Much: you can triage a good number of bugs without testdrive.. starting with finding old untouched bugs and trying to see if they logically are still relevant | 15:28 |
gQuigs | if not, something like this https://wiki.ubuntu.com/Bugs/Responses#Old_untouched_bugs and then set to Incomplete | 15:28 |
gQuigs | ^ would give some good experience with Launchpad | 15:29 |
Nothing_Much | gQuigs: From what I've read, Triaging is basically bugtesting on stable releases, right? | 15:40 |
gQuigs | Nothing_Much: in some ways yes.. confirm the bugs are still present | 15:49 |
gQuigs | but also make sure they have enough info for someone to work on them | 15:49 |
gQuigs | another big part is finding duplicates... oh and pushing upstream... | 15:49 |
gQuigs | but yea, start with bugtesting on stable releases :) | 15:49 |
=== roadmr is now known as roadmr_afk | ||
=== roadmr_afk is now known as roadmr | ||
=== DalekSec_ is now known as DalekSec | ||
=== salem_ is now known as _salem |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!