From trac at buildbot.net Sat Feb 1 03:53:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 03:53:46 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: NathanBlack
Message-ID: <20140201035346.374AE11FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user NathanBlack
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 10:12:55 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 10:12:55 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: roniblake110
Message-ID: <20140201101255.14EF211FA41@buildbot-trac.community.scl3.mozilla.com>
New user registration for user roniblake110
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 10:17:51 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 10:17:51 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: HaroldKn
Message-ID: <20140201101751.78EF911FA41@buildbot-trac.community.scl3.mozilla.com>
New user registration for user HaroldKn
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 10:26:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 10:26:46 -0000
Subject: [Buildbot-commits] [Buildbot] #2686: Skin Bost
Message-ID: <044.d7836a5b4f4e65889c21382c8ee07177@buildbot.net>
#2686: Skin Bost
-------------------------+-----------------------
Reporter: roniblake110 | Owner:
Type: task | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.8 | Keywords: a
-------------------------+-----------------------
some of them are I mentioned my I'm getting ready for bed video that I did
a while back and that this was going to be more Alike talking stereo can't
do [https://www.apsense.com/article/natural-way-to-remove-your-wrinkles-
in-minutes.html AuraVie] you mean SEM my reviews and some other products
that first thing I do is take classes my face and eye makeup and way used
to take it off is my times calls cream a class act actually doesn't have
the wine and a smaller container which is that DA Way Caddo facial scrub
traded.
I have the video in the Description box below but say is that every other
day a out any and classic really don?t affairs guess he can even use it
every day if you want but sassed ironies this month first I'm eighty
favorite you have favorite cities for myself and obviously the once I get
the entire and fight hackers as well but and .
https://www.apsense.com/article/natural-way-to-remove-your-wrinkles-in-
minutes.html
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 11:38:02 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 11:38:02 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: nenaking21
Message-ID: <20140201113802.7979111FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user nenaking21
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 14:35:11 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 14:35:11 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: adamrose110
Message-ID: <20140201143511.08A9611FA41@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user adamrose110
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 14:35:42 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 14:35:42 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: allona
Message-ID: <20140201143542.D24EA11F935@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user allona
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 14:35:45 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 14:35:45 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: nenaking21
Message-ID: <20140201143545.94A2411FC0B@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user nenaking21
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 14:35:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 14:35:48 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: roniblake110
Message-ID: <20140201143548.166EA12048C@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user roniblake110
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 1 22:15:57 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 01 Feb 2014 22:15:57 -0000
Subject: [Buildbot-commits] [Buildbot] #2687: Access ENV variables from
factory steps
Message-ID: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
#2687: Access ENV variables from factory steps
------------------------+-------------------------------
Reporter: NathanBlack | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords: ShellCommand, env
------------------------+-------------------------------
It would be nice to be able to use environment variables from build slaves
in ShellCommands.
For example if I needed to use an absolute path to the repository, I could
use $PDW (or something similar) to get the proper location.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 01:45:59 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 01:45:59 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Robertlina
Message-ID: <20140202014559.15F5E11FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Robertlina
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 03:01:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 03:01:48 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: LeonardGada
Message-ID: <20140202030148.7784B11F935@buildbot-trac.community.scl3.mozilla.com>
New user registration for user LeonardGada
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 04:02:54 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 04:02:54 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration:
Stoolvetiplivygex
Message-ID: <20140202040254.E123411FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Stoolvetiplivygex
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 06:20:21 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 06:20:21 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: StiklerVesk
Message-ID: <20140202062021.AE7F011F935@buildbot-trac.community.scl3.mozilla.com>
New user registration for user StiklerVesk
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 11:47:24 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 11:47:24 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Cviagraus
Message-ID: <20140202114724.7CFF911FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Cviagraus
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 13:16:58 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 13:16:58 -0000
Subject: [Buildbot-commits] [Buildbot] #2687: Access ENV variables from
factory steps
In-Reply-To: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
References: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
Message-ID: <058.1ee0207e8d88d2b9766779426dc51fc9@buildbot.net>
#2687: Access ENV variables from factory steps
---------------------------+--------------------
Reporter: NathanBlack | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: sprint, simple |
---------------------------+--------------------
Changes (by dustin):
* keywords: ShellCommand, env => sprint, simple
* milestone: undecided => 0.8.+
Comment:
This would be something to add to the Interpolate class, e.g.
{{{Interpolate("...%(env:PWD)s...")}}}. The slave environment variables
are already available on the master.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 15:55:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 15:55:41 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Annaxukm
Message-ID: <20140202155541.8F9D211F8AD@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Annaxukm
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 16:58:12 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 16:58:12 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: CharlesVash
Message-ID: <20140202165812.8D30A11FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user CharlesVash
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 2 19:24:05 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 02 Feb 2014 19:24:05 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Andomlivfbak
Message-ID: <20140202192405.4373011F8AD@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Andomlivfbak
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 3 05:27:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 03 Feb 2014 05:27:41 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Annagksw
Message-ID: <20140203052741.9482111FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Annagksw
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 3 08:15:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 03 Feb 2014 08:15:41 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Adriansinc
Message-ID: <20140203081541.6390411F8AD@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Adriansinc
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 3 14:23:22 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 03 Feb 2014 14:23:22 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: AnderMn
Message-ID: <20140203142322.91FDA11FBB2@buildbot-trac.community.scl3.mozilla.com>
New user registration for user AnderMn
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 00:34:56 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 00:34:56 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Annackhq
Message-ID: <20140204003456.C07C311F8AD@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Annackhq
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 02:09:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 02:09:41 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: benkep
Message-ID: <20140204020941.7DA8A11F87E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user benkep
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 08:03:56 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 08:03:56 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: erinbyers
Message-ID: <20140204080356.C7DAE11F8AD@buildbot-trac.community.scl3.mozilla.com>
New user registration for user erinbyers
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 08:08:23 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 08:08:23 -0000
Subject: [Buildbot-commits] [Buildbot] #2688: Caution Because of to its
great subject matter of omega-6 polyunsaturated fatty acids,
substantial usage of sunflower oil is probably to induce breast and prostate
cancer in publish-menopausal ladies.
Message-ID: <041.e213f90746f43bed17090993fa09b1de@buildbot.net>
#2688: Caution Because of to its great subject matter of omega-6 polyunsaturated
fatty acids, substantial usage of sunflower oil is probably to induce
breast and prostate cancer in publish-menopausal ladies.
----------------------+----------------------------
Reporter: erinbyers | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords: ELITE TEST 360
----------------------+----------------------------
There are two prevailing errors that a lot of folks represent when they go
to a successfulness matter browse and say gross upbeat supplements.
Initially, they ordinarily adapt on the enumerate toll of the production.
This is often thought of to be a monumental fault. Individuals feature to
refer that today, writer inexpensive doesn't automatically demand shining.
High products and solutions get solon quantify and resources to learn, so
they often value many. And our health and individuals of our households
ought to not bang a commerce damage tag on it. ELITE TEST 360
2nd, they look and reason at the quantities. I change regarded
plentifulness and abundance of men and women that determine two product
equal this. For instance, they deciding up a bottle of vitamins that
signifies 500mg of Vitamin C. The else bottle says exclusive 250mg of
Vitamin C. They immediately reckon that the previous is greater. Your full
body is not achievement to ask in all these added milligrams anyway. A
person bushel I would propose to you is to cautiously read through the
labels. And carry in psyche what I swordlike out a tho' in the foregone
full of these solon substances, or arise untold much inexpensive than
regular, block it.
Consume and Drink Rehab for guys
Secluded treatment rehab direction is been voted as unsurpassable
preferred and most undefeated by hundreds and thousands of men and women
crossways the nations. It is instead a new phenomenon in the playscript of
exploit from drug and alcohol. Guys opting for reclusive take rehab must
piss trusty that they tally to achieve a very sound harmony among rehab
stay and region unremarkable history. In another line the stats display
that the residential cloistered drug rehab has been shack in the
confection for weeks or months, possibilities of gaining rid of the
scornful dependency present be kinda borderline, kinda pursuing to near
zip.
When an particular visits the consultant for identify of hrs in a day and
then goes out to go to workplace and friends and ancestry, it is pretty
lyrate for him to succumb to the avaritia substantiate again address or
anywhere as there is no an somebody to interfere and forestall him.
Inpatient document has to be opted if you are intending for whole
retrieval. The perversion and body can exclusive constraint craving for
the thought if it is continually monitored and thermostated. When an nut
is near cypher value, he module act off snorting by falsely auspicious
himself that he won`t do the monovular
Welfare and condition Advantages Of Sunflower Oil ELITE TEST 360
Do you like to indulge in very hot fried pakodas, but hump been
recommended by your physician not to eat dirty personalty, surrendered
that of your diminishing comfortably being? Oil has oftentimes been linked
to undesirable wellbeing and suitability conditions. Matter products
processed implementing larger quantities of oil are typically strictly
prevented. This is mainly because oils are prosperous in concentrated and
trans fats, which are unsafe for our whole embody, preeminent to
incalculable required upbeat conditions. Having said that, this variety of
is not the someone with helianthus oil. Did you jazz that sunflower oil is
amongst the oils that pass in improving upon the boilersuit eudaemonia of
an idiosyncratic, instead than spoilage it? Sunflower oil gives an
congruent changelessness of monounsaturated and polyunsaturated
superfatted acids, making it the assign oil to inferior professionals. The
rewards of sunflower oil are a company of and are especially channeled via
its health and fitness-enhancing matter contents. Speak even more to label
out virtually the nutritional damage of sunflower oil and its voltage
upbeat and suitability gains. Nutritional Price Of Flower Oil Amount of
Sunflower Oil: one cup Unconditioned Coefficient of Flower Oil: 218 g
Nutrients Amount Calories Unconditional Calories 1927 Calories From
Humoring fat 1927 Fats & Suety Acids Accomplished Unit 218 g Pure Metric
19.6 g Monounsaturated Inordinateness fat 125 g Polyunsaturated Extra fat
63.one g Unmitigated Trans Buttery Acids.5 g Total.septet mg Come Omega-6
Buttery Acids 63056 mg Vitamins Vitamin E (Alpha Antioxidant) 89.5 mg
Vitamin K 11.eight mcg Choline.four mg Minerals Press.one mg Nutrition
Features Of Sunflower OilSunflower oil functions as an antioxidant
considering the fact that it is opulent in Vitamin E. This dimension of
flower oil aids in neutralizing cancer-creating autonomous radicals.
Vitamin E in flower oil also prevents rheumatoid arthritis, asthma and
metropolis somebody.The Vitamin E flowing in flower oil also functions as
a moisturizer which assists the group cells to continue irrigate within
retributory them. This abode would form sunflower oil reclaimable in many
decorative products and solutions as effectively.Flower oil, due to its
extraordinary levels of oleic dot and very low concentrated undue fat, is
deemed and judicious for cardiovascular consumption drawing with lower
amount of soppy discarded fat substituted with sunflower oil has proven
sterol change features. The penalise firmness amongst polyunsaturated and
monounsaturated fatty acids in helianthus oil lowers the cholesterol
amounts in a man or spouse.Sunflower oil also assists the wound to sustain
its moisture. It aids in providing a protective roadblock, resisting any
sort of contagion in pre-expression infants. Reports soul demonstrated
that infants feat day by day rind direction working with helianthus oil
are significantly fewer presumptive to expose any rind affined
infections.Helianthus oil is affluent in particularised phytochemicals
this good of as choline and phenolic elvis, which are salutary courage.
There are polyunsaturated and monounsaturated fats existing in flower oil,
along with nutritional vitamins, which helps play and better for a human
period of period of instant. The oil can be put to use in uttermost
considerable preparation temperatures. Helianthus oil is currently
existence utilised by the foods suppliers for reaction the level of trans-
extra fat in swell production of meals.
[http://tryelitetest360.com/]
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 08:10:10 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 08:10:10 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: erinbyers
Message-ID: <20140204081010.4270711F8AD@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user erinbyers
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 16:18:58 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 16:18:58 -0000
Subject: [Buildbot-commits] [Buildbot] #2687: Access ENV variables from
factory steps
In-Reply-To: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
References: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
Message-ID: <058.5eda28c10561fae2e06f43ca4d82762c@buildbot.net>
#2687: Access ENV variables from factory steps
---------------------------+--------------------
Reporter: NathanBlack | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: sprint, simple |
---------------------------+--------------------
Comment (by NathanBlack):
Actually since the variables are platform dependent, it might be better
(for my purposes) if there was just an Interpolate option that gave me the
absolute path to the buildslave source directory. (or should that be a
separate feature request)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 4 19:22:58 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 04 Feb 2014 19:22:58 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: ArendaFade
Message-ID: <20140204192258.9C3F511FAD4@buildbot-trac.community.scl3.mozilla.com>
New user registration for user ArendaFade
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 5 00:23:20 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 05 Feb 2014 00:23:20 -0000
Subject: [Buildbot-commits] [Buildbot] #2687: Access ENV variables from
factory steps
In-Reply-To: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
References: <043.af0544e829db36d27a7e27d56c1742f0@buildbot.net>
Message-ID: <058.c59218c4ac656dee7e3c400087973dbe@buildbot.net>
#2687: Access ENV variables from factory steps
---------------------------+--------------------
Reporter: NathanBlack | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: sprint, simple |
---------------------------+--------------------
Comment (by NathanBlack):
Ah, figured that out, `Interpolate("%(prop:builddir)s/path/to/project")`
does what I need.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 5 07:20:05 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 05 Feb 2014 07:20:05 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: ERtagreemn
Message-ID: <20140205072005.057D411F87E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user ERtagreemn
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 5 20:08:09 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 05 Feb 2014 20:08:09 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: AndreaRek
Message-ID: <20140205200809.0BB9E11F888@buildbot-trac.community.scl3.mozilla.com>
New user registration for user AndreaRek
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 5 22:29:24 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 05 Feb 2014 22:29:24 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Josephet
Message-ID: <20140205222924.8F58311F87E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Josephet
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 6 10:42:19 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 06 Feb 2014 10:42:19 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: ThomasJuh
Message-ID: <20140206104219.5988A11F888@buildbot-trac.community.scl3.mozilla.com>
New user registration for user ThomasJuh
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 6 12:50:53 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 06 Feb 2014 12:50:53 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: triatoth
Message-ID: <20140206125053.C17EE11F87E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user triatoth
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 6 14:58:11 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 06 Feb 2014 14:58:11 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: setruwub
Message-ID: <20140206145811.2D32711F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user setruwub
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 6 20:09:51 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 06 Feb 2014 20:09:51 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: NataliNect
Message-ID: <20140206200951.5FE2611F87E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user NataliNect
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 7 10:09:54 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 07 Feb 2014 10:09:54 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: maryfox
Message-ID: <20140207100954.B83BA11F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user maryfox
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 7 10:34:16 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 07 Feb 2014 10:34:16 -0000
Subject: [Buildbot-commits] [Buildbot] #2689: Make Your Body Stronge
Message-ID: <039.5b70cb7810e1030a925a0c3620166984@buildbot.net>
#2689: Make Your Body Stronge
--------------------+-----------------------
Reporter: maryfox | Owner:
Type: task | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords:
--------------------+-----------------------
They all took different roads to get there did of all the same plant which
is very interesting I think but then I think everybody?s probably
wondering so why is it then it that's common knowledge that not everybody
has access to that end the truth is this the truth is that finding
somebody that qualified first for formal to tailor the nutrition you
called I mean this afternoon the app here today it's not you that is
disqualified they can actually Taylor nutrition plan see you in your goal
that's one thing but the second thing.
It?s the face if not affordable portable right now I helpful I?ve been
doing it for years and this is the first time I went that route so it's
absolutely I think [http://www.maletestosteronebooster.org/ ANDROMALE]
that if I why the subject of there and let people know over it when I?m
weird anything new or groundbreaking here will be from saying that
customized solution of me is the best route to go what despite people
knowing that such a big got nobody using a personalized the individual
items I now know you got to go.
I got what favored of what's up before you go back in the next1i work in
your the home don't know you've been working on an Outspent a lot on her
own time allotted your own apt for and money developing a solution to
close the gap between what the pros know and to what our viewers a home
don?t know and Dob if you got some time to think we can hold of one more
for the weekend over and I to pick your brain on that yeah man for sure a
minute.
http://www.maletestosteronebooster.org/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 7 12:32:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 07 Feb 2014 12:32:41 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: robbyroni
Message-ID: <20140207123241.3E73511F87E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user robbyroni
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 7 13:12:24 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 07 Feb 2014 13:12:24 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: adamadam55555
Message-ID: <20140207131224.D3ED411F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user adamadam55555
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 01:17:31 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 01:17:31 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: AlexanderZQ
Message-ID: <20140208011731.E859811FAF1@buildbot-trac.community.scl3.mozilla.com>
New user registration for user AlexanderZQ
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 04:27:36 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 04:27:36 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Anuutikglamou
Message-ID: <20140208042736.2D06911F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Anuutikglamou
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 08:32:23 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 08:32:23 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: edwardedward
Message-ID: <20140208083223.63A2111FAF1@buildbot-trac.community.scl3.mozilla.com>
New user registration for user edwardedward
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 08:34:40 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 08:34:40 -0000
Subject: [Buildbot-commits] [Buildbot] #2690: weight loss activities 98
Message-ID: <044.ef895b3b939e19106c4d4b46b232f581@buildbot.net>
#2690: weight loss activities 98
-------------------------+-----------------------
Reporter: edwardedward | Owner:
Type: task | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.8 | Keywords: GARCINIUM
-------------------------+-----------------------
we do you have planned isn?t awesome ok up to the bridge to nowhere and it
seems to get to that bridge you jump off for you have planned isn't
awesome dugout to the bridge [http://garciniumpuregarcinia.com/ GARCINIUM]
to nowhere and it's easy to get to the bridge we'regonna jump off 32 I'm
serious I want to come up with another milestone that's meaningful for her
to take that proverbial read the fake its going to challenger but at the
sometime it will have a deeper emotional impact than anything your men
bungee-jumping before I've never done anything like that from this bridge
is no joke the bridges 40stories high get several hundred foot drop time
to take the lead I'm outlets see that the scale says the last time a
slight me to 189 pounds again the phase 1 yes and I gave you the goal
since 55 pounds and the last three months for phase two at this scale says
234 pounds or less that your goal from her before yeah me the sale on me
you racially did you go it 239 the last fifty pounds he didn't lose 55 the
last 50 when I first started this thing I kept telling myself I'm not
going to miss any golf home inside not bad feelings but then again I have
been there don?t know now what to do I come and learn from it and I'm
going to go on to the next phase economic chilling it was easy for you
found a positive and stay in 239 I started at 369 as a 130 k ohms and sex
life that is on believe long the good news is it the weight limit make the
jump is 250pounds you can still do it I will leave it up to you only do it
cut years that's what I want we got to have been a jump to make RF at the
trail you get nervous for dinner a period still good job rating my heart
like town and not breathing test yeah girl when I saw that Fred?s
immediately hours overwhelmed with fear got Wow see I everything first
today freeway I was absolutely scared to death because am about to jump
off bridge like it was no joke okay triggered a yeah both you and when it
actually came time to do it and I think imp and I sent an email to do this
Kelly birthday cut when you see the way limits you don?t ever heard and on
anything shares nothing to break up yeah and I?m like for OK'd scorcher
going to snap day but yet here I am internet my mind together factored
good old yeah I don't even know about watt you're not going straight
towards the ground and never quite camp and backup and I?m keep looking at
it was just a mess amazing feeling by you uniform six months ago there's
no way just for the day and an option for me because today job their
weight limits certain things and I exceeded those weight limit yeah
freaking amazing I from savvy
http://garciniumpuregarcinia.com/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 10:00:00 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 10:00:00 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: lenaadam110
Message-ID: <20140208100000.3E7CB11F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user lenaadam110
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 10:01:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 10:01:46 -0000
Subject: [Buildbot-commits] [Buildbot] #2691: Weight Loss Good
Message-ID: <043.aac6e93a07aa965300abd11bc5dcb588@buildbot.net>
#2691: Weight Loss Good
------------------------+------------------------
Reporter: lenaadam110 | Owner:
Type: task | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.8 | Keywords: cleanse fx
------------------------+------------------------
I encourage you to try hold the different fruits better out there
vegetables really should be ball love your diet and whether you eat meat
or not every single person on the planet myself included would benefit
fromeating more vegetables the bottom line is that our bodies are internal
organs need a certain amount of nutrients just in order to function
[http://cleansefxcanadanow.com/ Cleanse Fx]properly and vegetables are one
of them fast ways to make sure that you?re getting those nutrients they're
loaded with fiber day loaded with vitamins and again if you are not eating
enough vegetables you?re never really get a feel satisfied and fall this
is because your body.
[[Image(http://marketersmedia.com/wp-content/uploads/2013/07/weigt-
loss-5-womn-400-x-2001.jpg)]]
just isn?t getting the nutrition that heat so if you have been easy and I
haveprocessed foods and you're somebody who feels like you?re always
hungry feels like you're never satisfied then the lack vegetables
nutrients and fiber in your diet is probably the reason for that and you
were eating nutrient-rich foods like vegetables we don't have to worry so
much about counting calories because suddenly you're going to get so much
nutrition and fiber with these foods that you're going to fill up and feel
full and satisfied before you'll be able to CP too many calories at those
speeds again this is a topic that I've discussed in several videos that
empty calories verses nutrient-rich calories and I think that really is
the secret toot being on a diet and to not gaining weight back is
recognizing that we just take the empty calories out a large Diet we don't
even have to worry about counting calories at all so.
vegetables there's sweet potatoes eats spinach past swisschard kale there
are a whole green ball hole vegetables for you to try as explained in
previous videos the white refined flour that's used in white bread pasta
and tortillas is completely stripped all of its fiber its nutrients and
this refined white flour is Paul love empty calories this means those
calories turned straight into fat without giving your body in New in
nutrition it also means that this white bread and white flour products are
going to significantly spike your blood sugar basically it's like having
here we find sugar every time you have he's white flour products so.
http://cleansefxcanadanow.com/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 10:08:26 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 10:08:26 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: lenaadam110
Message-ID: <20140208100826.CB35411FAF1@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user lenaadam110
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 10:08:26 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 10:08:26 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: edwardedward
Message-ID: <20140208100826.9D33111F7FC@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user edwardedward
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 13:27:52 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 13:27:52 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: johnkaven
Message-ID: <20140208132752.BE3C611FAF1@buildbot-trac.community.scl3.mozilla.com>
New user registration for user johnkaven
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 13:38:06 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 13:38:06 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: johnkaven
Message-ID: <20140208133806.6686E11FAF1@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user johnkaven
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:06:16 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:06:16 -0000
Subject: [Buildbot-commits] [Buildbot] #2218: Add support for
declarative configuration.
In-Reply-To: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net>
References: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net>
Message-ID: <057.5c33e68fab678cc2682cc65d0528f439@buildbot.net>
#2218: Add support for declarative configuration.
-----------------------------+--------------------
Reporter: tom.prince | Owner:
Type: enhancement | Status: new
Priority: patches-accepted | Milestone: 1.0.+
Version: 0.8.5 | Resolution:
Keywords: config |
-----------------------------+--------------------
Changes (by dustin):
* priority: major => patches-accepted
* type: project-idea => enhancement
Comment:
I'm moving this out of Project-Ideas, because I don't think it makes a
great GSoC project -- too much design and room for bikeshedding. It's
still a good idea, though, and if it becomes much more explicit -- design
complete, with just the implementation to finish -- then it would make a
good GSoC project.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:07:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:07:46 -0000
Subject: [Buildbot-commits] [Buildbot] #2435: Complete Master-Side
Source Steps
In-Reply-To: <038.1f77a78260a6d174ad3e1563a68aa529@buildbot.net>
References: <038.1f77a78260a6d174ad3e1563a68aa529@buildbot.net>
Message-ID: <053.29059662360cabe0e4391cc63e39e797@buildbot.net>
#2435: Complete Master-Side Source Steps
-------------------------+---------------------
Reporter: dustin | Owner:
Type: project-idea | Status: closed
Priority: major | Milestone: 0.8.+
Version: 0.8.7p1 | Resolution: fixed
Keywords: |
-------------------------+---------------------
Changes (by dustin):
* status: new => closed
* resolution: => fixed
Old description:
> GSoC 2011 included a project to add master-side source steps. These are
> a new implementation of steps that have historically housed their logic
> in the slave's code, putting that logic in the master instead. There
> were a few key pieces of functionality omitted from the new master-side
> source steps, and until that functionality is complete Buildbot is stuck
> maintaining *both* - an awkward position.
>
> == scope ==
> This project would involve surveying the missing functionality,
> implementing it, and adding tests and documentation. This involves
> relatively little design work, but a good bit of hands-on debugging and
> coding.
>
> == relevant bugs ==
> The relevant bugs are tagged with 'master-side-source-steps:
> [[TicketQuery(order=priority,status!=closed,keywords~=master-side-source-
> steps,format=table,col=summary|owner)]]
New description:
GSoC 2011 included a project to add master-side source steps. These are a
new implementation of steps that have historically housed their logic in
the slave's code, putting that logic in the master instead. There were a
few key pieces of functionality omitted from the new master-side source
steps, and until that functionality is complete Buildbot is stuck
maintaining *both* - an awkward position.
== scope ==
This project would involve surveying the missing functionality,
implementing it, and adding tests and documentation. This involves
relatively little design work, but a good bit of hands-on debugging and
coding.
== relevant bugs ==
The relevant bugs are tagged with 'master-side-source-steps:
[[TicketQuery(order=priority,status!=closed,keywords~=master-side-source-
steps,format=table,col=summary|owner)]]
--
Comment:
This was srinu's project last year - and now it's done!
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:13:24 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:13:24 -0000
Subject: [Buildbot-commits] [Buildbot] #2461: Add support for providing
and graphing data charts of build statistics over time.
In-Reply-To: <035.e7dbeb1ff209523ffe365bc7355d9def@buildbot.net>
References: <035.e7dbeb1ff209523ffe365bc7355d9def@buildbot.net>
Message-ID: <050.b705643e1a973439c51243eff37cb064@buildbot.net>
#2461: Add support for providing and graphing data charts of build statistics over
time.
-------------------------+--------------------
Reporter: juj | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: 0.8.7p1 | Resolution:
Keywords: |
-------------------------+--------------------
Description changed by dustin:
Old description:
> This is a feature request I would find extremely useful, and it's also
> one that would probably be a good one for GSoC, since it's a new feature
> with visually concrete results, which can make it more
> compelling/tractable for a new developer to get interested in.
>
> I maintain a continuous testing architecture for the Emscripten C++->JS
> compiler project (https://github.com/kripken/emscripten). It has an
> extensive unit testing and benchmarking suite, which prints a lot of
> graphable metrics out as the result of its run. The buildbot page is
> openly accessible at http://clb.demon.fi:8112/waterfall . More
> explanation at the bottom of the page here
> https://github.com/kripken/emscripten/wiki . While maintaining the
> buildbot, I've often wondered about the following:
>
> * How do build times vary over time? Are we optimizing the compiler, or
> is it getting more bloated and slowing down over time? Which commits
> caused big regressions/improvements?
> * How do buildbot task run times vary over time? These are already
> logged at the end of stdio with lines "program finished with exit code 0
> elapsedTime=1060.951319", which we'd like to graph over time.
> * How does runtime execution performance of compiled apps change over
> time? Emscripten has runtime benchmarks tester that tests runtime
> performance: http://clb.demon.fi:8112/builders/ubuntu-emcc-incoming-
> tests/builds/175/steps/Benchmarks/logs/stdio . Which commits caused big
> regressions/improvements?
> * How does compiled code size vary over time? There are some test apps
> that get built and stored after each commit:
> http://clb.demon.fi/dump/emcc/win-emcc-incoming-code-test/ . Which
> commits caused big regressions/improvements?
>
> To be able to measure these kind of quality concerns, visual graphing
> could be the answer. Being able to feed custom data fields into a data
> storage inside buildbot, and having a built-in data grapher integrated to
> buildbot HTTP server to visually compare metrics over time would be
> immensely helpful.
>
> The architecture should be somehow custom-driven so that the buildbot
> config files can control what data to generate and feed into graphs,
> since most of the above data points are specific to the project in
> question.
>
> Utilizing existing free graphing solutions would be expected, see for
> reference:
> * http://raphaeljs.com/analytics.html
> * https://www.reverserisk.com/ico/ (line graphs)
> * etc.
New description:
This is a feature request I would find extremely useful, and it's also one
that would probably be a good one for GSoC, since it's a new feature with
visually concrete results, which can make it more compelling/tractable for
a new developer to get interested in.
I maintain a continuous testing architecture for the Emscripten C++->JS
compiler project (https://github.com/kripken/emscripten). It has an
extensive unit testing and benchmarking suite, which prints a lot of
graphable metrics out as the result of its run. The buildbot page is
openly accessible at http://clb.demon.fi:8112/waterfall . More explanation
at the bottom of the page here https://github.com/kripken/emscripten/wiki
. While maintaining the buildbot, I've often wondered about the following:
* How do build times vary over time? Are we optimizing the compiler, or
is it getting more bloated and slowing down over time? Which commits
caused big regressions/improvements?
* How do buildbot task run times vary over time? These are already
logged at the end of stdio with lines "program finished with exit code 0
elapsedTime=1060.951319", which we'd like to graph over time.
* How does runtime execution performance of compiled apps change over
time? Emscripten has runtime benchmarks tester that tests runtime
performance: http://clb.demon.fi:8112/builders/ubuntu-emcc-incoming-
tests/builds/175/steps/Benchmarks/logs/stdio . Which commits caused big
regressions/improvements?
* How does compiled code size vary over time? There are some test apps
that get built and stored after each commit: http://clb.demon.fi/dump/emcc
/win-emcc-incoming-code-test/ . Which commits caused big
regressions/improvements?
To be able to measure these kind of quality concerns, visual graphing
could be the answer. Being able to feed custom data fields into a data
storage inside buildbot, and having a built-in data grapher integrated to
buildbot HTTP server to visually compare metrics over time would be
immensely helpful.
The architecture should be somehow custom-driven so that the buildbot
config files can control what data to generate and feed into graphs, since
most of the above data points are specific to the project in question.
Utilizing existing free graphing solutions would be expected, see for
reference:
* http://raphaeljs.com/analytics.html
* https://www.reverserisk.com/ico/ (line graphs)
* etc.
== Scope ==
This project involves quite a bit of design work. If you are applying to
work on this project, you will need to do most of that work *before* the
application deadline, and include your suggested design in with the GSoC
application. Things to think about:
* How will Buildbot gather the build statistics?
* How will Buildbot store the build statistics?
* How will Buildbot display the statistics?
* How will the statistics be made available for other purposes, e.g.,
export to a spreadsheet?
* How will users configure this?
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:16:19 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:16:19 -0000
Subject: [Buildbot-commits] [Buildbot] #2590: Use Alembic instead of
SQLAlchemy-Migrate
In-Reply-To: <038.01d6f3572dd087837bffc9b58acbdc59@buildbot.net>
References: <038.01d6f3572dd087837bffc9b58acbdc59@buildbot.net>
Message-ID: <053.bd5c9a759afb7e66354c594fa4c0e7aa@buildbot.net>
#2590: Use Alembic instead of SQLAlchemy-Migrate
-------------------------+--------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: | Resolution:
Keywords: database |
-------------------------+--------------------
Description changed by dustin:
Old description:
> Migrate has some compatibility problems - in particular, it doesn't work
> with SQLAlchemy >= 8.0. Its API is a little unpredictable, too, and it
> doesn't do a very good job of masking differences between dialects. Its
> linear numbering scheme is also problematic when developing on topic
> branches, as a merge of branches with overlapping DB version numbers will
> need some substantial changes to put them in linear order.
>
> Alembic seems to be the fix to all that, although that's as far as we've
> gotten.
>
> This would make a decent, if small, Google Summer of Code project.
New description:
Migrate has some compatibility problems - in particular, it doesn't work
with SQLAlchemy >= 8.0. Its API is a little unpredictable, too, and it
doesn't do a very good job of masking differences between dialects. Its
linear numbering scheme is also problematic when developing on topic
branches, as a merge of branches with overlapping DB version numbers will
need some substantial changes to put them in linear order.
Alembic seems to be the fix to all that, although that's as far as we've
gotten.
This would make a decent, if small, Google Summer of Code project.
== Scope ==
The goal of this project is clear: replace the functionality of
SQLAlchemy-Migrate with equivalent functionality implemented with Alembic.
A GSoC application should also address:
* Compatibility - users with current versions of Buildbot must be able to
upgrade to Alembic
* Testing - when database migrations fail, users lose data. The current
migrations are thoroughly tested to ensure they do the right thing on all
supported databases, and the new implementation must do the same.
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:26:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:26:41 -0000
Subject: [Buildbot-commits] [Buildbot] #2460: Build a plugin architecture
In-Reply-To: <038.6919b566108f7f458af744f94de142c3@buildbot.net>
References: <038.6919b566108f7f458af744f94de142c3@buildbot.net>
Message-ID: <053.5aab42ab85b1c59e9a9a5bbbd94c2be6@buildbot.net>
#2460: Build a plugin architecture
-------------------------+--------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: 0.8.7p1 | Resolution:
Keywords: |
-------------------------+--------------------
Description changed by dustin:
Old description:
> It should be possible for users to add extra functionality to Buildbot by
> installing additional packages from pypi. The extra functionality should
> include
> * change sources
> * build steps
> * status plugins
> * web UI components
> * utility scripts (#1828)
>
> The setuptools entry-points support can help here.
>
> Once this is complete, long-term unmaintained code currently distributed
> with Buildbot should be moved to external projects (still in the Buildbot
> github organization) where it can be maintained - or not - by its users.
>
> We should produce simple "hello-world" templates for each type of plugin,
> so that users have somewhere to start.
>
> == scope ==
>
> This project will involve understanding how Python packages are built,
> tested, documented, and distributed.
New description:
It should be possible for users to add extra functionality to Buildbot by
installing additional packages from pypi. The extra functionality should
include
* change sources
* build steps
* status plugins
* web UI components
* utility scripts (#1828)
The setuptools entry-points support can help here.
Once this is complete, long-term unmaintained code currently distributed
with Buildbot should be moved to external projects (still in the Buildbot
github organization) where it can be maintained - or not - by its users.
We should produce simple "hello-world" templates for each type of plugin,
so that users have somewhere to start.
== scope ==
This project will involve understanding how Python packages are built,
tested, documented, and distributed.
== related bugs ==
[[TicketQuery(order=priority,status!=closed,keywords~=plugins,format=table,col=summary|owner)]]
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:27:11 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:27:11 -0000
Subject: [Buildbot-commits] [Buildbot] #2642: [nine] Document Plugins
In-Reply-To: <038.8ce22803c975a9b39d9bfc5392566734@buildbot.net>
References: <038.8ce22803c975a9b39d9bfc5392566734@buildbot.net>
Message-ID: <053.acdba49d89975c67848e6d58f8931dc1@buildbot.net>
#2642: [nine] Document Plugins
------------------------+--------------------
Reporter: dustin | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: plugins |
------------------------+--------------------
Changes (by dustin):
* keywords: => plugins
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:30:04 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:30:04 -0000
Subject: [Buildbot-commits] [Buildbot] #1788: MQ options
In-Reply-To: <038.562d4de9cecd700250275a2eb5a51f11@buildbot.net>
References: <038.562d4de9cecd700250275a2eb5a51f11@buildbot.net>
Message-ID: <053.4997811f2e0adf85b3272708140388b3@buildbot.net>
#1788: MQ options
-------------------------+--------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: 0.8.3p1 | Resolution:
Keywords: |
-------------------------+--------------------
Description changed by dustin:
Old description:
> When Buildbot adopts an MQ framework, there are a number of choices.
> Among them:
>
> * pure-python, internal implementation (no network, only a single
> master)
> * pure-python, internal implementation that uses TCP or UDP between
> masters
> * http://morbidq.com/
> * http://code.google.com/p/coilmq/
> * txamqp
> * zeromq
>
> The first is already implemented in 'nine', but we need more.
>
> The more difficult part of this project is to ensure that messages are
> only delivered after the corresponding database changes are visible.
>
> The issue is a race condition between message passing and database
> replication. Imagine you have a large Buildbot installation with several
> replicated MySQL servers and a redundant RabbitMQ cluster. One buildbot
> master writes changes to a build to the database (an UPDATE operation),
> then sends a message describing the change. On another master, some
> service gets the message and queries a different MySQL server to see the
> build's new status. If the message arrives before the database
> replication occurs, then this master will see stale data. That will lead
> to a lot of subtle, rare bugs.
>
> == scope ==
> This project would involve separate tasks:
> * implement one or more of the above MQ plugins (mostly just coding)
> * solve the data-ordering problem (requiring some CS theory)
New description:
When Buildbot adopts an MQ framework, there are a number of choices.
Among them:
* pure-python, internal implementation (no network, only a single master)
* pure-python, internal implementation that uses TCP or UDP between
masters
* http://morbidq.com/
* http://code.google.com/p/coilmq/
* txamqp
* zeromq
The first is already implemented in 'nine', but we need more.
The more difficult part of this project is to ensure that messages are
only delivered after the corresponding database changes are visible.
The issue is a race condition between message passing and database
replication. Imagine you have a large Buildbot installation with several
replicated MySQL servers and a redundant RabbitMQ cluster. One buildbot
master writes changes to a build to the database (an UPDATE operation),
then sends a message describing the change. On another master, some
service gets the message and queries a different MySQL server to see the
build's new status. If the message arrives before the database
replication occurs, then this master will see stale data. That will lead
to a lot of subtle, rare bugs.
== scope ==
This project would involve separate tasks:
* implement one or more of the above MQ plugins (mostly just coding)
* solve the data-ordering problem (requiring some CS theory)
== relevant bugs ==
[[TicketQuery(order=priority,status!=closed,keywords~=mq,format=table,col=summary|owner)]]
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 18:40:03 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 18:40:03 -0000
Subject: [Buildbot-commits] [Buildbot] #2647: [nine] Import old Pickles
In-Reply-To: <038.2a34f9e8b522fa803569f642070c8bc0@buildbot.net>
References: <038.2a34f9e8b522fa803569f642070c8bc0@buildbot.net>
Message-ID: <053.a92019f5d16d4ab15fac3a57cb333fb7@buildbot.net>
#2647: [nine] Import old Pickles
-------------------------+--------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: |
-------------------------+--------------------
Changes (by dustin):
* type: task => project-idea
Old description:
> The most likely plan for data from 0.8.x implementations is to ignore it.
> However, it would be great for users if data in build pickles could be
> easily imported into the database.
New description:
The most likely plan for data from 0.8.x implementations is to ignore it.
However, it would be great for users if data in build pickles could be
easily imported into the database.
== scope ==
The outline of this project is pretty clear: if the user requests it, read
all of the 0.8.x data from pickles and logfiles, and write it into the
database. The tricky bits will be about handling subtle incompatibilities
between the pickle data format and what's in the database, as well as
encoding errors (most of the data in pickles are bytestrings, while
everything in the DB is unicode).
A good GSoC application would talk about these edge cases:
* What are some of the subtle incompatibilities? (this will require
looking at what's in the pickles and in the database) How will you handle
them?
* How will you handle converting bytestrings into unicode strings?
* When a user's data import fails because of some error we haven't
anticipated, what happens? Is their database corrupt? Can they re-run
the script once they've fixed the error? How will the script report
progress?
There's a lot of design work here, and we will need to see much of it in
the application. Part of the decision to accept the proposal will be on
the quality of the design, so make it good! Keep in mind that you can ask
for feedback on your design before the applications are due.
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sat Feb 8 20:40:08 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sat, 08 Feb 2014 20:40:08 -0000
Subject: [Buildbot-commits] [Buildbot] #2692: Auto-generate some
documentation
Message-ID: <038.9bb0a3648358c7f5228dc8977d4abb7d@buildbot.net>
#2692: Auto-generate some documentation
-------------------------+-------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: | Keywords: docs
-------------------------+-------------------
Lots of the Buildbot documentation is manually maintained to correspond to
the code: buildstep arguments, data API descriptions, DB APIs, and so on.
It'd be great to have some means of automatically verifying or even
generating that documentation. http://dexy.it/ looks like a useful
general tool for building this kind of thing.
== Scope ==
This project would involve writing code and configuration to automate the
documentation-generation process. This should take Buildbot's source code
as input (preferably parsed by Python, rather than with regular
expressions or some other text-mode process) and generate rst output that
can then be processed using Sphinx.
A good GSoC application will identify several areas of the documentation
that can be converted to automatic generation. These should become
milestones in the project schedule.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 9 14:56:17 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 09 Feb 2014 14:56:17 -0000
Subject: [Buildbot-commits] [Buildbot] #2587: Buildbot doesn't accept
changes done by the same user for different repositories
In-Reply-To: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
References: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
Message-ID: <057.e9626e6bd604a01a3691ff4e8a21248b@buildbot.net>
#2587: Buildbot doesn't accept changes done by the same user for different
repositories
---------------------------+--------------------
Reporter: jollyroger | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution:
Keywords: database users |
---------------------------+--------------------
Comment (by gracinet):
Wouldn't that be reasonible to consider valid email addresses to be unique
enough ?
In that case, the Python library has methods to parse them that could
help.
Of course that'd stay an external input, therefore someone could cheat by
submitting bogus author information in their changesets.
Is this a security concern, though? Any implications on authentication ?
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 9 15:01:36 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 09 Feb 2014 15:01:36 -0000
Subject: [Buildbot-commits] [Buildbot] #2587: Buildbot doesn't accept
changes done by the same user for different repositories
In-Reply-To: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
References: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
Message-ID: <057.0718ad26cc8b2ede4f43b69b44b496c3@buildbot.net>
#2587: Buildbot doesn't accept changes done by the same user for different
repositories
---------------------------+--------------------
Reporter: jollyroger | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution:
Keywords: database users |
---------------------------+--------------------
Comment (by dustin):
Not all version-control systems supply email addresses, though, nor do IRC
networks. So, for example, if Buildbot sees 'dustin' as a subversion
username, then 'dustin' seems a reasonable identifier. If it later sees
'dustin' as a github username, I'd very much like that it not assume
that's me (it's not), so it should create a new user identity in Buildbot.
But the 'dustin' identity is already taken, and no email address is
readily available. In this case, using 'dustin (2)' would, I think, be a
good solution.
That identifier is only ever used for display purposes (it's separate from
the username), and thus can be changed easily. Well, it could if the
'buildbot user' command worked better :)
Buildbot authentication always happens with a username and password.
Users should only rely on identifiers from version control systems if they
know that those version control systems are secure. For example, if SSH
is configured to use the system username, and commits are only allowed by
SSH, that's probably safe. On the other hand, trusting committer/author
information from a simple git repository is most definitely not safe.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 9 15:12:38 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 09 Feb 2014 15:12:38 -0000
Subject: [Buildbot-commits] [Buildbot] #2587: Buildbot doesn't accept
changes done by the same user for different repositories
In-Reply-To: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
References: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
Message-ID: <057.e9290dea997e505909a67b5cd562fdb3@buildbot.net>
#2587: Buildbot doesn't accept changes done by the same user for different
repositories
---------------------------+--------------------
Reporter: jollyroger | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution:
Keywords: database users |
---------------------------+--------------------
Comment (by gracinet):
Sorry I haven't been really clear, I was suggesting that ''in case'' the
identifier looks to be an email address (which the library can help us to
check), it could be assumed to be unique.
Any way, if this is only for display purposes, I agree there's not much
point about guesswork, and a simple disambiguation system would at least
solve the blocking. Buildmaster admins can then very well perform
afterwards merging with whatever tool or decide not to care.
The pattern you suggest above ```User Name (1) '```
means that the disambiguation part should anyway use the address parsing
utilities.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 00:17:19 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 00:17:19 -0000
Subject: [Buildbot-commits] [Buildbot] #928: Allow builder to be
associated with multiple categories
In-Reply-To: <038.51386ed5975d423860b7df3ecfae8e27@buildbot.net>
References: <038.51386ed5975d423860b7df3ecfae8e27@buildbot.net>
Message-ID: <053.384c1d730ed725d96d5b8bf708f1dbaa@buildbot.net>
#928: Allow builder to be associated with multiple categories
------------------------+-------------------------
Reporter: stefan | Owner: jaredgrubb
Type: enhancement | Status: assigned
Priority: major | Milestone: 0.9.+
Version: 0.8.0 | Resolution:
Keywords: sprint |
------------------------+-------------------------
Comment (by jaredgrubb):
I have this patch ready (for 9) but need to get it approved.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 02:02:34 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 02:02:34 -0000
Subject: [Buildbot-commits] [Buildbot] #419: No tests for
buildbot.changes.hgbuildbot.py ?
In-Reply-To: <039.a0482836020bd633f2a3f0750c8f5e9c@buildbot.net>
References: <039.a0482836020bd633f2a3f0750c8f5e9c@buildbot.net>
Message-ID: <054.f6d527292919ca3a3b13680e4f0aa117@buildbot.net>
#419: No tests for buildbot.changes.hgbuildbot.py ?
-----------------------------+----------------------
Reporter: marcusl | Owner: marcusl
Type: defect | Status: closed
Priority: patches-accepted | Milestone: 0.8.+
Version: 0.7.9 | Resolution: fixed
Keywords: hg simple sprint |
-----------------------------+----------------------
Changes (by dustin):
* status: new => closed
* resolution: => fixed
Old description:
> As we did some changes to add support for inrepo branches, it is probably
> a good thing to have some tests for this, to see that everything runs
> smoothly.
New description:
As we did some changes to add support for inrepo branches, it is probably
a good thing to have some tests for this, to see that everything runs
smoothly.
--
Comment:
And now it's gone :)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 09:26:36 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 09:26:36 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: CornellGoeman
Message-ID: <20140210092636.BD90B11F83D@buildbot-trac.community.scl3.mozilla.com>
New user registration for user CornellGoeman
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 09:37:16 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 09:37:16 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: hunnysunny
Message-ID: <20140210093716.0518A11F83D@buildbot-trac.community.scl3.mozilla.com>
New user registration for user hunnysunny
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 09:38:19 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 09:38:19 -0000
Subject: [Buildbot-commits] [Buildbot] #2693: weight loss permantly 658
Message-ID: <042.fd48789470f4b1bcfd623bd02ad21f52@buildbot.net>
#2693: weight loss permantly 658
-----------------------+----------------------------
Reporter: hunnysunny | Owner:
Type: task | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.8 | Keywords: Cleanse Ultimo
-----------------------+----------------------------
end up putting it all back on now that I gave you an idea the secretor
learn program here's exactly what you'll get shipped to your door with the
31 Day Fat Loss Cure program the 31 Day Fat Loss Cure manual it 127dollar
value once inside this sixty eight-page manual don?t get my step-by-step
31 day program with my little known fact burning workouts these workouts
can be done right your living room with absolutely no equipment at all you
won't even need a dumbbell or appall-up bar and if you like going to the
gym I?ve also included my gym program that's focused around
[http://cleanseultimoadvice.com/ Cleanse Ultimo] program the beginners
program is perfect if you had been very active lately orchard bodyweight
http://cleanseultimoadvice.com/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 09:45:22 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 09:45:22 -0000
Subject: [Buildbot-commits] [Buildbot] #2694: Essay Writing Software
Message-ID: <045.48f5255a3d8bd5ec1c06d21708a7ff05@buildbot.net>
#2694: Essay Writing Software
--------------------------+-----------------------
Reporter: CornellGoeman | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords:
--------------------------+-----------------------
We now have essay-writing software application our publishers make use of
to examine on in situation your customized designed research document,
framework, declaration, discuss, thesis, as well as term documents are
generally totally without any plagiarism as well as syntax mistakes.
There is plenty of [http://www.vipessayservice.com/blog/expository-essay-
topics expository essay topics for college] writing online marketers
exactly where almost all scholars acquire essay writing help. The
organization is exclusively generally because all of us offer you top
outstanding quality framework writing support which clothes additional
writing suppliers. Generally, they offer the customers biggest framework
writing suppliers which have allowed many of them move their own levels.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 09:58:14 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 09:58:14 -0000
Subject: [Buildbot-commits] [Buildbot] #2693: weight loss permantly 658
In-Reply-To: <042.fd48789470f4b1bcfd623bd02ad21f52@buildbot.net>
References: <042.fd48789470f4b1bcfd623bd02ad21f52@buildbot.net>
Message-ID: <057.4a755842a607a81c63ad673ca5ad0d7c@buildbot.net>
#2693: weight loss permantly 658
---------------------------+------------------------
Reporter: hunnysunny | Owner:
Type: task | Status: closed
Priority: minor | Milestone: undecided
Version: 0.8.8 | Resolution: invalid
Keywords: Cleanse Ultimo |
---------------------------+------------------------
Changes (by ewong):
* status: new => closed
* resolution: => invalid
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 09:58:50 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 09:58:50 -0000
Subject: [Buildbot-commits] [Buildbot] #2694: Essay Writing Software
In-Reply-To: <045.48f5255a3d8bd5ec1c06d21708a7ff05@buildbot.net>
References: <045.48f5255a3d8bd5ec1c06d21708a7ff05@buildbot.net>
Message-ID: <060.e176bb20a56879b35adf2ab8d46695f7@buildbot.net>
#2694: Essay Writing Software
--------------------------+------------------------
Reporter: CornellGoeman | Owner:
Type: undecided | Status: closed
Priority: major | Milestone: undecided
Version: 0.8.8 | Resolution: invalid
Keywords: |
--------------------------+------------------------
Changes (by ewong):
* status: new => closed
* resolution: => invalid
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 11:55:31 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 11:55:31 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: chrisjohn000
Message-ID: <20140210115531.C217B11F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user chrisjohn000
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 12:04:08 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 12:04:08 -0000
Subject: [Buildbot-commits] [Buildbot] #2695: weight loss new program
Message-ID: <044.12a994d21fed6e37601c9b13c521afaf@buildbot.net>
#2695: weight loss new program
-------------------------+-------------------------
Reporter: chrisjohn000 | Owner: < default >
Type: task | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.8 | Keywords: contrib
-------------------------+-------------------------
already given up then the question becomes will happily burn up this
dysfunctional at a petition to talk about that but this is the key see if
you have people it that they?ve tried to lose weight the weight loss stops
and yet there still really overweight because that that that's hanging off
there as usually oftentimes places are not very desirable looking places
we have this fat maybe tender arms of your browser or your hips revised
and in fact you can lose much weight as you want it seems and that stopped
just doesn't seem to want to go away very frustrating so I a segue to talk
about feared and one of my talks I always talk about the goldilocks
principle which is basically you want everything to be just right in order
for things to work can store goldilocks breaks into the house and she
tries love them follows bed was to harden the mother that was to stop of
course the babies that was just right and then she accidents last
incidentmexico sleep in the baby's dead which he tries to soup and mama's
with you papa soup was to hide in the babysitting was destroyed of course
but you want your soup to be right if your soup is a bright meaning what's
inside your body or your brain chemistry Arial hormonal chemistry things
are not going to work and so there's optimum out the facts this is where
this you should[http://cleanseultimoadvice.com/ Cleanse Ultimo] performs
along too little of something or too much of something is no good even if
it's something that you may think is good for you for example water it's
possible to have not enough water we call it dehydration it's also
possible to have too much water that's over hydration that's actually very
him dangerous to drink too much water I think really yesterday's news
people and actually have died from drinking too much water in this from
these meetings for these fraternities you may be heard of these things so
everything is to be
http://cleanseultimoadvice.com/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 12:34:11 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 12:34:11 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: angelacrystal
Message-ID: <20140210123411.D1D6211F83D@buildbot-trac.community.scl3.mozilla.com>
New user registration for user angelacrystal
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 13:21:43 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 13:21:43 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: angelacrystal
Message-ID: <20140210132143.0C8AC11F7FC@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user angelacrystal
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 13:21:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 13:21:48 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: chrisjohn000
Message-ID: <20140210132148.0FCA211FD7F@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user chrisjohn000
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 13:21:50 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 13:21:50 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: CornellGoeman
Message-ID: <20140210132150.4D88311F7FC@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user CornellGoeman
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 13:21:51 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 13:21:51 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: hunnysunny
Message-ID: <20140210132151.AF1C311FE00@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user hunnysunny
--
Buildbot
Buildbot: build/test automation
From noreply at github.com Mon Feb 10 15:05:54 2014
From: noreply at github.com (GitHub)
Date: Mon, 10 Feb 2014 07:05:54 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 09749e: On solaris use the
tail in /usr/xpg4/bin/tail inst...
Message-ID: <52f8ead216d83_70f2d1dd3c11274a@hookshot-fe10-pe1-prd.aws.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 09749e7fe72915d3718bcac37902dab0af383a2b
https://github.com/buildbot/buildbot/commit/09749e7fe72915d3718bcac37902dab0af383a2b
Author: Yasser Lebon
Date: 2014-02-10 (Mon, 10 Feb 2014)
Changed paths:
M slave/buildslave/scripts/logwatcher.py
Log Message:
-----------
On solaris use the tail in /usr/xpg4/bin/tail insteaf of /usr/bin/tail which does not support the -n option
Commit: a275913fb0732e56bfc6a881614a4a74a44155b2
https://github.com/buildbot/buildbot/commit/a275913fb0732e56bfc6a881614a4a74a44155b2
Author: Dustin J. Mitchell
Date: 2014-02-10 (Mon, 10 Feb 2014)
Changed paths:
M slave/buildslave/scripts/logwatcher.py
Log Message:
-----------
Merge madazone/buildbot:upstream-master (PR #1065)
Compare: https://github.com/buildbot/buildbot/compare/54efd81f3cef...a275913fb073
From noreply at github.com Mon Feb 10 15:05:54 2014
From: noreply at github.com (GitHub)
Date: Mon, 10 Feb 2014 07:05:54 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 74b0b4: Do not catch
GeneratorExit exception
Message-ID: <52f8ead2f30d9_7faa1311d38895e@hookshot-fe8-pe1-prd.aws.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 74b0b421b89099e9759bee3664aefd785086c623
https://github.com/buildbot/buildbot/commit/74b0b421b89099e9759bee3664aefd785086c623
Author: chantra
Date: 2014-01-30 (Thu, 30 Jan 2014)
Changed paths:
M master/buildbot/process/buildstep.py
Log Message:
-----------
Do not catch GeneratorExit exception
On buildbot 0.8.8 in rare conditions, we hit:
File "/data/buildbot/twisted/internet/threads.py", line 49, in deferToThreadPool
threadpool.callInThreadWithCallback(onResult, f, *args, **kwargs)
File "/data/buildbot/twisted/python/threadpool.py", line 148, in callInThreadWithCallb
ack
self.q.put(o)
File "//usr/lib/python2.7/Queue.py", line 138, in put
self.not_empty.notify()
File "//usr/lib/python2.7/threading.py", line 392, in notify
for waiter in waiters:
--- ---
File "/data/buildbot/buildbot/process/buildstep.py", line 605, in _startStep_3
result = yield defer.maybeDeferred(self.start)
exceptions.GeneratorExit:
this applies the fix from http://trac.buildbot.net/ticket/2395#comment:10 to master/buildbot/process/buildstep.py
Commit: 54efd81f3cefb6525fe90917b13b373f96184d45
https://github.com/buildbot/buildbot/commit/54efd81f3cefb6525fe90917b13b373f96184d45
Author: Dustin J. Mitchell
Date: 2014-01-31 (Fri, 31 Jan 2014)
Changed paths:
M master/buildbot/process/buildstep.py
Log Message:
-----------
Merge chantra/buildbot:fb-master (PR #1063)
Commit: 5bab83c7bb2d31e0082074aa6a33f4d9737ccce9
https://github.com/buildbot/buildbot/commit/5bab83c7bb2d31e0082074aa6a33f4d9737ccce9
Author: Dustin J. Mitchell
Date: 2014-02-08 (Sat, 08 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
Log Message:
-----------
Merge branch 'master' into nine
Compare: https://github.com/buildbot/buildbot/compare/c4a765be5026...5bab83c7bb2d
From noreply at github.com Mon Feb 10 15:07:21 2014
From: noreply at github.com (GitHub)
Date: Mon, 10 Feb 2014 07:07:21 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 9b7619: apply 09749e7 to
master
Message-ID: <52f8eb29e051c_3fb5901d34287df@hookshot-fe7-pe1-prd.aws.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 9b7619020790d9437a8f5a7f97f26803df523132
https://github.com/buildbot/buildbot/commit/9b7619020790d9437a8f5a7f97f26803df523132
Author: Yasser Lebon
Date: 2014-02-10 (Mon, 10 Feb 2014)
Changed paths:
M master/buildbot/scripts/logwatcher.py
Log Message:
-----------
apply 09749e7 to master
From trac at buildbot.net Mon Feb 10 19:33:13 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 19:33:13 -0000
Subject: [Buildbot-commits] [Buildbot] #2696: (PostgreSQL) missing rollback
in db.scheduler
Message-ID: <040.9b0798ab145c252883c9a91df9555b39@buildbot.net>
#2696: (PostgreSQL) missing rollback in db.scheduler
---------------------+-----------------------
Reporter: gracinet | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: master | Keywords:
---------------------+-----------------------
Main symptom:
{{{
File "/srv/buildbot/local/lib/python2.7/site-
packages/sqlalchemy/engin
e/base.py", line 1690, in _execute_context
context)
File "/srv/buildbot/local/lib/python2.7/site-
packages/sqlalchemy/engin
e/default.py", line 335, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.InternalError: (InternalError) current transaction
is aborted, commands ignored until end of transaction block
'UPDATE scheduler_changes SET important=%(important)s WHERE
scheduler_changes.objectid = %(objectid_1)s AND scheduler_changes.changeid
= %(wc_changeid)s' {'wc_changeid': 5096, 'important': 1, 'objectid_1': 15}
}}}
This excerpt from ```db.schedulers``` cannot work with PostgreSQL:
{{{
except (sqlalchemy.exc.ProgrammingError,
sqlalchemy.exc.IntegrityError):
# insert failed, so try an update
conn.execute(upd_q,
}}}
Indeed, after either of these two exceptions, the transaction must be
rollbacked.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 19:41:50 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 19:41:50 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: TeresaDIOB
Message-ID: <20140210194150.0767511F83E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user TeresaDIOB
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 20:00:09 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 20:00:09 -0000
Subject: [Buildbot-commits] [Buildbot] #2696: (PostgreSQL) missing
rollback in db.scheduler
In-Reply-To: <040.9b0798ab145c252883c9a91df9555b39@buildbot.net>
References: <040.9b0798ab145c252883c9a91df9555b39@buildbot.net>
Message-ID: <055.1b59b8eb10844402e5e21ffbd8c8b01c@buildbot.net>
#2696: (PostgreSQL) missing rollback in db.scheduler
---------------------+------------------------
Reporter: gracinet | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: master | Resolution:
Keywords: |
---------------------+------------------------
Comment (by gracinet):
A quickfix is at
https://github.com/gracinet/buildbot/commit/c9289275452555f96db2aa1edd8e2824f34e85dc
Contrary to what the commit message says, the transactional behaviour with
the quickfix is suboptimal (the transaction is about several changeset,
one failed insert should not rollback the others).
A better version would be to check for prior existence and update or
insert accordingly, but I'll have to dig a bit further to know what this
is about really.
savepoints would be an option, but I'm not sure all RDMS provide them
(does SQLite ? ) IIRC, they're not even exposed in an abstract API by
psycopg2.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 10 20:32:30 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 10 Feb 2014 20:32:30 -0000
Subject: [Buildbot-commits] [Buildbot] #2696: (PostgreSQL) missing
rollback in db.scheduler
In-Reply-To: <040.9b0798ab145c252883c9a91df9555b39@buildbot.net>
References: <040.9b0798ab145c252883c9a91df9555b39@buildbot.net>
Message-ID: <055.dcb4876ff5e102d71a9462dd92e94008@buildbot.net>
#2696: (PostgreSQL) missing rollback in db.scheduler
---------------------+------------------------
Reporter: gracinet | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: master | Resolution:
Keywords: |
---------------------+------------------------
Comment (by dustin):
Checking and then inserting introduces a race condition - that's what
we're trying to avoid with this logic.
It's OK to introduce DB-specific behavior in the DB modules, if there's a
need to.
Is it automatic that when an insert fails, Postgres aborts the whole
transaction? Or is that something automatic that's happening on the
client? In my testing with postgres, this works fine (the
buildbot.test.unit.test_db_schedulers.TestSchedulersConnectorComponent.test_classifyChanges_again
executes this particular except block)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 11 12:53:02 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 11 Feb 2014 12:53:02 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: vanezapow
Message-ID: <20140211125302.16D4011F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user vanezapow
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 11 13:09:04 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 11 Feb 2014 13:09:04 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: saicrila
Message-ID: <20140211130904.7A81711F83E@buildbot-trac.community.scl3.mozilla.com>
New user registration for user saicrila
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 11 19:30:14 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 11 Feb 2014 19:30:14 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Megaei
Message-ID: <20140211193014.83FA311FB05@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Megaei
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 11 20:02:35 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 11 Feb 2014 20:02:35 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: vanezapow
Message-ID: <20140211200235.C1AB312046E@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user vanezapow
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 11 20:02:35 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 11 Feb 2014 20:02:35 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: saicrila
Message-ID: <20140211200235.9452711F83E@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user saicrila
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 10:36:55 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 10:36:55 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: ADelmerdek
Message-ID: <20140212103655.20C3E11FB05@buildbot-trac.community.scl3.mozilla.com>
New user registration for user ADelmerdek
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 10:46:32 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 10:46:32 -0000
Subject: [Buildbot-commits] [Buildbot] #2697: Clean Face Fresh Face
Message-ID: <039.fa2445a851e62ffe139c65a78ae76f44@buildbot.net>
#2697: Clean Face Fresh Face
--------------------+-------------------------
Reporter: maryfox | Owner: < default >
Type: task | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords: admin
--------------------+-------------------------
I look at Taiwan and it was and I have my purse is on here answer cross-
body I created yes photo stream line collage with ease I'm lottery hang a
wreath that I got from Michaels craft store and they came in a package so
this is what they look like and I just printed out some of myfavorite
pictures of Integra and my phone and I hung them up on this mind I guess
you could call it dislikes try wrote saying that my mom found at Michael?s
I think so yeah that is what is on this wall sorry herein haven't my
nightstand.
I also have the someone on backside but this is actually from Ross and
what did was this was black this metal part here and spray painted it for
you to match my room this [http://aktiveamadvice.com/ Aktive AM] unique
right here actually paid bank and I got this from target and it was
originally blue but I speaking it this kind of mustard yellow color these
flowers are from home visits and my candle holder thing that she is from a
target and then this repair flow Campbell is for I'm at myopic so that is
my neck down this side looks like so my edit comforter is just the blue
and pink floral print and then asked this blue and white striped on the
opposite side.
So I think it's reverse the ball but its trend the target shabby chic
collection and then this pillow right here which is just a creamy roughly
parallel is also from target this 10 years from target day %uh pink one is
from target and then this came up with the Comforter Set knots from that
shabby chic collection and my sheets are just these click floral lands and
these are from the shabby chic collection as well and then my bowl and
keep this is the best blanket ever its private pier 1 imports and it's
just screen with some ruffles on it.
http://aktiveamadvice.com/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 12:52:37 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 12:52:37 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: maryfox
Message-ID: <20140212125237.19BD611F83E@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user maryfox
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 13:05:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 13:05:48 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: allonaroy
Message-ID: <20140212130548.BE4D611FB05@buildbot-trac.community.scl3.mozilla.com>
New user registration for user allonaroy
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 13:19:08 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 13:19:08 -0000
Subject: [Buildbot-commits] [Buildbot] #2587: Buildbot doesn't accept
changes done by the same user for different repositories
In-Reply-To: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
References: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
Message-ID: <057.7af338a8e51327d1d47beb196cfb1cab@buildbot.net>
#2587: Buildbot doesn't accept changes done by the same user for different
repositories
---------------------------+--------------------
Reporter: jollyroger | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution:
Keywords: database users |
---------------------------+--------------------
Comment (by jollyroger):
I've remembered another possible caveat with using email address. Even
buildbot has some examples: simply run '''`git log | grep Author: | sort |
uniq`''' . So how many emails does Dustin have? And the same picture is
for lots of other repositories. This is mostly a problem to make a precise
statistics per person but we still could use this to have a description
and email to blame for a broken build. I've seen Redmine project has a
possibility to map repository id's to the id's of the accounts inside this
software. Some semi-automatic matching rules are available there (if email
matches strictly, for example) but you always can change things manually.
Once this is done, association of the commits in VCS and Redmine user
allows to have a better navigation and linking.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 13:37:30 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 13:37:30 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: margaretwdame
Message-ID: <20140212133730.546D411FB05@buildbot-trac.community.scl3.mozilla.com>
New user registration for user margaretwdame
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 13:41:16 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 13:41:16 -0000
Subject: [Buildbot-commits] [Buildbot] #2698: Cleanse Ultimo is very advance
base product
Message-ID: <045.e9f8ca30945597f9d812b5a6eb85c4e3@buildbot.net>
#2698: Cleanse Ultimo is very advance base product
--------------------------+-----------------------
Reporter: margaretwdame | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords:
--------------------------+-----------------------
Because let's have a little think about smoked a cable [[Cleanse Ultimo]]
that about Willie BK I A Dolly Parton great book not working for me but
gone are the days of nasty glue in mohair instead extensions a fixed into
place by tiny metal clamps the hair is that for two years say literally
every 10 a small quakes you?re just going to sell have the clip opened up
the halo of light up will start again from places listed like girls giant
range oh my God my chain too much though I'm guilty re in it anything
really beautiful I'm very excited about going to be all very excited I'm
very excited this is totally a big deal but it s she's never had long
shiny peek at so we're going to give it to a change in allot from luscious
locks change the at the moment you look like a disco ballet yes variable
yeah case stylus Troy Thompson has a different kind of challenge on his
hands thinking about the son David Beckham local do I think that style but
said should know election play media you need to have ashcake within the
head when.
[http://cleanseultimohq.com]
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 13:47:53 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 13:47:53 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: michaelmmoore
Message-ID: <20140212134753.D25B312046E@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user michaelmmoore
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 13:47:53 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 13:47:53 -0000
Subject: [Buildbot-commits] [Buildbot] Deleted User: margaretwdame
Message-ID: <20140212134753.A5D9811FB05@buildbot-trac.community.scl3.mozilla.com>
Deleted User for user margaretwdame
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 12 15:44:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 12 Feb 2014 15:44:48 -0000
Subject: [Buildbot-commits] [Buildbot] #2587: Buildbot doesn't accept
changes done by the same user for different repositories
In-Reply-To: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
References: <042.647ffbe58d9dbdf43cd36c8ede4b35cf@buildbot.net>
Message-ID: <057.3fb13df18bf005b61d22a4d67595bbc4@buildbot.net>
#2587: Buildbot doesn't accept changes done by the same user for different
repositories
---------------------------+--------------------
Reporter: jollyroger | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution:
Keywords: database users |
---------------------------+--------------------
Comment (by dustin):
Yes - that's the idea we're going for here. It just needs to get
implemented :)
Know any students that want to apply to GSoC?
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 13 16:20:14 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 13 Feb 2014 16:20:14 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: friedgold
Message-ID: <20140213162014.F26B611FA66@buildbot-trac.community.scl3.mozilla.com>
New user registration for user friedgold
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 13 16:32:52 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 13 Feb 2014 16:32:52 -0000
Subject: [Buildbot-commits] [Buildbot] #2699: Changes not shown in filtered
waterfall view
Message-ID: <041.24a3e4d72aad25093c9dd012c9aa4dfb@buildbot.net>
#2699: Changes not shown in filtered waterfall view
----------------------+-----------------------
Reporter: friedgold | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.8 | Keywords:
----------------------+-----------------------
In the filtered waterfall view it appears that the changes aren't
displayed correctly. The changes column is always empty except for a '?'
at the bottom of the page.
I've observed this on our local buildbot install (version 0.8.6p1), but
you can see the same problem on buildbot's buildbot, for example:
http://buildbot.buildbot.net/waterfall?category=config
When googling for answers I also stumbled across this, which I believe
describes the same issue:
https://mail.python.org/pipermail//python-committers/2013-July/002636.html
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Sun Feb 16 18:07:54 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 16 Feb 2014 18:07:54 -0000
Subject: [Buildbot-commits] [Buildbot] #2699: Changes not shown in
filtered waterfall view
In-Reply-To: <041.24a3e4d72aad25093c9dd012c9aa4dfb@buildbot.net>
References: <041.24a3e4d72aad25093c9dd012c9aa4dfb@buildbot.net>
Message-ID: <056.cd42cd8a4b21c540d716ae91671cbef8@buildbot.net>
#2699: Changes not shown in filtered waterfall view
----------------------+--------------------
Reporter: friedgold | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: web |
----------------------+--------------------
Changes (by dustin):
* keywords: => web
* milestone: undecided => 0.8.+
Comment:
I suspect that the waterfall view is filtering both builders and changes
using the given category, even though those are two unrelated sets of
categories. So unless your changes happen to have category 'config', you
won't see them.
Does that match what you're seeing?
There's work underway to support "tags" for builders, which would
disambuguate the two kinds of categories.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 17 13:00:21 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 17 Feb 2014 13:00:21 -0000
Subject: [Buildbot-commits] [Buildbot] #2683: clobber if git clean fails
In-Reply-To: <038.5400cc43c483acfdfeadb7c449459aeb@buildbot.net>
References: <038.5400cc43c483acfdfeadb7c449459aeb@buildbot.net>
Message-ID: <053.fb65f8cbe1edaf605624b0b962058310@buildbot.net>
#2683: clobber if git clean fails
-------------------+---------------------
Reporter: dustin | Owner:
Type: defect | Status: closed
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution: fixed
Keywords: git |
-------------------+---------------------
Changes (by dustin):
* status: new => closed
* resolution: => fixed
Comment:
We had a look at the contents of the directory, and it appears that one of
the files in .git is empty ({{{HEAD}}}, IIRC), probably from a full disk
at some point. Git refuses to go on after this, so every time the source
step runs for this builder on this slave, it fails.
This was fixed in https://github.com/buildbot/buildbot/pull/1058
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From noreply at github.com Mon Feb 17 13:09:09 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 05:09:09 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 09749e: On solaris use the
tail in /usr/xpg4/bin/tail inst...
Message-ID: <530209f5d0771_39aa1141d3c345f6@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 09749e7fe72915d3718bcac37902dab0af383a2b
https://github.com/buildbot/buildbot/commit/09749e7fe72915d3718bcac37902dab0af383a2b
Author: Yasser Lebon
Date: 2014-02-10 (Mon, 10 Feb 2014)
Changed paths:
M slave/buildslave/scripts/logwatcher.py
Log Message:
-----------
On solaris use the tail in /usr/xpg4/bin/tail insteaf of /usr/bin/tail which does not support the -n option
Commit: a275913fb0732e56bfc6a881614a4a74a44155b2
https://github.com/buildbot/buildbot/commit/a275913fb0732e56bfc6a881614a4a74a44155b2
Author: Dustin J. Mitchell
Date: 2014-02-10 (Mon, 10 Feb 2014)
Changed paths:
M slave/buildslave/scripts/logwatcher.py
Log Message:
-----------
Merge madazone/buildbot:upstream-master (PR #1065)
Commit: 9b7619020790d9437a8f5a7f97f26803df523132
https://github.com/buildbot/buildbot/commit/9b7619020790d9437a8f5a7f97f26803df523132
Author: Yasser Lebon
Date: 2014-02-10 (Mon, 10 Feb 2014)
Changed paths:
M master/buildbot/scripts/logwatcher.py
Log Message:
-----------
apply 09749e7 to master
Commit: ce19aac21c3e0af550b31748305935f95d720ed6
https://github.com/buildbot/buildbot/commit/ce19aac21c3e0af550b31748305935f95d720ed6
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/scripts/logwatcher.py
M slave/buildslave/scripts/logwatcher.py
Log Message:
-----------
Merge branch 'master' of github.com:buildbot/buildbot into nine
Commit: dff7724cf3ef241670e013509f6f96db245b3b54
https://github.com/buildbot/buildbot/commit/dff7724cf3ef241670e013509f6f96db245b3b54
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M Makefile
Log Message:
-----------
add a 'gruntci' Makefile target
Compare: https://github.com/buildbot/buildbot/compare/5bab83c7bb2d...dff7724cf3ef
From trac at buildbot.net Mon Feb 17 14:53:17 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 17 Feb 2014 14:53:17 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: nothing
Message-ID: <20140217145317.6CBC411F935@buildbot-trac.community.scl3.mozilla.com>
New user registration for user nothing
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 17 14:53:33 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 17 Feb 2014 14:53:33 -0000
Subject: [Buildbot-commits] [Buildbot] Password reset for user: nothing
Message-ID: <20140217145333.54CE711F935@buildbot-trac.community.scl3.mozilla.com>
Password reset for user for user nothing
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 17 18:25:20 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 17 Feb 2014 18:25:20 -0000
Subject: [Buildbot-commits] [Buildbot] Password reset for user: dlatornell
Message-ID: <20140217182520.2FD5711FA66@buildbot-trac.community.scl3.mozilla.com>
Password reset for user for user dlatornell
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 17 18:26:40 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 17 Feb 2014 18:26:40 -0000
Subject: [Buildbot-commits] [Buildbot] Password reset for user: dlatornell
Message-ID: <20140217182640.16A6C11FA66@buildbot-trac.community.scl3.mozilla.com>
Password reset for user for user dlatornell
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 17 22:28:53 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 17 Feb 2014 22:28:53 -0000
Subject: [Buildbot-commits] [Buildbot] #2700: 'grunt ci' fails,
when install gets that far
Message-ID: <038.e8fcf065e9b00a63b3899e4e4e88902f@buildbot.net>
#2700: 'grunt ci' fails, when install gets that far
-------------------+-------------------
Reporter: dustin | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.9.0
Version: 0.8.8 | Keywords:
-------------------+-------------------
Sometimes I see this, either on my system or on Travis:
{{{
running develop
running bower_install
running npm_install
npm install
rm -rf bower_components
./node_modules/.bin/bower install
bower angular-bootstrap#~0.6.0 cached git://github.com/angular-ui
/bootstrap-bower.git#0.6.0
bower angular-bootstrap#~0.6.0 validate 0.6.0 against
git://github.com/angular-ui/bootstrap-bower.git#~0.6.0
bower angular-mocks#v1.2.5 cached git://github.com/angular
/bower-angular-mocks.git#1.2.5
bower angular-mocks#v1.2.5 validate 1.2.5 against
git://github.com/angular/bower-angular-mocks.git#v1.2.5
bower font-awesome#4.0.3 cached
git://github.com/FortAwesome/Font-Awesome.git#4.0.3
bower font-awesome#4.0.3 validate 4.0.3 against
git://github.com/FortAwesome/Font-Awesome.git#4.0.3
bower moment#~2.1.0 cached
git://github.com/moment/moment.git#2.1.0
bower moment#~2.1.0 validate 2.1.0 against
git://github.com/moment/moment.git#~2.1.0
bower json2#* cached
git://github.com/douglascrockford/JSON-js.git#3d7767b6b1
bower json2#* validate 3d7767b6b1 against
git://github.com/douglascrockford/JSON-js.git#*
bower angular-animate#v1.2.5 cached git://github.com/angular
/bower-angular-animate.git#1.2.5
bower angular-animate#v1.2.5 validate 1.2.5 against
git://github.com/angular/bower-angular-animate.git#v1.2.5
bower angular#v1.2.5 cached git://github.com/angular
/bower-angular.git#1.2.5
bower angular#v1.2.5 validate 1.2.5 against
git://github.com/angular/bower-angular.git#v1.2.5
bower jquery#~2.0.0 cached
git://github.com/jquery/jquery.git#2.0.3
bower jquery#~2.0.0 validate 2.0.3 against
git://github.com/jquery/jquery.git#~2.0.0
bower html5shiv#~3.6.2 cached
git://github.com/aFarkas/html5shiv.git#3.6.2
bower html5shiv#~3.6.2 validate 3.6.2 against
git://github.com/aFarkas/html5shiv.git#~3.6.2
bower angular-ui-router#0.2.7 cached git://github.com/angular-
ui/ui-router.git#0.2.7
bower angular-ui-router#0.2.7 validate 0.2.7 against
git://github.com/angular-ui/ui-router.git#0.2.7
bower lodash#* cached
git://github.com/lodash/lodash.git#2.4.1
bower lodash#* validate 2.4.1 against
git://github.com/lodash/lodash.git#*
bower bootstrap#~3.0.0 cached
git://github.com/twbs/bootstrap.git#3.0.3
bower bootstrap#~3.0.0 validate 3.0.3 against
git://github.com/twbs/bootstrap.git#~3.0.0
bower requirejs#~2.1.5 cached git://github.com/jrburke
/requirejs-bower.git#2.1.11
bower requirejs#~2.1.5 validate 2.1.11 against
git://github.com/jrburke/requirejs-bower.git#~2.1.5
bower restangular#* cached
git://github.com/mgonto/restangular.git#1.3.1
bower restangular#* validate 1.3.1 against
git://github.com/mgonto/restangular.git#*
bower angular#>=1 cached git://github.com/angular
/bower-angular.git#1.2.13
bower angular#>=1 validate 1.2.13 against
git://github.com/angular/bower-angular.git#>=1
bower angular#>=1 new version for
git://github.com/angular/bower-angular.git#>=1
bower angular#>=1 resolve git://github.com/angular
/bower-angular.git#>=1
bower angular#1.2.5 cached git://github.com/angular
/bower-angular.git#1.2.5
bower angular#1.2.5 validate 1.2.5 against
git://github.com/angular/bower-angular.git#1.2.5
bower angular#>=1 download https://github.com/angular
/bower-angular/archive/v1.2.14-build.2273+sha.666137d.tar.gz
bower lodash#>=1.3.0 <2.5.0 cached
git://github.com/lodash/lodash.git#2.4.1
bower lodash#>=1.3.0 <2.5.0 validate 2.4.1 against
git://github.com/lodash/lodash.git#>=1.3.0 <2.5.0
bower angular#* cached git://github.com/angular
/bower-angular.git#1.2.13
bower angular#* validate 1.2.13 against
git://github.com/angular/bower-angular.git#*
bower angular#>= 1.1.5 cached git://github.com/angular
/bower-angular.git#1.2.13
bower angular#>= 1.1.5 validate 1.2.13 against
git://github.com/angular/bower-angular.git#>= 1.1.5
bower angular#>= 1.1.5 new version for
git://github.com/angular/bower-angular.git#>= 1.1.5
bower angular#>= 1.1.5 resolve git://github.com/angular
/bower-angular.git#>= 1.1.5
bower angular#>= 1.1.5 download https://github.com/angular
/bower-angular/archive/v1.2.14-build.2273+sha.666137d.tar.gz
bower jquery#>= 1.9.0 cached
git://github.com/jquery/jquery.git#2.1.0
bower jquery#>= 1.9.0 validate 2.1.0 against
git://github.com/jquery/jquery.git#>= 1.9.0
bower sizzle#1.10.16 cached
git://github.com/jquery/sizzle.git#1.10.16
bower sizzle#1.10.16 validate 1.10.16 against
git://github.com/jquery/sizzle.git#1.10.16
bower angular#>=1 extract archive.tar.gz
bower angular#>= 1.1.5 extract archive.tar.gz
bower angular#>= 1.1.5 resolved git://github.com/angular
/bower-angular.git#1.2.14-build.2273+sha.666137d
bower angular#>=1 ENOENT ENOENT, lstat
'/home/dustin/.cache/bower/packages/ef2188def21eb1bbd1f1792311942a53/1.2.14-build.2273%2Bsha.666137d/angular.js'
Stack trace:
/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules/fstream/lib/writer.js:284:26
Object.oncomplete (fs.js:107:15)
Console trace:
Trace
at StandardRenderer.error
(/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/lib/renderers/StandardRenderer.js:74:17)
at Logger.updateNotifier.packageName
(/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/bin/bower:109:18)
at Logger.EventEmitter.emit (events.js:95:17)
at Logger.emit
(/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules
/bower-logger/lib/Logger.js:29:39)
at
/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/lib/commands/install.js:27:16
at _rejected
(/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules/q/q.js:808:24)
at
/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules/q/q.js:834:30
at Promise.when
(/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules/q/q.js:1079:31)
at Promise.promise.promiseDispatch
(/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules/q/q.js:752:41)
at
/home/dustin/code/buildbot/t/buildbot/www/node_modules/bower/node_modules/q/q.js:574:44
System info:
Bower version: 1.2.8
Node version: 0.10.24
OS: Linux 3.10.25-gentoo-2014021101 x64
error: command './node_modules/.bin/bower' failed with exit status 1
}}}
But re-running without any changes may result in test failures:
{{{
PhantomJS 1.9.2 (Linux) buildbot service should query for changes at
/changes and receive an empty array FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at fetchFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1040)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:117
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10725
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10811
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11726
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11554
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/libs
/angular-mocks.js:1451
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:27
PhantomJS 1.9.2 (Linux) buildbot service should query for builds/1/steps/2
and receive a SUCCESS result FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at elemFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1107)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at getFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1161)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:126
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:168
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:188
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:39
PhantomJS 1.9.2 (Linux) buildbot service should query for builds/1/steps/2
mocked via dataspec FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at elemFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1107)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at getFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1161)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:126
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:168
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:188
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:48
PhantomJS 1.9.2 (Linux) buildbot service should query default scope_key to
route key FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at elemFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1107)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at getFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1161)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:126
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:168
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:188
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:60
PhantomJS 1.9.2 (Linux) buildbot service should update the $scope when
event received FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at elemFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1107)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at getFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1161)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:126
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:168
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:188
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:78
PhantomJS 1.9.2 (Linux) buildbot service should update the $scope when
event received for collections FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at fetchFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1040)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:117
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10725
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10811
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11726
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11554
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/libs
/angular-mocks.js:1451
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:110
PhantomJS 1.9.2 (Linux) buildbot service should update the $scope when
event received for collections with same id FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at fetchFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1040)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:117
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10725
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10811
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11726
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11554
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/libs
/angular-mocks.js:1451
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:139
PhantomJS 1.9.2 (Linux) buildbot service has a onchild api which should be
usable for restangular api FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at fetchFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1040)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:117
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10725
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10811
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11726
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11554
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/libs
/angular-mocks.js:1451
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:177
PhantomJS 1.9.2 (Linux) buildbot service has a bindHierarchy helper to
bind a hierarchy FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at elemFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1107)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at getFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1161)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:126
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:168
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:188
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:223
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:194
PhantomJS 1.9.2 (Linux) buildbot service should use one request for one
endpoint, take advantage of events to maintain
synchronisation FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at fetchFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1040)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:117
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10725
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10811
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11726
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11554
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/libs
/angular-mocks.js:1451
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:249
PhantomJS 1.9.2 (Linux) buildbot service should reload the data in case of
loss of synchronisation FAILED
TypeError:
at memoize
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:5561)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:27
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:36
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:206
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:463
at fetchFunction
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/restangular.js:1040)
at bound
(/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/lodash.js:729)
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/services/buildbotService.js:117
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10725
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:10811
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11726
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/libs/angular.js:11554
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/libs
/angular-mocks.js:1451
at
/home/dustin/code/buildbot/t/buildbot/www/buildbot_www/scripts/test/services/buildbotServiceSpec.js:293
PhantomJS 1.9.2 (Linux): Executed 22 of 22 (11 FAILED) (0.168 secs / 0.129
secs)
Warning: Task "karma:ci" failed. Use --force to continue.
Aborted due to warnings.
}}}
I haven't been able to bisect these warnings, as every version I've tried
(after re-running bower until it succeeds) either fails with these errors
or fails with
{{{
Warning: Unable to read "src/scripts/libs/angular-ui-router.js" file
(Error code: ENOENT). Use --force to continue.
}}}
which I believe is a result of a newer version of Angular being available
now than when that commit was made.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From noreply at github.com Mon Feb 17 22:26:08 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 14:26:08 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 82f14e: clean up steps:
LoggingBuildStep subclasses are al...
Message-ID: <53028c8010fb4_424acefd388871e@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 82f14ec680a630f50214df2a1d84694ccc678af0
https://github.com/buildbot/buildbot/commit/82f14ec680a630f50214df2a1d84694ccc678af0
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/docs/relnotes/index.rst
Log Message:
-----------
clean up steps: LoggingBuildStep subclasses are always old-style, ShellMixin is always new
Commit: 30953f523b5821e12323967f5dc9d75b761ac23a
https://github.com/buildbot/buildbot/commit/30953f523b5821e12323967f5dc9d75b761ac23a
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/process/remotecommand.py
M master/docs/developer/cls-remotecommands.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
make RemoteCommand able to handle old and new logfiles
Commit: 930c2b1ded8c03ddddaf6823994a41b5e88c8445
https://github.com/buildbot/buildbot/commit/930c2b1ded8c03ddddaf6823994a41b5e88c8445
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/process/remotecommand.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/docs/developer/cls-remotecommands.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
Merge djmitche/buildbot:9/use-data-api-8 (PR #1068)
Compare: https://github.com/buildbot/buildbot/compare/dff7724cf3ef...930c2b1ded8c
From noreply at github.com Mon Feb 17 22:32:42 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 14:32:42 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 80e97e: Removed bare excepts
Message-ID: <53028e0a83a9_2e1466dd342339e@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 80e97e301737550ebd6f2f91d102ed57abd140c5
https://github.com/buildbot/buildbot/commit/80e97e301737550ebd6f2f91d102ed57abd140c5
Author: Jonas Pommerening
Date: 2014-02-13 (Thu, 13 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
Log Message:
-----------
Removed bare excepts
Commit: b9a85da2efc77f011bb227e2f4a44cbf727b872c
https://github.com/buildbot/buildbot/commit/b9a85da2efc77f011bb227e2f4a44cbf727b872c
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
Log Message:
-----------
replaced "except as" syntax w/ 2.4 compatible comma syntax
Commit: 2f9e41343cc91cc0d3e7c212e2d0d4085bda878c
https://github.com/buildbot/buildbot/commit/2f9e41343cc91cc0d3e7c212e2d0d4085bda878c
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/fs.py
M slave/buildslave/test/unit/test_commands_base.py
Log Message:
-----------
replace assertions, raise ValueError instead
Commit: 2f1aba331fb65f6bb2646e502077e35ff645522f
https://github.com/buildbot/buildbot/commit/2f1aba331fb65f6bb2646e502077e35ff645522f
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
Log Message:
-----------
update steps to use requiredArgs
Commit: 4baf41dc5e1128061a3d68c219a744f8f0ab6b22
https://github.com/buildbot/buildbot/commit/4baf41dc5e1128061a3d68c219a744f8f0ab6b22
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/shell.py
M slave/buildslave/test/unit/test_bot.py
Log Message:
-----------
Fix failing test & shell command
Commit: d4b04b91583beb26102fe64c039e54787c2ecb89
https://github.com/buildbot/buildbot/commit/d4b04b91583beb26102fe64c039e54787c2ecb89
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
check rc in a callback (errback is not called)
Commit: ce52a890e16e1dcfce63b249d83f59e928fd9a56
https://github.com/buildbot/buildbot/commit/ce52a890e16e1dcfce63b249d83f59e928fd9a56
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
send headers and errno for failed fs commands
Commit: ed9c56b5243edc6a5ba60f1ba1b8bd9705686bb2
https://github.com/buildbot/buildbot/commit/ed9c56b5243edc6a5ba60f1ba1b8bd9705686bb2
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/test/unit/test_bot.py
Log Message:
-----------
removed blank line
Commit: 5399e6ce6c63d7eea732af87030dd2c084405637
https://github.com/buildbot/buildbot/commit/5399e6ce6c63d7eea732af87030dd2c084405637
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
M slave/buildslave/test/unit/test_bot.py
M slave/buildslave/test/unit/test_commands_base.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Merge jpommerening/buildbot:slave-fs-cmds-cleanup (PR #1066)
Compare: https://github.com/buildbot/buildbot/compare/9b7619020790...5399e6ce6c63
From noreply at github.com Mon Feb 17 22:36:37 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 14:36:37 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 80e97e: Removed bare excepts
Message-ID: <53028ef5999d4_4fe61353d3c249f5@hookshot-fe11-pe1-prd.aws.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 80e97e301737550ebd6f2f91d102ed57abd140c5
https://github.com/buildbot/buildbot/commit/80e97e301737550ebd6f2f91d102ed57abd140c5
Author: Jonas Pommerening
Date: 2014-02-13 (Thu, 13 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
Log Message:
-----------
Removed bare excepts
Commit: b9a85da2efc77f011bb227e2f4a44cbf727b872c
https://github.com/buildbot/buildbot/commit/b9a85da2efc77f011bb227e2f4a44cbf727b872c
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
Log Message:
-----------
replaced "except as" syntax w/ 2.4 compatible comma syntax
Commit: 2f9e41343cc91cc0d3e7c212e2d0d4085bda878c
https://github.com/buildbot/buildbot/commit/2f9e41343cc91cc0d3e7c212e2d0d4085bda878c
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/fs.py
M slave/buildslave/test/unit/test_commands_base.py
Log Message:
-----------
replace assertions, raise ValueError instead
Commit: 2f1aba331fb65f6bb2646e502077e35ff645522f
https://github.com/buildbot/buildbot/commit/2f1aba331fb65f6bb2646e502077e35ff645522f
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
Log Message:
-----------
update steps to use requiredArgs
Commit: 4baf41dc5e1128061a3d68c219a744f8f0ab6b22
https://github.com/buildbot/buildbot/commit/4baf41dc5e1128061a3d68c219a744f8f0ab6b22
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/shell.py
M slave/buildslave/test/unit/test_bot.py
Log Message:
-----------
Fix failing test & shell command
Commit: d4b04b91583beb26102fe64c039e54787c2ecb89
https://github.com/buildbot/buildbot/commit/d4b04b91583beb26102fe64c039e54787c2ecb89
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
check rc in a callback (errback is not called)
Commit: ce52a890e16e1dcfce63b249d83f59e928fd9a56
https://github.com/buildbot/buildbot/commit/ce52a890e16e1dcfce63b249d83f59e928fd9a56
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
send headers and errno for failed fs commands
Commit: ed9c56b5243edc6a5ba60f1ba1b8bd9705686bb2
https://github.com/buildbot/buildbot/commit/ed9c56b5243edc6a5ba60f1ba1b8bd9705686bb2
Author: Jonas Pommerening
Date: 2014-02-16 (Sun, 16 Feb 2014)
Changed paths:
M slave/buildslave/test/unit/test_bot.py
Log Message:
-----------
removed blank line
Commit: 5399e6ce6c63d7eea732af87030dd2c084405637
https://github.com/buildbot/buildbot/commit/5399e6ce6c63d7eea732af87030dd2c084405637
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
M slave/buildslave/test/unit/test_bot.py
M slave/buildslave/test/unit/test_commands_base.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Merge jpommerening/buildbot:slave-fs-cmds-cleanup (PR #1066)
Commit: 44efafac5c599b2f93be39e53b15fbb5b213aef5
https://github.com/buildbot/buildbot/commit/44efafac5c599b2f93be39e53b15fbb5b213aef5
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
M slave/buildslave/test/unit/test_bot.py
M slave/buildslave/test/unit/test_commands_base.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Merge branch 'master' into nine
Commit: a9be96f2ee417b2080ddff011f514f2dad828908
https://github.com/buildbot/buildbot/commit/a9be96f2ee417b2080ddff011f514f2dad828908
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M common/validate.sh
Log Message:
-----------
make 'grunt ci' failures a warning unti #2700 is fixed
Compare: https://github.com/buildbot/buildbot/compare/930c2b1ded8c...a9be96f2ee41
From noreply at github.com Mon Feb 17 23:16:05 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 15:16:05 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] e11444: add a
BuildStep.isNewStyle method
Message-ID: <53029835d93a_3c46d07d3426047@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: e114447a8273557a6f12f60ebf448de8a49e7ca2
https://github.com/buildbot/buildbot/commit/e114447a8273557a6f12f60ebf448de8a49e7ca2
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
add a BuildStep.isNewStyle method
Commit: 3c69dc49c1e21e17f243ca700ce837ef91fca3aa
https://github.com/buildbot/buildbot/commit/3c69dc49c1e21e17f243ca700ce837ef91fca3aa
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
M master/docs/manual/index.rst
A master/docs/manual/new-style-steps.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
relnotes for new-style steps
Commit: f14b3819718610ff2372b25dc70d8c0e9218627f
https://github.com/buildbot/buildbot/commit/f14b3819718610ff2372b25dc70d8c0e9218627f
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
Log Message:
-----------
support calling run on new-style steps
Commit: a22a87ceb809e31bf6f27cb5511f5a6b928f8615
https://github.com/buildbot/buildbot/commit/a22a87ceb809e31bf6f27cb5511f5a6b928f8615
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/buildslave/base.py
M master/buildbot/process/build.py
M master/buildbot/process/buildstep.py
M master/buildbot/test/fake/fakedb.py
M master/buildbot/test/fake/fakemaster.py
M master/buildbot/test/fake/slave.py
A master/buildbot/test/integration/test_custom_buildstep.py
M master/buildbot/test/unit/test_buildslave_base.py
M master/buildbot/test/unit/test_process_build.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/buildbot/test/unit/test_steps_slave.py
M master/buildbot/test/util/steps.py
M master/docs/developer/cls-buildsteps.rst
Log Message:
-----------
Integration tests for custom buildsteps (backport from nine)
This includes updates to fakes and interface tests for them
Compare: https://github.com/buildbot/buildbot/compare/5399e6ce6c63...a22a87ceb809
From noreply at github.com Mon Feb 17 23:16:06 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 15:16:06 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] e11444: add a
BuildStep.isNewStyle method
Message-ID: <530298367c88b_7d6e1133d4039883@hookshot-fe8-pe1-prd.aws.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: e114447a8273557a6f12f60ebf448de8a49e7ca2
https://github.com/buildbot/buildbot/commit/e114447a8273557a6f12f60ebf448de8a49e7ca2
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
add a BuildStep.isNewStyle method
Commit: f7ddb853b4c390ffa85051ecb717e4771bc51dc8
https://github.com/buildbot/buildbot/commit/f7ddb853b4c390ffa85051ecb717e4771bc51dc8
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
Merge branch 'master' into nine
Conflicts:
master/buildbot/process/buildstep.py
master/buildbot/test/unit/test_process_buildstep.py
Commit: 3c69dc49c1e21e17f243ca700ce837ef91fca3aa
https://github.com/buildbot/buildbot/commit/3c69dc49c1e21e17f243ca700ce837ef91fca3aa
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
M master/docs/manual/index.rst
A master/docs/manual/new-style-steps.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
relnotes for new-style steps
Commit: 540fb4fda3e711fc62209dd0fcc6762256e02451
https://github.com/buildbot/buildbot/commit/540fb4fda3e711fc62209dd0fcc6762256e02451
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
M master/docs/manual/index.rst
A master/docs/manual/new-style-steps.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
Merge branch 'master' into nine
(with minor modifications to documentation for nine)
Commit: f14b3819718610ff2372b25dc70d8c0e9218627f
https://github.com/buildbot/buildbot/commit/f14b3819718610ff2372b25dc70d8c0e9218627f
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
Log Message:
-----------
support calling run on new-style steps
Commit: c358328d1a356cee9f4ad72320cda93ff1277cbb
https://github.com/buildbot/buildbot/commit/c358328d1a356cee9f4ad72320cda93ff1277cbb
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Log Message:
-----------
Merge branch 'master' into nine
Commit: a22a87ceb809e31bf6f27cb5511f5a6b928f8615
https://github.com/buildbot/buildbot/commit/a22a87ceb809e31bf6f27cb5511f5a6b928f8615
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/buildslave/base.py
M master/buildbot/process/build.py
M master/buildbot/process/buildstep.py
M master/buildbot/test/fake/fakedb.py
M master/buildbot/test/fake/fakemaster.py
M master/buildbot/test/fake/slave.py
A master/buildbot/test/integration/test_custom_buildstep.py
M master/buildbot/test/unit/test_buildslave_base.py
M master/buildbot/test/unit/test_process_build.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/buildbot/test/unit/test_steps_slave.py
M master/buildbot/test/util/steps.py
M master/docs/developer/cls-buildsteps.rst
Log Message:
-----------
Integration tests for custom buildsteps (backport from nine)
This includes updates to fakes and interface tests for them
Commit: 53c58c6878da286a1a6f51cb7d447caf2c4cc783
https://github.com/buildbot/buildbot/commit/53c58c6878da286a1a6f51cb7d447caf2c4cc783
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/integration/test_custom_buildstep.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
Merge branch 'master' into nine
Compare: https://github.com/buildbot/buildbot/compare/a9be96f2ee41...53c58c6878da
From noreply at github.com Tue Feb 18 01:27:30 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 17:27:30 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] a0170b: fix pep8/pyflakes
Message-ID: <5302b70259dd2_4823ca1d40550fd@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: a0170babb8520531759b53d8bff6fba739294e89
https://github.com/buildbot/buildbot/commit/a0170babb8520531759b53d8bff6fba739294e89
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_buildslave_base.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
fix pep8/pyflakes
From noreply at github.com Tue Feb 18 01:36:30 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 17:36:30 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] a0170b: fix pep8/pyflakes
Message-ID: <5302b91e935a1_35e011dbd3810654a@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: a0170babb8520531759b53d8bff6fba739294e89
https://github.com/buildbot/buildbot/commit/a0170babb8520531759b53d8bff6fba739294e89
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_buildslave_base.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
fix pep8/pyflakes
Commit: f1c6a7b4b9977140ec079b892d18cc0768b5eea6
https://github.com/buildbot/buildbot/commit/f1c6a7b4b9977140ec079b892d18cc0768b5eea6
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
Log Message:
-----------
Merge branch 'master' into nine
Compare: https://github.com/buildbot/buildbot/compare/53c58c6878da...f1c6a7b4b997
From noreply at github.com Tue Feb 18 01:48:52 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 17:48:52 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 56621e: fix pylint
Message-ID: <5302bc045098d_49988b5d44378c0@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 56621ee2d3ca717f0c33991e9d6940e45ff54887
https://github.com/buildbot/buildbot/commit/56621ee2d3ca717f0c33991e9d6940e45ff54887
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_buildslave_base.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
fix pylint
From noreply at github.com Tue Feb 18 02:30:14 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 18:30:14 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 83f5ad: more pep8
Message-ID: <5302c5b696265_25a555dd407753b@hookshot-fe9-pe1-prd.aws.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 83f5ada793adfa1dfd6496601a03826c52ec95be
https://github.com/buildbot/buildbot/commit/83f5ada793adfa1dfd6496601a03826c52ec95be
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
more pep8
From noreply at github.com Tue Feb 18 03:14:03 2014
From: noreply at github.com (GitHub)
Date: Mon, 17 Feb 2014 19:14:03 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 2515aa: move tests for
buildbot.process.remotecommand to t...
Message-ID: <5302cffbe1991_3c10a5bd3869815@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 2515aa7e71e9dd5e54aff7c5103a90233ae8986a
https://github.com/buildbot/buildbot/commit/2515aa7e71e9dd5e54aff7c5103a90233ae8986a
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_process_buildstep.py
A master/buildbot/test/unit/test_process_remotecommand.py
Log Message:
-----------
move tests for buildbot.process.remotecommand to the appropriate module
From trac at buildbot.net Tue Feb 18 10:34:22 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 10:34:22 -0000
Subject: [Buildbot-commits] [Buildbot] #2649: [nine] i10n --
Localization Support
In-Reply-To: <038.f8b1dea62938a29434666bee74944d8f@buildbot.net>
References: <038.f8b1dea62938a29434666bee74944d8f@buildbot.net>
Message-ID: <053.8d1bfc433527bdaa2eb7dd00101db498@buildbot.net>
#2649: [nine] i10n -- Localization Support
-------------------+--------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: |
-------------------+--------------------
Comment (by tardyp):
This can be a good candidate for gsoc..
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 10:46:29 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 10:46:29 -0000
Subject: [Buildbot-commits] [Buildbot] #2652: [nine] Coordinate Messages
and Data
In-Reply-To: <038.08ad9025d103e16892c9a4c25f53586b@buildbot.net>
References: <038.08ad9025d103e16892c9a4c25f53586b@buildbot.net>
Message-ID: <053.57c3c1fd9fb50002ea9b3987c521396e@buildbot.net>
#2652: [nine] Coordinate Messages and Data
-------------------+--------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: |
-------------------+--------------------
Comment (by tardyp):
I think this problem should be documented, and for the moment have the
recommendation of not using db replication for now.
I think there is a need for numbers to know at which load threshold db
replication is really needed. On my own 0.8 setup, mysql load is barely
measurable, while my 3 masters are often 100% cpu.
At the moment, what is the implemented in most case is that the event is
built with the full data, for that kind, and the ui is using this and dont
go get the data again via data api. The problem would be for the child
details.
As a result, I would demote this task for post 0.9
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 11:17:06 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 11:17:06 -0000
Subject: [Buildbot-commits] [Buildbot] #2654: [nine] Handle build status
compatibly
In-Reply-To: <038.e53a6fa3c4fa9d09fdfd08bb3d1f5556@buildbot.net>
References: <038.e53a6fa3c4fa9d09fdfd08bb3d1f5556@buildbot.net>
Message-ID: <053.fa7a3cd952b1f3bc2d9e778b662c5483@buildbot.net>
#2654: [nine] Handle build status compatibly
-------------------+--------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: |
-------------------+--------------------
Comment (by tardyp):
on buildbot 0.8.x step have 2 way of stating their status as text
{{{
#!python
step.setText(list_of_strings)
}}}
This is the status text displayed in the step part of the UI. Some steps
are using description, and descriptionDone parameters to set respectively
the status when step is running, and when step has succeed.
{{{
#!python
step.setText2(list_of_strings)
}}}
This is the status text that is concatenated for the build part of the UI.
It is used in the top of a build part, but more importantly on the build
list (aka onelineperbuild) and allows to quickly see why this build
failed.
The build's status is the concatenation of
- build results as text: eg. Failed
- all steps's text2
As the build's status is a concatenation of possibly a number of steps's
text2. So this must be very concise, and set only if really needed.
I can see several problems to this approach.
- names are bad. text and text2 does not assess at all where this text
will be used in the UI
- having the step's text being a list of strings is confusing for custom
step writers. The type is not checked, and you'll often get bugs having
strings being automatically converted as list of single chars.. I don't
see a clear reason why we would keep the list of strings for state_strings
- You cannot quickly see which step wrote which state string, so that we
cannot make a nice mouseover UI over the list to have quick access to the
logs
As we already changed the step data in buildbot nine, I would propose the
following:
- change db backend to use state_string instead of state_strings
- keep setText() api, but " ".join() it if it is sent a list, and store
the text result in the data api
- mark setText2() api as deprecated
- change the state_strings format in the builds to be a dictionary
{{{
{
'global': "SUCCESS"
'': "make failed"
}
}}}
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 13:38:23 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 13:38:23 -0000
Subject: [Buildbot-commits] [Buildbot] #2649: [nine] i18n --
Internationalization (was: [nine] i10n -- Localization Support)
In-Reply-To: <038.f8b1dea62938a29434666bee74944d8f@buildbot.net>
References: <038.f8b1dea62938a29434666bee74944d8f@buildbot.net>
Message-ID: <053.06b1fc729de7b423fc5ee02ecba557cc@buildbot.net>
#2649: [nine] i18n -- Internationalization
-------------------------+--------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: |
-------------------------+--------------------
Changes (by dustin):
* type: task => project-idea
Old description:
> The Web UI should be localized.
> AngularJS ecosystem has ngTranslate project, which makes i18n relatively
> easy.
New description:
The Web UI should be localized.
AngularJS ecosystem has ngTranslate project, which makes i18n relatively
easy.
== scope ==
This project would require
* Learning about AngularJS and ngTranslate and how they are applied to an
application
* Applying ngTranslate to the Buildbot JS source code
* Documenting how to correctly use ngTranslate in new code
* Documenting the process for adding or updating a localization
* Testing translation
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 13:38:58 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 13:38:58 -0000
Subject: [Buildbot-commits] [Buildbot] #2652: [nine] Coordinate Messages
and Data
In-Reply-To: <038.08ad9025d103e16892c9a4c25f53586b@buildbot.net>
References: <038.08ad9025d103e16892c9a4c25f53586b@buildbot.net>
Message-ID: <053.ca3f35adc0be1ac837d359a07f2dd3e9@buildbot.net>
#2652: [nine] Coordinate Messages and Data
-------------------+--------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.+
Version: | Resolution:
Keywords: |
-------------------+--------------------
Changes (by dustin):
* milestone: 0.9.0 => 0.9.+
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 13:56:26 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 13:56:26 -0000
Subject: [Buildbot-commits] [Buildbot] #2651: [nine] Tracking for
Triggered Builds
In-Reply-To: <038.d570a297687ef9a1bd891eb4b24dca2e@buildbot.net>
References: <038.d570a297687ef9a1bd891eb4b24dca2e@buildbot.net>
Message-ID: <053.704846c694ec9e2e18c6590c146048bd@buildbot.net>
#2651: [nine] Tracking for Triggered Builds
-------------------+-----------------------
Reporter: dustin | Owner: tardyp
Type: task | Status: accepted
Priority: major | Milestone: 0.9.0
Version: | Resolution:
Keywords: |
-------------------+-----------------------
Changes (by tardyp):
* owner: => tardyp
* status: new => accepted
Comment:
Start working on that
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 14:26:17 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 14:26:17 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: elmirjagudin
Message-ID: <20140218142617.A95E211F935@buildbot-trac.community.scl3.mozilla.com>
New user registration for user elmirjagudin
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 15:08:54 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 15:08:54 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: cpsgfr
Message-ID: <20140218150854.4744511FA66@buildbot-trac.community.scl3.mozilla.com>
New user registration for user cpsgfr
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 15:48:07 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 15:48:07 -0000
Subject: [Buildbot-commits] [Buildbot] #2701: problems removing running
builders
Message-ID: <044.0c44554906d4f2b5334188e839dd02de@buildbot.net>
#2701: problems removing running builders
-------------------------+-----------------------
Reporter: elmirjagudin | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords:
-------------------------+-----------------------
Buildbot does not seem to handle removal and renaming of running builders
properly.
When a builder is removed from master.cfg while it is running on some
slave, it looks like buildbot tries to abort it. However it seems like it
fails to do that properly. The builder will be listed as running on that
slave indefinitely. Same issue is encountered when a builder is renamed,
as buildbot will remove a builder with the old name and add a builder with
new name.
Below are contents of slave's twisted.log, when a builder 'hellox' is
renamed to 'helloy' in master.cfg and 'buildbot reconfig' is run:
{{{
2014-02-13 15:34:10+0100 [Broker,client] stopCommand: halting current
command
2014-02-13 15:34:10+0100 [Broker,client] command interrupted, attempting
to kill
2014-02-13 15:34:10+0100 [Broker,client] trying to kill process group
20112
2014-02-13 15:34:10+0100 [Broker,client] signal 9 sent successfully
2014-02-13 15:34:10+0100 [Broker,client] I have a leftover directory
'hellox' that is not being used by the buildmaster: you can delete it now
2014-02-13 15:34:10+0100 [-] command finished with signal 9, exit code
None, elapsedTime: 9.045442
2014-02-13 15:34:10+0100 [-] would sendStatus but not .running
2014-02-13 15:34:10+0100 [-] SlaveBuilder.commandComplete None
2014-02-13 15:34:10+0100 [-] but we weren't running, quitting silently
2014-02-13 15:34:10+0100 [Broker,client]
SlaveBuilder.remote_print(helloy): message from master: attached
}}}
It is possible to restore the slave with 'buildslave restart', however
following is printed in master's twisted.log when the slave reconnects:
{{{
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1]
BuildSlave.detached(example-slave)
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] releaseLocks(): []
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] Buildslave example-slave
detached from helloy
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] .lostRemote
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] stopping currentStep
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] addCompleteLog(interrupt)
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] RemoteCommand.interrupt
[Failure instance: Traceback
(failure with no frames): : Connection to the other side
was lost in a non-clean fashion.
]
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] RemoteCommand.disconnect:
lost slave
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1]
releaseLocks(): []
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] step 'shell' complete:
retry
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] : build
finished
2014-02-13 15:37:55+0100 [Broker,0,127.0.0.1] from a running build; this
is a serious error - please file a bug at http://buildbot.net
Traceback (most recent call last):
File "/home/elmir/remblds/src/master/buildbot/process/build.py",
line 519, in allStepsDone
return self.buildFinished(text, self.result)
File "/home/elmir/remblds/src/master/buildbot/process/build.py",
line 558, in buildFinished
self.deferred.callback(self)
File
"/home/elmir/remblds/sandbox/local/lib/python2.7/site-
packages/twisted/internet/defer.py",
line 382, in callback
self._startRunCallbacks(result)
File
"/home/elmir/remblds/sandbox/local/lib/python2.7/site-
packages/twisted/internet/defer.py",
line 490, in _startRunCallbacks
self._runCallbacks()
--- ---
File
"/home/elmir/remblds/sandbox/local/lib/python2.7/site-
packages/twisted/internet/defer.py",
line 577, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File
"/home/elmir/remblds/src/master/buildbot/process/builder.py", line 455,
in buildFinished
d = self.master.db.builds.finishBuilds(bids)
exceptions.AttributeError: 'NoneType' object has no attribute 'db'
2014-02-13 15:37:55+0100 [Broker,1,127.0.0.1] slave 'example-slave'
attaching from IPv4Address(TCP, '127.0.0.1', 54965)
2014-02-13 15:37:55+0100 [Broker,1,127.0.0.1] Got slaveinfo from
'example-slave'
2014-02-13 15:37:55+0100 [Broker,1,127.0.0.1] Starting buildslave
keepalive timer for 'example-slave'
2014-02-13 15:37:55+0100 [Broker,1,127.0.0.1] bot attached
2014-02-13 15:37:57+0100 [Broker,1,127.0.0.1] Buildslave example-slave
attached to helloy
}}}
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 18 16:31:44 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 18 Feb 2014 16:31:44 -0000
Subject: [Buildbot-commits] [Buildbot] #2699: Changes not shown in
filtered waterfall view
In-Reply-To: <041.24a3e4d72aad25093c9dd012c9aa4dfb@buildbot.net>
References: <041.24a3e4d72aad25093c9dd012c9aa4dfb@buildbot.net>
Message-ID: <056.c7a450f460eaa49329cdc5bf8ac341e9@buildbot.net>
#2699: Changes not shown in filtered waterfall view
----------------------+--------------------
Reporter: friedgold | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: web |
----------------------+--------------------
Comment (by friedgold):
Replying to [comment:1 dustin]:
> I suspect that the waterfall view is filtering both builders and changes
using the given category, even though those are two unrelated sets of
categories. So unless your changes happen to have category 'config', you
won't see them.
>
> Does that match what you're seeing?
Yes, that matches what I'm seeing, thanks for the explanation. Having a
way categorize builders separately to changes would be good.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 19 20:13:15 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 19 Feb 2014 20:13:15 -0000
Subject: [Buildbot-commits] [Buildbot] #2702: Inform the user if wrong
SQLAlchemy is installed
Message-ID: <038.69c037eba7b2c0565deaaf311db57633@buildbot.net>
#2702: Inform the user if wrong SQLAlchemy is installed
------------------------+----------------------
Reporter: dustin | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.8 | Keywords: database
------------------------+----------------------
If a too-new version of SQLAlchemy is installed, Buildbot doesn't give a
very clear error message.
It'd be great to be able to catch this early enough in the startup process
to give a good error message. That may be tricky since the
incompatibility between SQLAlchemy and SQLAlchemy-Migrate occurs during
the imports.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 20 14:02:06 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 20 Feb 2014 14:02:06 -0000
Subject: [Buildbot-commits] [Buildbot] #1929: refactor
BotMaster.cleanShutdown
In-Reply-To: <038.8e3bf05e4c72fcd375f458b0c6548227@buildbot.net>
References: <038.8e3bf05e4c72fcd375f458b0c6548227@buildbot.net>
Message-ID: <053.ee98f9851bced3dd8c13ec40eba79113@buildbot.net>
#1929: refactor BotMaster.cleanShutdown
--------------------+--------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: minor | Milestone: 0.9.+
Version: 0.8.3p1 | Resolution:
Keywords: |
--------------------+--------------------
Changes (by tardyp):
* type: enhancement => task
Comment:
buck started working on this but was interrupted, and will probably dont
finish it.
The work is nearly done, and has some small minor fix needed
https://github.com/buildbot/buildbot/pull/861
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 20 16:50:34 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 20 Feb 2014 16:50:34 -0000
Subject: [Buildbot-commits] [Buildbot] #2703: handle step interruption
properly
Message-ID: <038.2be206ca7559e82532a21325c04d7119@buildbot.net>
#2703: handle step interruption properly
-------------------+-------------------
Reporter: tardyp | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.0
Version: master | Keywords:
-------------------+-------------------
There are some subtleties to handle step interrupts.
For shellcommands this works, but for master steps its more complex.
especially trigger would need special attention.
djmitche, in the case of a new style step, how are you supposed
to interrupt a step?
?? tardyp converting Trigger to new style..
<+djmitche> tardyp: has that changed?
well if I run interrupt(), we are in the middle of run(), which
would be yielding someting
old style step would just call self.finished() so can skip
waiting
<+djmitche> interrupt will also interrupt a running command
<+djmitche> so this is only a problem when run() isn't executing a command
I realize that trigger's interrupt is badly written
it should cancel the requests
and stop the builds
<+djmitche> yes
<+djmitche> there should be some instructions for step authors who are not
just executing commands to poll self.stopped or something like that
the first is easy, end the second need the stop rpc
<+djmitche> also, initiating a new command after an interrupt should
immediately fail
<+djmitche> I don't think it necessarily should stop the triggered builds
well, we have hacks to do so, as my user were requesting this
loud
<+djmitche> what if those requests got merged?
it make sense to release the buildfarm, when like use a single
build can trigger douzens of parralel builds
the algo is to claim_cancel the buildrequests first
then if the buildrequests are claimed, get to the build status
and stop it
<+djmitche> I suppose if we're collapsing requests instead, then if the
request was collapsed, you just don't cancel a build
so I believe this works with the collapsing
<+djmitche> yeah
if it is callapsed then its claimed
<+djmitche> as long as it's via the data API I think that's OK :)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 21 21:56:30 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 21 Feb 2014 21:56:30 -0000
Subject: [Buildbot-commits] [Buildbot] #2701: problems removing running
builders
In-Reply-To: <044.0c44554906d4f2b5334188e839dd02de@buildbot.net>
References: <044.0c44554906d4f2b5334188e839dd02de@buildbot.net>
Message-ID: <059.9d7b938ce360ea06b5f913544ad67c7a@buildbot.net>
#2701: problems removing running builders
-------------------------+--------------------
Reporter: elmirjagudin | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: |
-------------------------+--------------------
Changes (by dustin):
* type: undecided => defect
* milestone: undecided => 0.8.+
Comment:
This may not be an issue in nine, but needs to be fixed in 0.8.x
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From noreply at github.com Fri Feb 21 22:14:55 2014
From: noreply at github.com (GitHub)
Date: Fri, 21 Feb 2014 14:14:55 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 2831f2: Added a 'glob'
command to the slave.
Message-ID: <5307cfdf43340_40c1e71d3c37719@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 2831f244505a04c77412912107065b522ce820c8
https://github.com/buildbot/buildbot/commit/2831f244505a04c77412912107065b522ce820c8
Author: Jonas Pommerening
Date: 2013-11-19 (Tue, 19 Nov 2013)
Changed paths:
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/registry.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Added a 'glob' command to the slave.
Can be used to retrieve a list of files from the slave that match
a given pattern. (This is somewhat more portable than using shell
expansion.)
Custom steps can use this command to add filenames to a property
of the build where they may be later picked up by an uploading step.
RemoteCommand('glob', dict(path='[Bb]uild[Bb]ot-*', workdir='wkdir'))
Commit: d9a1069aaeb1c8dc8822058f0d2e8ee15bc8db1c
https://github.com/buildbot/buildbot/commit/d9a1069aaeb1c8dc8822058f0d2e8ee15bc8db1c
Author: Jonas Pommerening
Date: 2013-11-19 (Tue, 19 Nov 2013)
Changed paths:
M slave/buildslave/commands/fs.py
Log Message:
-----------
pep8 (so close)
Commit: 87cca9206357533d2a8809d479d9bd8b036b1f57
https://github.com/buildbot/buildbot/commit/87cca9206357533d2a8809d479d9bd8b036b1f57
Author: Jonas Pommerening
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M .travis.yml
M CONTRIBUTING.md
M common/pylintrc
M common/validate.sh
M master/buildbot/buildslave/base.py
M master/buildbot/buildslave/ec2.py
M master/buildbot/changes/base.py
M master/buildbot/changes/bonsaipoller.py
M master/buildbot/changes/gerritchangesource.py
M master/buildbot/changes/gitpoller.py
R master/buildbot/changes/hgbuildbot.py
M master/buildbot/changes/hgpoller.py
M master/buildbot/changes/mail.py
M master/buildbot/changes/p4poller.py
M master/buildbot/changes/svnpoller.py
M master/buildbot/clients/tryclient.py
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
M master/buildbot/process/build.py
M master/buildbot/process/buildstep.py
A master/buildbot/process/logobserver.py
A master/buildbot/process/remotecommand.py
M master/buildbot/process/slavebuilder.py
M master/buildbot/process/users/manual.py
M master/buildbot/schedulers/trysched.py
M master/buildbot/scripts/logwatcher.py
M master/buildbot/scripts/start.py
M master/buildbot/status/base.py
M master/buildbot/status/client.py
M master/buildbot/status/mail.py
M master/buildbot/status/master.py
M master/buildbot/status/slave.py
M master/buildbot/status/status_push.py
M master/buildbot/status/tinderbox.py
M master/buildbot/status/web/base.py
M master/buildbot/status/web/baseweb.py
M master/buildbot/status/web/build.py
M master/buildbot/status/web/feeds.py
M master/buildbot/status/web/grid.py
M master/buildbot/status/web/hooks/github.py
M master/buildbot/status/web/templates/feed_description.html
M master/buildbot/status/web/templates/grid_macros.html
M master/buildbot/status/web/waterfall.py
M master/buildbot/steps/maxq.py
M master/buildbot/steps/package/deb/lintian.py
M master/buildbot/steps/shell.py
M master/buildbot/steps/source/base.py
M master/buildbot/steps/source/bzr.py
M master/buildbot/steps/source/cvs.py
M master/buildbot/steps/source/darcs.py
M master/buildbot/steps/source/git.py
M master/buildbot/steps/source/mercurial.py
M master/buildbot/steps/source/mtn.py
M master/buildbot/steps/source/oldsource.py
M master/buildbot/steps/source/p4.py
M master/buildbot/steps/source/repo.py
M master/buildbot/steps/source/svn.py
M master/buildbot/steps/transfer.py
M master/buildbot/steps/vstudio.py
A master/buildbot/test/integration/test_try_client.py
M master/buildbot/test/regressions/test_shell_command_properties.py
M master/buildbot/test/test_extra_coverage.py
M master/buildbot/test/unit/test_changes_base.py
M master/buildbot/test/unit/test_changes_gerritchangesource.py
M master/buildbot/test/unit/test_changes_gitpoller.py
M master/buildbot/test/unit/test_changes_hgpoller.py
M master/buildbot/test/unit/test_changes_mail_CVSMaildirSource.py
M master/buildbot/test/unit/test_process_build.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/buildbot/test/unit/test_schedulers_timed_NightlyBase.py
M master/buildbot/test/unit/test_status_mail.py
M master/buildbot/test/unit/test_status_web_hooks_github.py
M master/buildbot/test/unit/test_steps_source_bzr.py
M master/buildbot/test/unit/test_steps_source_cvs.py
M master/buildbot/test/unit/test_steps_source_darcs.py
M master/buildbot/test/unit/test_steps_source_git.py
M master/buildbot/test/unit/test_steps_source_mercurial.py
M master/buildbot/test/unit/test_steps_source_mtn.py
M master/buildbot/test/unit/test_steps_source_p4.py
M master/buildbot/test/unit/test_steps_source_repo.py
M master/buildbot/test/unit/test_steps_source_svn.py
M master/buildbot/test/unit/test_steps_transfer.py
M master/buildbot/test/unit/test_util.py
M master/buildbot/test/util/sourcesteps.py
M master/buildbot/test/util/steps.py
M master/buildbot/util/__init__.py
A master/contrib/hgbuildbot.py
A master/contrib/systemd/buildbot.service
R master/docs/_images/header-text-transparent.png
M master/docs/conf.py
M master/docs/developer/utils.rst
A master/docs/header-text-transparent.png
M master/docs/manual/cfg-buildslaves.rst
M master/docs/manual/cfg-buildsteps.rst
M master/docs/manual/cfg-changesources.rst
M master/docs/manual/cfg-statustargets.rst
M master/docs/manual/cmdline.rst
M master/docs/manual/customization.rst
M master/docs/manual/installation.rst
M master/docs/relnotes/0.8.6.rst
M master/docs/relnotes/index.rst
M master/setup.py
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
M slave/buildslave/scripts/logwatcher.py
M slave/buildslave/test/unit/test_bot.py
M slave/buildslave/test/unit/test_commands_base.py
M slave/buildslave/test/unit/test_commands_fs.py
A slave/contrib/systemd/buildslave.service
Log Message:
-----------
Merge branch 'slave-fs-cmds-cleanup' into slave-glob-command
* slave-fs-cmds-cleanup: (148 commits)
removed blank line
send headers and errno for failed fs commands
check rc in a callback (errback is not called)
Fix failing test & shell command
update steps to use requiredArgs
replace assertions, raise ValueError instead
replaced "except as" syntax w/ 2.4 compatible comma syntax
Removed bare excepts
apply 09749e7 to master
On solaris use the tail in /usr/xpg4/bin/tail insteaf of /usr/bin/tail which does not support the -n option
Do not catch GeneratorExit exception
remove use of MutableMapping, not in Python 2.5
Ignore decoding errors in atom/rss feeds; fixes #951
Fix step None bug
sphinx doesn't seem to support relative paths for logos anymore
fix typo in comment
Add systemd unit for slave.
Add systemd service unit for master.
add whitespace to avoid failure with Sphinx-1.2.1
Fix failures where 'git clean' fails but could be clobbered
...
Commit: 32f314e6c488e1b0e03e54a6d485c7da52e71b03
https://github.com/buildbot/buildbot/commit/32f314e6c488e1b0e03e54a6d485c7da52e71b03
Author: Jonas Pommerening
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Incorporate improvements from #1066
* rename sent updates `glob` -> `files` (as in ListDir)
* drop the asserts, use base.Command.requiredArgs
* catch only OSError (even that one is quite unlikely to appear) and
send the appropriate `rc` to master
* rename `globpath` -> `globname` (as in the python docs:
http://docs.python.org/2/library/glob.html)
Commit: 052e273c154c1b2bda4a9686305f9462465c9cbb
https://github.com/buildbot/buildbot/commit/052e273c154c1b2bda4a9686305f9462465c9cbb
Author: Jonas Pommerening
Date: 2014-02-18 (Tue, 18 Feb 2014)
Changed paths:
M master/docs/developer/master-slave.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
Added relnote, developer doc
Commit: 277072e1d66c23a93c1a247b07eb825e57ed91c8
https://github.com/buildbot/buildbot/commit/277072e1d66c23a93c1a247b07eb825e57ed91c8
Author: Jonas Pommerening
Date: 2014-02-18 (Tue, 18 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/buildbot/test/unit/test_steps_slave.py
Log Message:
-----------
Added runGlob to CompositeStepMixin
Commit: 29f5f6dda8f10475c980f5c19c30d29feb32db8b
https://github.com/buildbot/buildbot/commit/29f5f6dda8f10475c980f5c19c30d29feb32db8b
Author: Jonas Pommerening
Date: 2014-02-18 (Tue, 18 Feb 2014)
Changed paths:
M master/docs/relnotes/index.rst
Log Message:
-----------
Mention CompositeStepMixin.runGlob in relnotes
Commit: 119aab92568ca01ead1417c7867c5091f0debe5d
https://github.com/buildbot/buildbot/commit/119aab92568ca01ead1417c7867c5091f0debe5d
Author: Jonas Pommerening
Date: 2014-02-19 (Wed, 19 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/docs/manual/customization.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
Added manual/docs, fixed reference in releasenotes
Commit: c68bbb9f0b9b8973ff28b59039f93d945e3bd831
https://github.com/buildbot/buildbot/commit/c68bbb9f0b9b8973ff28b59039f93d945e3bd831
Author: Dustin J. Mitchell
Date: 2014-02-21 (Fri, 21 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/buildbot/test/unit/test_steps_slave.py
M master/docs/developer/master-slave.rst
M master/docs/manual/customization.rst
M master/docs/relnotes/index.rst
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/registry.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Merge jpommerening/buildbot:slave-glob-command (PR #970)
+autopep8
Compare: https://github.com/buildbot/buildbot/compare/2515aa7e71e9...c68bbb9f0b9b
From noreply at github.com Fri Feb 21 22:29:59 2014
From: noreply at github.com (GitHub)
Date: Fri, 21 Feb 2014 14:29:59 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 9bd021: fix docs
Message-ID: <5307d367204d1_1cb6ab9d3491373@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 9bd02182a50095eb055f6bd3b4fe77ca703961d8
https://github.com/buildbot/buildbot/commit/9bd02182a50095eb055f6bd3b4fe77ca703961d8
Author: Dustin J. Mitchell
Date: 2014-02-21 (Fri, 21 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
Log Message:
-----------
fix docs
From noreply at github.com Sat Feb 22 20:16:34 2014
From: noreply at github.com (GitHub)
Date: Sat, 22 Feb 2014 12:16:34 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 2831f2: Added a 'glob'
command to the slave.
Message-ID: <530905a2462f7_23466c1d447287@hookshot-fe7-pe1-prd.aws.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 2831f244505a04c77412912107065b522ce820c8
https://github.com/buildbot/buildbot/commit/2831f244505a04c77412912107065b522ce820c8
Author: Jonas Pommerening
Date: 2013-11-19 (Tue, 19 Nov 2013)
Changed paths:
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/registry.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Added a 'glob' command to the slave.
Can be used to retrieve a list of files from the slave that match
a given pattern. (This is somewhat more portable than using shell
expansion.)
Custom steps can use this command to add filenames to a property
of the build where they may be later picked up by an uploading step.
RemoteCommand('glob', dict(path='[Bb]uild[Bb]ot-*', workdir='wkdir'))
Commit: d9a1069aaeb1c8dc8822058f0d2e8ee15bc8db1c
https://github.com/buildbot/buildbot/commit/d9a1069aaeb1c8dc8822058f0d2e8ee15bc8db1c
Author: Jonas Pommerening
Date: 2013-11-19 (Tue, 19 Nov 2013)
Changed paths:
M slave/buildslave/commands/fs.py
Log Message:
-----------
pep8 (so close)
Commit: 87cca9206357533d2a8809d479d9bd8b036b1f57
https://github.com/buildbot/buildbot/commit/87cca9206357533d2a8809d479d9bd8b036b1f57
Author: Jonas Pommerening
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M .travis.yml
M CONTRIBUTING.md
M common/pylintrc
M common/validate.sh
M master/buildbot/buildslave/base.py
M master/buildbot/buildslave/ec2.py
M master/buildbot/changes/base.py
M master/buildbot/changes/bonsaipoller.py
M master/buildbot/changes/gerritchangesource.py
M master/buildbot/changes/gitpoller.py
R master/buildbot/changes/hgbuildbot.py
M master/buildbot/changes/hgpoller.py
M master/buildbot/changes/mail.py
M master/buildbot/changes/p4poller.py
M master/buildbot/changes/svnpoller.py
M master/buildbot/clients/tryclient.py
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
M master/buildbot/process/build.py
M master/buildbot/process/buildstep.py
A master/buildbot/process/logobserver.py
A master/buildbot/process/remotecommand.py
M master/buildbot/process/slavebuilder.py
M master/buildbot/process/users/manual.py
M master/buildbot/schedulers/trysched.py
M master/buildbot/scripts/logwatcher.py
M master/buildbot/scripts/start.py
M master/buildbot/status/base.py
M master/buildbot/status/client.py
M master/buildbot/status/mail.py
M master/buildbot/status/master.py
M master/buildbot/status/slave.py
M master/buildbot/status/status_push.py
M master/buildbot/status/tinderbox.py
M master/buildbot/status/web/base.py
M master/buildbot/status/web/baseweb.py
M master/buildbot/status/web/build.py
M master/buildbot/status/web/feeds.py
M master/buildbot/status/web/grid.py
M master/buildbot/status/web/hooks/github.py
M master/buildbot/status/web/templates/feed_description.html
M master/buildbot/status/web/templates/grid_macros.html
M master/buildbot/status/web/waterfall.py
M master/buildbot/steps/maxq.py
M master/buildbot/steps/package/deb/lintian.py
M master/buildbot/steps/shell.py
M master/buildbot/steps/source/base.py
M master/buildbot/steps/source/bzr.py
M master/buildbot/steps/source/cvs.py
M master/buildbot/steps/source/darcs.py
M master/buildbot/steps/source/git.py
M master/buildbot/steps/source/mercurial.py
M master/buildbot/steps/source/mtn.py
M master/buildbot/steps/source/oldsource.py
M master/buildbot/steps/source/p4.py
M master/buildbot/steps/source/repo.py
M master/buildbot/steps/source/svn.py
M master/buildbot/steps/transfer.py
M master/buildbot/steps/vstudio.py
A master/buildbot/test/integration/test_try_client.py
M master/buildbot/test/regressions/test_shell_command_properties.py
M master/buildbot/test/test_extra_coverage.py
M master/buildbot/test/unit/test_changes_base.py
M master/buildbot/test/unit/test_changes_gerritchangesource.py
M master/buildbot/test/unit/test_changes_gitpoller.py
M master/buildbot/test/unit/test_changes_hgpoller.py
M master/buildbot/test/unit/test_changes_mail_CVSMaildirSource.py
M master/buildbot/test/unit/test_process_build.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/buildbot/test/unit/test_schedulers_timed_NightlyBase.py
M master/buildbot/test/unit/test_status_mail.py
M master/buildbot/test/unit/test_status_web_hooks_github.py
M master/buildbot/test/unit/test_steps_source_bzr.py
M master/buildbot/test/unit/test_steps_source_cvs.py
M master/buildbot/test/unit/test_steps_source_darcs.py
M master/buildbot/test/unit/test_steps_source_git.py
M master/buildbot/test/unit/test_steps_source_mercurial.py
M master/buildbot/test/unit/test_steps_source_mtn.py
M master/buildbot/test/unit/test_steps_source_p4.py
M master/buildbot/test/unit/test_steps_source_repo.py
M master/buildbot/test/unit/test_steps_source_svn.py
M master/buildbot/test/unit/test_steps_transfer.py
M master/buildbot/test/unit/test_util.py
M master/buildbot/test/util/sourcesteps.py
M master/buildbot/test/util/steps.py
M master/buildbot/util/__init__.py
A master/contrib/hgbuildbot.py
A master/contrib/systemd/buildbot.service
R master/docs/_images/header-text-transparent.png
M master/docs/conf.py
M master/docs/developer/utils.rst
A master/docs/header-text-transparent.png
M master/docs/manual/cfg-buildslaves.rst
M master/docs/manual/cfg-buildsteps.rst
M master/docs/manual/cfg-changesources.rst
M master/docs/manual/cfg-statustargets.rst
M master/docs/manual/cmdline.rst
M master/docs/manual/customization.rst
M master/docs/manual/installation.rst
M master/docs/relnotes/0.8.6.rst
M master/docs/relnotes/index.rst
M master/setup.py
M slave/buildslave/commands/base.py
M slave/buildslave/commands/bk.py
M slave/buildslave/commands/bzr.py
M slave/buildslave/commands/cvs.py
M slave/buildslave/commands/darcs.py
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/git.py
M slave/buildslave/commands/hg.py
M slave/buildslave/commands/mtn.py
M slave/buildslave/commands/p4.py
M slave/buildslave/commands/repo.py
M slave/buildslave/commands/shell.py
M slave/buildslave/commands/svn.py
M slave/buildslave/commands/transfer.py
M slave/buildslave/scripts/logwatcher.py
M slave/buildslave/test/unit/test_bot.py
M slave/buildslave/test/unit/test_commands_base.py
M slave/buildslave/test/unit/test_commands_fs.py
A slave/contrib/systemd/buildslave.service
Log Message:
-----------
Merge branch 'slave-fs-cmds-cleanup' into slave-glob-command
* slave-fs-cmds-cleanup: (148 commits)
removed blank line
send headers and errno for failed fs commands
check rc in a callback (errback is not called)
Fix failing test & shell command
update steps to use requiredArgs
replace assertions, raise ValueError instead
replaced "except as" syntax w/ 2.4 compatible comma syntax
Removed bare excepts
apply 09749e7 to master
On solaris use the tail in /usr/xpg4/bin/tail insteaf of /usr/bin/tail which does not support the -n option
Do not catch GeneratorExit exception
remove use of MutableMapping, not in Python 2.5
Ignore decoding errors in atom/rss feeds; fixes #951
Fix step None bug
sphinx doesn't seem to support relative paths for logos anymore
fix typo in comment
Add systemd unit for slave.
Add systemd service unit for master.
add whitespace to avoid failure with Sphinx-1.2.1
Fix failures where 'git clean' fails but could be clobbered
...
Commit: 32f314e6c488e1b0e03e54a6d485c7da52e71b03
https://github.com/buildbot/buildbot/commit/32f314e6c488e1b0e03e54a6d485c7da52e71b03
Author: Jonas Pommerening
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M slave/buildslave/commands/fs.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Incorporate improvements from #1066
* rename sent updates `glob` -> `files` (as in ListDir)
* drop the asserts, use base.Command.requiredArgs
* catch only OSError (even that one is quite unlikely to appear) and
send the appropriate `rc` to master
* rename `globpath` -> `globname` (as in the python docs:
http://docs.python.org/2/library/glob.html)
Commit: 56621ee2d3ca717f0c33991e9d6940e45ff54887
https://github.com/buildbot/buildbot/commit/56621ee2d3ca717f0c33991e9d6940e45ff54887
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_buildslave_base.py
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
fix pylint
Commit: 83f5ada793adfa1dfd6496601a03826c52ec95be
https://github.com/buildbot/buildbot/commit/83f5ada793adfa1dfd6496601a03826c52ec95be
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_process_buildstep.py
Log Message:
-----------
more pep8
Commit: 2515aa7e71e9dd5e54aff7c5103a90233ae8986a
https://github.com/buildbot/buildbot/commit/2515aa7e71e9dd5e54aff7c5103a90233ae8986a
Author: Dustin J. Mitchell
Date: 2014-02-17 (Mon, 17 Feb 2014)
Changed paths:
M master/buildbot/test/unit/test_process_buildstep.py
A master/buildbot/test/unit/test_process_remotecommand.py
Log Message:
-----------
move tests for buildbot.process.remotecommand to the appropriate module
Commit: 052e273c154c1b2bda4a9686305f9462465c9cbb
https://github.com/buildbot/buildbot/commit/052e273c154c1b2bda4a9686305f9462465c9cbb
Author: Jonas Pommerening
Date: 2014-02-18 (Tue, 18 Feb 2014)
Changed paths:
M master/docs/developer/master-slave.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
Added relnote, developer doc
Commit: 277072e1d66c23a93c1a247b07eb825e57ed91c8
https://github.com/buildbot/buildbot/commit/277072e1d66c23a93c1a247b07eb825e57ed91c8
Author: Jonas Pommerening
Date: 2014-02-18 (Tue, 18 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/buildbot/test/unit/test_steps_slave.py
Log Message:
-----------
Added runGlob to CompositeStepMixin
Commit: 29f5f6dda8f10475c980f5c19c30d29feb32db8b
https://github.com/buildbot/buildbot/commit/29f5f6dda8f10475c980f5c19c30d29feb32db8b
Author: Jonas Pommerening
Date: 2014-02-18 (Tue, 18 Feb 2014)
Changed paths:
M master/docs/relnotes/index.rst
Log Message:
-----------
Mention CompositeStepMixin.runGlob in relnotes
Commit: 119aab92568ca01ead1417c7867c5091f0debe5d
https://github.com/buildbot/buildbot/commit/119aab92568ca01ead1417c7867c5091f0debe5d
Author: Jonas Pommerening
Date: 2014-02-19 (Wed, 19 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/docs/manual/customization.rst
M master/docs/relnotes/index.rst
Log Message:
-----------
Added manual/docs, fixed reference in releasenotes
Commit: c68bbb9f0b9b8973ff28b59039f93d945e3bd831
https://github.com/buildbot/buildbot/commit/c68bbb9f0b9b8973ff28b59039f93d945e3bd831
Author: Dustin J. Mitchell
Date: 2014-02-21 (Fri, 21 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/buildbot/test/unit/test_steps_slave.py
M master/docs/developer/master-slave.rst
M master/docs/manual/customization.rst
M master/docs/relnotes/index.rst
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/registry.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Merge jpommerening/buildbot:slave-glob-command (PR #970)
+autopep8
Commit: 9bd02182a50095eb055f6bd3b4fe77ca703961d8
https://github.com/buildbot/buildbot/commit/9bd02182a50095eb055f6bd3b4fe77ca703961d8
Author: Dustin J. Mitchell
Date: 2014-02-21 (Fri, 21 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
Log Message:
-----------
fix docs
Commit: 62b1491303ac06d49b0e8d6c004a9e738c12ca3a
https://github.com/buildbot/buildbot/commit/62b1491303ac06d49b0e8d6c004a9e738c12ca3a
Author: Dustin J. Mitchell
Date: 2014-02-22 (Sat, 22 Feb 2014)
Changed paths:
M master/buildbot/steps/slave.py
M master/buildbot/test/unit/test_process_remotecommand.py
M master/buildbot/test/unit/test_steps_slave.py
M master/docs/developer/master-slave.rst
M master/docs/manual/customization.rst
M master/docs/relnotes/index.rst
M slave/buildslave/commands/fs.py
M slave/buildslave/commands/registry.py
M slave/buildslave/test/unit/test_commands_fs.py
Log Message:
-----------
Merge branch 'master' into nine
Conflicts:
master/buildbot/test/unit/test_process_buildstep.py
master/buildbot/test/unit/test_process_remotecommand.py
Compare: https://github.com/buildbot/buildbot/compare/f1c6a7b4b997...62b1491303ac
From noreply at github.com Sat Feb 22 21:00:36 2014
From: noreply at github.com (GitHub)
Date: Sat, 22 Feb 2014 13:00:36 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 4d5f34: port glob to
CommandMixin
Message-ID: <53090ff4bde0e_2897d6bd3435553@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 4d5f34f0646ebb4540123a490cd03a3e5e9f1efd
https://github.com/buildbot/buildbot/commit/4d5f34f0646ebb4540123a490cd03a3e5e9f1efd
Author: Dustin J. Mitchell
Date: 2014-02-22 (Sat, 22 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_process_buildstep.py
M master/docs/developer/cls-buildsteps.rst
Log Message:
-----------
port glob to CommandMixin
From trac at buildbot.net Sun Feb 23 13:32:21 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 23 Feb 2014 13:32:21 -0000
Subject: [Buildbot-commits] [Buildbot] #2702: Inform the user if wrong
SQLAlchemy is installed
In-Reply-To: <038.69c037eba7b2c0565deaaf311db57633@buildbot.net>
References: <038.69c037eba7b2c0565deaaf311db57633@buildbot.net>
Message-ID: <053.3963cb25e2013d448d9058cd67e2aef9@buildbot.net>
#2702: Inform the user if wrong SQLAlchemy is installed
------------------------+--------------------
Reporter: dustin | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: database |
------------------------+--------------------
Comment (by dustin):
https://github.com/buildbot/buildbot/pull/1075
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From noreply at github.com Sun Feb 23 14:16:28 2014
From: noreply at github.com (GitHub)
Date: Sun, 23 Feb 2014 06:16:28 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] a8bc7f: update github webhook
Message-ID: <530a02bc69dd7_38157b5d40203ee@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: a8bc7fd008f511af735c51cfeaa5dfc3c920a594
https://github.com/buildbot/buildbot/commit/a8bc7fd008f511af735c51cfeaa5dfc3c920a594
Author: Sam Kleinman
Date: 2014-02-20 (Thu, 20 Feb 2014)
Changed paths:
M master/contrib/github_buildbot.py
Log Message:
-----------
update github webhook
Commit: d0538284abe503943e92668fbcc4a1307c4eabf3
https://github.com/buildbot/buildbot/commit/d0538284abe503943e92668fbcc4a1307c4eabf3
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/contrib/github_buildbot.py
Log Message:
-----------
Merge tychoish/buildbot:github-hook-update (PR #1073)
Compare: https://github.com/buildbot/buildbot/compare/9bd02182a500...d0538284abe5
From trac at buildbot.net Sun Feb 23 14:17:06 2014
From: trac at buildbot.net (Buildbot trac)
Date: Sun, 23 Feb 2014 14:17:06 -0000
Subject: [Buildbot-commits] [Buildbot] #2703: handle step interruption
properly
In-Reply-To: <038.2be206ca7559e82532a21325c04d7119@buildbot.net>
References: <038.2be206ca7559e82532a21325c04d7119@buildbot.net>
Message-ID: <053.b795d42a65df3594476d7375bebfbd59@buildbot.net>
#2703: handle step interruption properly
-------------------+--------------------
Reporter: tardyp | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.9.0
Version: master | Resolution:
Keywords: |
-------------------+--------------------
Description changed by dustin:
Old description:
> There are some subtleties to handle step interrupts.
>
> For shellcommands this works, but for master steps its more complex.
> especially trigger would need special attention.
>
> djmitche, in the case of a new style step, how are you supposed
> to interrupt a step?
> ?? tardyp converting Trigger to new style..
> <+djmitche> tardyp: has that changed?
> well if I run interrupt(), we are in the middle of run(), which
> would be yielding someting
> old style step would just call self.finished() so can skip
> waiting
> <+djmitche> interrupt will also interrupt a running command
> <+djmitche> so this is only a problem when run() isn't executing a
> command
> I realize that trigger's interrupt is badly written
> it should cancel the requests
> and stop the builds
> <+djmitche> yes
> <+djmitche> there should be some instructions for step authors who are
> not just executing commands to poll self.stopped or something like that
> the first is easy, end the second need the stop rpc
> <+djmitche> also, initiating a new command after an interrupt should
> immediately fail
> <+djmitche> I don't think it necessarily should stop the triggered builds
> well, we have hacks to do so, as my user were requesting this
> loud
> <+djmitche> what if those requests got merged?
> it make sense to release the buildfarm, when like use a single
> build can trigger douzens of parralel builds
> the algo is to claim_cancel the buildrequests first
> then if the buildrequests are claimed, get to the build status
> and stop it
> <+djmitche> I suppose if we're collapsing requests instead, then if the
> request was collapsed, you just don't cancel a build
> so I believe this works with the collapsing
> <+djmitche> yeah
> if it is callapsed then its claimed
> <+djmitche> as long as it's via the data API I think that's OK :)
New description:
There are some subtleties to handle step interrupts.
For shellcommands this works, but for master steps its more complex.
especially trigger would need special attention.
{{{
djmitche, in the case of a new style step, how are you supposed
to interrupt a step?
?? tardyp converting Trigger to new style..
<+djmitche> tardyp: has that changed?
well if I run interrupt(), we are in the middle of run(), which
would be yielding someting
old style step would just call self.finished() so can skip
waiting
<+djmitche> interrupt will also interrupt a running command
<+djmitche> so this is only a problem when run() isn't executing a command
I realize that trigger's interrupt is badly written
it should cancel the requests
and stop the builds
<+djmitche> yes
<+djmitche> there should be some instructions for step authors who are not
just executing commands to poll self.stopped or something like that
the first is easy, end the second need the stop rpc
<+djmitche> also, initiating a new command after an interrupt should
immediately fail
<+djmitche> I don't think it necessarily should stop the triggered builds
well, we have hacks to do so, as my user were requesting this
loud
<+djmitche> what if those requests got merged?
it make sense to release the buildfarm, when like use a single
build can trigger douzens of parralel builds
the algo is to claim_cancel the buildrequests first
then if the buildrequests are claimed, get to the build status
and stop it
<+djmitche> I suppose if we're collapsing requests instead, then if the
request was collapsed, you just don't cancel a build
so I believe this works with the collapsing
<+djmitche> yeah
if it is callapsed then its claimed
<+djmitche> as long as it's via the data API I think that's OK :)
}}}
--
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From noreply at github.com Sun Feb 23 18:18:46 2014
From: noreply at github.com (GitHub)
Date: Sun, 23 Feb 2014 10:18:46 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 1750af: Warn the user with a
nice message if the version o...
Message-ID: <530a3b866f3b0_36e450fd3424225@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 1750afb3cd05a9da79bff768afe818c9098ae196
https://github.com/buildbot/buildbot/commit/1750afb3cd05a9da79bff768afe818c9098ae196
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
Log Message:
-----------
Warn the user with a nice message if the version of SQLAlchemy is too new
Commit: cd9297749a9d5cb566127df0d0ac3e0ae06ab2b0
https://github.com/buildbot/buildbot/commit/cd9297749a9d5cb566127df0d0ac3e0ae06ab2b0
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
Log Message:
-----------
Merge djmitche/buildbot:bug2702 (PR #1075)
Compare: https://github.com/buildbot/buildbot/compare/d0538284abe5...cd9297749a9d
From noreply at github.com Sun Feb 23 18:20:11 2014
From: noreply at github.com (GitHub)
Date: Sun, 23 Feb 2014 10:20:11 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] a8bc7f: update github webhook
Message-ID: <530a3bdb2230f_349813bbd3866084@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: a8bc7fd008f511af735c51cfeaa5dfc3c920a594
https://github.com/buildbot/buildbot/commit/a8bc7fd008f511af735c51cfeaa5dfc3c920a594
Author: Sam Kleinman
Date: 2014-02-20 (Thu, 20 Feb 2014)
Changed paths:
M master/contrib/github_buildbot.py
Log Message:
-----------
update github webhook
Commit: 1750afb3cd05a9da79bff768afe818c9098ae196
https://github.com/buildbot/buildbot/commit/1750afb3cd05a9da79bff768afe818c9098ae196
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
Log Message:
-----------
Warn the user with a nice message if the version of SQLAlchemy is too new
Commit: d0538284abe503943e92668fbcc4a1307c4eabf3
https://github.com/buildbot/buildbot/commit/d0538284abe503943e92668fbcc4a1307c4eabf3
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/contrib/github_buildbot.py
Log Message:
-----------
Merge tychoish/buildbot:github-hook-update (PR #1073)
Commit: cd9297749a9d5cb566127df0d0ac3e0ae06ab2b0
https://github.com/buildbot/buildbot/commit/cd9297749a9d5cb566127df0d0ac3e0ae06ab2b0
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
Log Message:
-----------
Merge djmitche/buildbot:bug2702 (PR #1075)
Commit: 6a467d2ef5fcb9de7cc793ec34e7959f941414bb
https://github.com/buildbot/buildbot/commit/6a467d2ef5fcb9de7cc793ec34e7959f941414bb
Author: Dustin J. Mitchell
Date: 2014-02-23 (Sun, 23 Feb 2014)
Changed paths:
M master/buildbot/db/enginestrategy.py
M master/buildbot/db/model.py
M master/contrib/github_buildbot.py
Log Message:
-----------
Merge branch 'master' into nine
Compare: https://github.com/buildbot/buildbot/compare/4d5f34f0646e...6a467d2ef5fc
From trac at buildbot.net Mon Feb 24 14:36:27 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 24 Feb 2014 14:36:27 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: varun
Message-ID: <20140224143627.0A8A411FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user varun
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 24 16:14:05 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 24 Feb 2014 16:14:05 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: MichaelHomo
Message-ID: <20140224161405.BAA9A11FA66@buildbot-trac.community.scl3.mozilla.com>
New user registration for user MichaelHomo
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 24 17:54:40 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 24 Feb 2014 17:54:40 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: jpommerening
Message-ID: <20140224175440.1CB0411FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user jpommerening
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 24 18:28:40 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 24 Feb 2014 18:28:40 -0000
Subject: [Buildbot-commits] [Buildbot] #2607: A lot of broken links and
Jenkins instance in SuccessStories
In-Reply-To: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
References: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
Message-ID: <051.72a3ba26283f365a8a2e247dfb4e1ef4@buildbot.net>
#2607: A lot of broken links and Jenkins instance in SuccessStories
---------------------+----------------------
Reporter: hgen | Owner:
Type: defect | Status: new
Priority: critical | Milestone: ongoing
Version: 0.8.8 | Resolution:
Keywords: |
---------------------+----------------------
Comment (by jpommerening):
Here's the broken links ? hope I didn't miss any?
* Monotone: http://buildbot.monotone.ca/
* Subversion: http://www.mobsol.be/buildbot/
* FTEQW: http://triptohell.info:65533/
* Gstreamer: http://build.fluendo.com:8080
* Free Geek: http://cvs.freegeek.org/buildbot/
* Spamassassin: http://buildbot.spamassassin.org:8010 (Jenkins ->
http://wiki.apache.org/spamassassin/ContinuousTesting)
* Boost: http://build.redshift-software.com:9990
* arkadas: http://mono.ximian.com:8008
* Nuxeo (Jenkins -> http://www.nuxeo.com/en/developers)
* Logicalware: http://www.logicalware.org/buildbot/
* Xenomai: http://ngiger.dyndns.org/buildbot/
* Aqsis: http://build.aqsis.org:8010
* Enfold Systems: http://buildbot.enfoldsystems.com
* Cheesecake: http://agilistas.org:8888
* Armagetron Advanced: http://waterfall.davefancella.com
* GHC: http://darcs.haskell.org/buildbot/all/
* OpenOffice: http://termite.services.openoffice.org/buildbot/
* Jython: http://freya.cs.uiuc.edu:8009/waterfall
* OpenSG: http://opensg.vrsource.org/trac/tracbb
* OpenPlans: http://buildbot.openplans.org
* Gentoo: http://buildbot.gentooext.net
* NuFW: http://buildbot.inl.fr/
* sipXecs: http://sipxecs.sipfoundry.org/build
* Kusu: http://build.osgdc.org
* Tamarin: http://tamarin-builds.mozilla.org
* ES4: http://buildbot.ecmascript.org
* Darcs: http://buildbot.darcs.net
* Drizzle: http://drizzlebuild.42sql.com
* PyAMF: http://build.pyamf.org
* Parrot: http://buildbot.eigenstate.net:8040
* ScummVM: http://buildbot.scummvm.org/buildbot/waterfall
* EDE: http://build.equinox-project.org/
* Clementine: http://clementine.davidsansome.com/buildbot/
* Songbird: http://buildbot.songbirdnest.com/buildbot?category=trunk
* Paintown: http://crystalis.cs.utah.edu:8010/waterfall
* Reu2: http://dreamtrack.dnsalias.com:19990/waterfall
* OpenERP: http://test.openobject.com:8010
* Node.js: http://jenkins.nodejs.org (Ouch)
* NA61/SHINE: http://dory.ung.si:8010
* Yocto Project: http://autobuilder.yoctoproject.org:8010
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Mon Feb 24 21:51:31 2014
From: trac at buildbot.net (Buildbot trac)
Date: Mon, 24 Feb 2014 21:51:31 -0000
Subject: [Buildbot-commits] [Buildbot] #2607: A lot of broken links and
Jenkins instance in SuccessStories
In-Reply-To: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
References: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
Message-ID: <051.c023ca48dac4fec7e493b358087c75ed@buildbot.net>
#2607: A lot of broken links and Jenkins instance in SuccessStories
---------------------+----------------------
Reporter: hgen | Owner:
Type: defect | Status: new
Priority: critical | Milestone: ongoing
Version: 0.8.8 | Resolution:
Keywords: |
---------------------+----------------------
Comment (by dustin):
Sweet - can you edit the wiki to reflect that?
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 02:39:35 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 02:39:35 -0000
Subject: [Buildbot-commits] [Buildbot] #2692: Auto-generate some
documentation
In-Reply-To: <038.9bb0a3648358c7f5228dc8977d4abb7d@buildbot.net>
References: <038.9bb0a3648358c7f5228dc8977d4abb7d@buildbot.net>
Message-ID: <053.83dfe450ac17a3cb3d06788deb133f3f@buildbot.net>
#2692: Auto-generate some documentation
-------------------------+--------------------
Reporter: dustin | Owner:
Type: project-idea | Status: new
Priority: major | Milestone: 0.9.+
Version: | Resolution:
Keywords: docs |
-------------------------+--------------------
Changes (by dustin):
* cc: keikun (added)
Comment:
This could also involve automatically documenting step parameters, as
suggested by KeiKun.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 02:46:55 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 02:46:55 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Ronalddymn
Message-ID: <20140225024655.DB6C411FA66@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Ronalddymn
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 04:27:25 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 04:27:25 -0000
Subject: [Buildbot-commits] [Buildbot] #2704: github status is pushed twice
Message-ID: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
#2704: github status is pushed twice
----------------------+-----------------------
Reporter: liucougar | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: master | Keywords:
----------------------+-----------------------
by looking at the log file, it seems for every build which triggers github
status, both the start status (started) and finish status (success etc)
are sent twice to github
if I use github api to query the status for a particular revision, I can
see there are are 2 start status (both with the same timestamp), then 2
finish status (both with the same timestamp)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 10:10:07 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 10:10:07 -0000
Subject: [Buildbot-commits] [Buildbot] Password reset for user: jpommerening
Message-ID: <20140225101007.3BC7F11FAD5@buildbot-trac.community.scl3.mozilla.com>
Password reset for user for user jpommerening
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 10:10:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 10:10:46 -0000
Subject: [Buildbot-commits] [Buildbot] Password reset for user: jpommerening
Message-ID: <20140225101046.EC75611FAD5@buildbot-trac.community.scl3.mozilla.com>
Password reset for user for user jpommerening
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 10:43:00 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 10:43:00 -0000
Subject: [Buildbot-commits] [Buildbot] #2607: A lot of broken links and
Jenkins instance in SuccessStories
In-Reply-To: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
References: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
Message-ID: <051.9c4faf405859bee26131c7cc07124258@buildbot.net>
#2607: A lot of broken links and Jenkins instance in SuccessStories
---------------------+----------------------
Reporter: hgen | Owner:
Type: defect | Status: new
Priority: critical | Milestone: ongoing
Version: 0.8.8 | Resolution:
Keywords: |
---------------------+----------------------
Comment (by jpommerening):
Sure!
I just discovered some moved Buildbot Instances, so for these I just
updated the links:
* ScummVM: http://buildbot.scummvm.org/waterfall
* Subversion: http://ci.apache.org/waterfall?&show=bb-openbsd&show=svn-
windows-local&show=svn-windows-ra&show=svn-trunk-rat-report&show=svn-x64
-centos-gcc&show=svn-x64-ubuntu-gcc&show=svn-backport-conflicts-1.7.x&show
=svn-backport-conflicts-1.8.x&show=svn-warnings&show_events=true&
The SVN Buildbot is just a partial view of http://ci.apache.org which
hosts quite a lot more projects. Maybe someone can get in touch with them
and find out what's going on there?
Anyway, I edited the page and moved all dead links to a big comment block
at the bottom of the page. There's still plenty buildbots running.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 11:09:19 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 11:09:19 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: JosephTiC
Message-ID: <20140225110919.094CB11FA66@buildbot-trac.community.scl3.mozilla.com>
New user registration for user JosephTiC
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 12:29:43 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 12:29:43 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: bettyehill
Message-ID: <20140225122943.20BE511FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user bettyehill
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 13:27:39 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 13:27:39 -0000
Subject: [Buildbot-commits] [Buildbot] #2607: A lot of broken links and
Jenkins instance in SuccessStories
In-Reply-To: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
References: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
Message-ID: <051.d2084f0ef8decd3c2a6f013354f6c993@buildbot.net>
#2607: A lot of broken links and Jenkins instance in SuccessStories
---------------------+----------------------
Reporter: hgen | Owner:
Type: defect | Status: new
Priority: critical | Milestone: ongoing
Version: 0.8.8 | Resolution:
Keywords: |
---------------------+----------------------
Comment (by dustin):
You rock - thanks!
Regarding Apache, I'll see if I can get in touch with Gavin McDonald,
although I'm not sure he's still the best person.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 13:31:03 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 13:31:03 -0000
Subject: [Buildbot-commits] [Buildbot] #2607: A lot of broken links and
Jenkins instance in SuccessStories
In-Reply-To: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
References: <036.1308bf05191fe2b1bb42c2ba657aa945@buildbot.net>
Message-ID: <051.b9046a87822ec71e0ec325e730b898f0@buildbot.net>
#2607: A lot of broken links and Jenkins instance in SuccessStories
---------------------+----------------------
Reporter: hgen | Owner:
Type: defect | Status: closed
Priority: critical | Milestone: ongoing
Version: 0.8.8 | Resolution: fixed
Keywords: |
---------------------+----------------------
Changes (by dustin):
* status: new => closed
* resolution: => fixed
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 13:55:01 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 13:55:01 -0000
Subject: [Buildbot-commits] [Buildbot] #2704: github status is pushed
twice
In-Reply-To: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
References: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
Message-ID: <056.598b2b6106f39a74345f023244b235ae@buildbot.net>
#2704: github status is pushed twice
----------------------+------------------------
Reporter: liucougar | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: master | Resolution:
Keywords: |
----------------------+------------------------
Comment (by dustin):
But there's only one status listener configured in your setup?
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 15:31:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 15:31:46 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: AnthonynaPt
Message-ID: <20140225153146.6B55C11F83D@buildbot-trac.community.scl3.mozilla.com>
New user registration for user AnthonynaPt
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Tue Feb 25 21:23:31 2014
From: trac at buildbot.net (Buildbot trac)
Date: Tue, 25 Feb 2014 21:23:31 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: PafpannaNot
Message-ID: <20140225212331.2425F11FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user PafpannaNot
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 07:44:54 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 07:44:54 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration:
garrettpinckneyrk0
Message-ID: <20140226074454.962FD11F83D@buildbot-trac.community.scl3.mozilla.com>
New user registration for user garrettpinckneyrk0
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 10:43:32 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 10:43:32 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: BaliDon121
Message-ID: <20140226104332.E493911FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user BaliDon121
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 10:45:31 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 10:45:31 -0000
Subject: [Buildbot-commits] [Buildbot] #2705: skin care 5
Message-ID: <042.233eaacf3595b770a0af225f6956a20c@buildbot.net>
#2705: skin care 5
-----------------------+-----------------------
Reporter: BaliDon121 | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords: Amacari
-----------------------+-----------------------
the most affected product on the market forgetting rant lines and wrinkles
this actually used to be spoke mostly used %uh for Acme because it?s so
effective on acne I'll and that I then he to realize I that is just as a
factor on lines and wrinkles it?s amazing I am this is the .1 percent red
meat products usually common I about the restraints when
I started using[http://amacariantiaging.org/ Amacari] this I used the
lowest and I worked my way up to the point one which is the highest and
that's kind of what you want to do with friendly products because you need
your skin to build up a tolerance them because there is some redness and
some peeling I associated with that first which is completely fine
completely normal you want that you that's just going to help you bring
youknow get the best results so Obama this is again air and a not to be
confused with right now products only people all are confused about the
right now and the right name
http://amacariantiaging.org/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 11:37:16 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 11:37:16 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Ronniest
Message-ID: <20140226113716.1B3A411F83D@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Ronniest
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 13:36:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 13:36:48 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: pvalsecc
Message-ID: <20140226133648.65CFC11FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user pvalsecc
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 13:42:43 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 13:42:43 -0000
Subject: [Buildbot-commits] [Buildbot] #2076: GitPoller initiates bad
builds
In-Reply-To: <038.5f411c78e97ea8d9f82e20dc29b61751@buildbot.net>
References: <038.5f411c78e97ea8d9f82e20dc29b61751@buildbot.net>
Message-ID: <053.13be885bb5f42738b6e6cfe4eed9bf62@buildbot.net>
#2076: GitPoller initiates bad builds
----------------------------+----------------------
Reporter: dwyerk | Owner:
Type: support-request | Status: new
Priority: major | Milestone: ongoing
Version: 0.8.4p2 | Resolution:
Keywords: |
----------------------------+----------------------
Comment (by pvalsecc):
There is no such option as treeStableTimer in GitPoller. So your
workaround doesn't work.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 13:48:19 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 13:48:19 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Rullcive
Message-ID: <20140226134819.F196E11FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Rullcive
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 14:48:51 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 14:48:51 -0000
Subject: [Buildbot-commits] [Buildbot] #2076: GitPoller initiates bad
builds
In-Reply-To: <038.5f411c78e97ea8d9f82e20dc29b61751@buildbot.net>
References: <038.5f411c78e97ea8d9f82e20dc29b61751@buildbot.net>
Message-ID: <053.e3ce4d22534e966ba3aaf2fcc2c1515e@buildbot.net>
#2076: GitPoller initiates bad builds
----------------------------+----------------------
Reporter: dwyerk | Owner:
Type: support-request | Status: new
Priority: major | Milestone: ongoing
Version: 0.8.4p2 | Resolution:
Keywords: |
----------------------------+----------------------
Old description:
> I have a git repo with two branches, master and stable. I have configured
> one GitPoller to watch for changes on master. Master and stable have
> diverged in some serious ways, but most of the time it's still possible
> and preferable to merge a change from stable into master.
>
> When I make a change to stable and merge it to master, GitPoller triggers
> two builds. The first is based off of the commit hash for the original
> change to stable, and the second is based off of the commit hash for the
> merge. The first build will always fail because the Git buildstep will
> reset the repo to stable's hash, and the rest of the steps will not be
> able to find the files that they expect, since they were setup to build
> master, not stable.
>
> The second build will work, because it resets the repo to the merge
> commit, which is a state that actually exists on the master branch.
>
> So is this a supported configuration? In this case, what I really want
> GitPoller to do is ignore that first build, since the hash doesn't refer
> to the branch that GitPoller is supposed to be watching.
New description:
I have a git repo with two branches, master and stable. I have configured
one GitPoller to watch for changes on master. Master and stable have
diverged in some serious ways, but most of the time it's still possible
and preferable to merge a change from stable into master.
When I make a change to stable and merge it to master, GitPoller triggers
two builds. The first is based off of the commit hash for the original
change to stable, and the second is based off of the commit hash for the
merge. The first build will always fail because the Git buildstep will
reset the repo to stable's hash, and the rest of the steps will not be
able to find the files that they expect, since they were setup to build
master, not stable.
The second build will work, because it resets the repo to the merge
commit, which is a state that actually exists on the master branch.
So is this a supported configuration? In this case, what I really want
GitPoller to do is ignore that first build, since the hash doesn't refer
to the branch that GitPoller is supposed to be watching.
--
Comment (by dustin):
It's a scheduler option, not a poller option.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 16:43:48 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 16:43:48 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: niketnrequins
Message-ID: <20140226164348.E01CF11FAF1@buildbot-trac.community.scl3.mozilla.com>
New user registration for user niketnrequins
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 18:29:53 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 18:29:53 -0000
Subject: [Buildbot-commits] [Buildbot] Password reset for user: jpommerening
Message-ID: <20140226182953.84E3F11FAD5@buildbot-trac.community.scl3.mozilla.com>
Password reset for user for user jpommerening
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 18:41:57 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 18:41:57 -0000
Subject: [Buildbot-commits] [Buildbot] #739: HTML logs are included in
pickles
In-Reply-To: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
References: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
Message-ID: <054.f1e4601e505b129b9a70a50920230184@buildbot.net>
#739: HTML logs are included in pickles
---------------------+--------------------
Reporter: marcusl | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 0.8.+
Version: 0.7.12 | Resolution:
Keywords: sprint |
---------------------+--------------------
Comment (by jpommerening):
Hey! I'm working on a fix: https://github.com/buildbot/buildbot/pull/1077
The main problem with HTML-logs (in my opinion) is that they can not (yet)
be streamed from the slaves. So if you have a 5MB log, you first have to
collect the whole contents into an enormous string and pass it to
`BuildStepStatus.addHTMLLog`. The fact that it will stay in memory and
will stay there for as long as the whole `BuildStatus` instance lives only
makes matters worse.
OTOH, for small stack traces like the `err.html`, keeping them in memory
may be the way to go?
Another thing I'm not really comfortable with is the way the `HTMLLogFile`
class serves as a kind of hint for the web status to handle it
differently.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 20:27:41 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 20:27:41 -0000
Subject: [Buildbot-commits] [Buildbot] #2706: Handling test results
Message-ID: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
#2706: Handling test results
-------------------------+-------------------
Reporter: jpommerening | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Keywords:
-------------------------+-------------------
Me again?
I'm currently working on integrating our test results with the BuildBot
web-frontend and mail notifications. I discovered the "halfway there"
implementation consisting of `BuildStatus.addTestResult` some unfinished
web views etc. and thought now would be a good opportunity to tackle that
problem.
I already whipped up a little proof-of-concept based on 0.8.8 and am now
looking to clean up some rough edges and learn how make the right
extensions to nine's the data api (?).
'''First: What's there already?'''
[https://github.com/buildbot/buildbot/blob/master/master/buildbot/interfaces.py#L595
ITestResult]: Everything that is known about a single test case: Its name
(a tuple of strings), result, a string/text further describing the result,
a dictionary (string->string) of logs.
[https://github.com/buildbot/buildbot/blob/master/master/buildbot/interfaces.py#L577
IBuildStatus.getTestResults]: Returns all test results for the given
build, keeping `ITestResult` per name (where name is
`ITestResult.getName()`).
[https://github.com/buildbot/buildbot/blob/master/master/buildbot/status/web/tests.py
StatusResourceBuildTest]: a web view that can display the result and logs
of a single test case.
'''What do I want to contribute?'''
1. `ILogObserver` implementations for incrementally parsing test result
logs
* SubunitLogObserver ? already there
* JUnitLogObserver ? parse incrementally with defusedxml (I'll port my
lxml-based implementation)
* TAPLogObserver ? can someone point me to a python library for that?
* are there any other wide spread formats?
2. I want to replace the dictionary with a list (possible upgrade hazard?)
* currently the test results are in whatever order the dictionary deems
right, the list would assure chronological order
* Allows duplicate names, I'll have to see how to handle that in the
ui. I actually think this is needed for data-driven tests (a single
method, multiple datasets that are tested within the same test, multiple
results).
3. A "click-through/drill-down" web interface to navigate test results on
0.8.x (#1794)
* linked on the build-status page in the "Result" section with number
of passed and failed tests (#536)
* tests results grouped by common prefix of the name tuple (one page
per "level")
* maybe a "proportionally split bar" style visualization of failed vs.
passed tests
4. hook it up in nine
* I have no idea what that means, can someone point me in the right
direction?
(each of these steps may come as a separate pull request on github)
'''Why is this important?'''
This may not yet be the final solution but I think it is a step in the
right direction. Buildbot is all about CI and proper integration of test
tools should be a big part of that. Right now the whole test result thing
is kind of in stealth mode ? I didn't know about it until last week,
despite having worked with Buildbot for about 2 years. The changes I want
to make would show that there '''is''' a feature like that and maybe
inspire discussion and ideas for improving it.
'''What feedback do I need?'''
Can I go ahead and change `getTestResults` to return a list?
What changes are needed for nine?
Do you have any suggestions, things I should consider, etc?
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 20:43:06 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 20:43:06 -0000
Subject: [Buildbot-commits] [Buildbot] #2706: Handling test results
In-Reply-To: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
References: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
Message-ID: <059.b0812112d593a0c6a8b9d8393ed01ec6@buildbot.net>
#2706: Handling test results
-------------------------+--------------------
Reporter: jpommerening | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: |
-------------------------+--------------------
Comment (by dustin):
This is a great idea!
The existing code for handling test results is, as far as I know,
completely inoperative. So you should feel free to throw that out.
The big danger here is an explosion of data. If you have thousands of
builds (as most users do) and each build has thousands of tests (as most
test runs do), that's millions of test-result rows. It's a lot more for a
larger-than-average installation. If we're sending a message for each new
test result, that's also a lot of messages. We've done some work with log
handling in nine to try to reduce this (by collapsing multiple log lines
into a single database record, and compressing it).
I don't think there's a lot of sense in implementing this in 0.8.x, unless
you're planning to simultaneously re-implement it in nine. At this point
the branches have diverged significantly, and I can't promise to re-
implement any new 0.8.x functionality in nine. This would be a
substantial rewrite in nine: it will need DB connector plus tables (and
new DB migrations in 0.8.x are forbidden..), plus a data API connector,
methods for tests to add new test results (which will need to be
asynchronous to support DB inserts), and an AngularJS implementation of
the frontend.
A good place to start looking at developing for nine is in the developer
section of the nine docs - see http://docs.buildbot.net/nine/
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 21:16:26 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 21:16:26 -0000
Subject: [Buildbot-commits] [Buildbot] #2706: Handling test results
In-Reply-To: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
References: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
Message-ID: <059.867c095947160b25cb269420216bfb10@buildbot.net>
#2706: Handling test results
-------------------------+--------------------
Reporter: jpommerening | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: |
-------------------------+--------------------
Comment (by jpommerening):
Some good points!
> If you have thousands of builds (as most users do)
check.
> and each build has thousands of tests (as most test runs do),
check?
> that's millions of test-result rows.
ouch? so what to do about it? If anything is good at handling that amount
of equally structured data it should be a database, right?
> It's a lot more for a larger-than-average installation. If we're sending
a message for each new test result, that's also a lot of messages.
> We've done some work with log handling in nine to try to reduce this (by
collapsing multiple log lines into a single database record, and
compressing it).
This, indeed, sounds problematic. But wait, you're storing the logs in the
database? And you were doing it line-by-line before? Also messages ? is
that related to nine's MQ stuff?
My impression was that it worked something like this:
* Slave watches logfile
* Slave sends chunks to the master
* LogObservers get updated with received chunks
* Master pipes chunks to a file
* Master compresses logfile, when step is done
* file is read from disk and decompressed when it's needed
But before I'll bother you with any more misinformed assumptions I'll have
a look at the nine docs ;)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Wed Feb 26 21:27:24 2014
From: trac at buildbot.net (Buildbot trac)
Date: Wed, 26 Feb 2014 21:27:24 -0000
Subject: [Buildbot-commits] [Buildbot] #2706: Handling test results
In-Reply-To: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
References: <044.c37abe282384417d67a2df955b975a91@buildbot.net>
Message-ID: <059.436011ed54d98483371739aee93db5b0@buildbot.net>
#2706: Handling test results
-------------------------+--------------------
Reporter: jpommerening | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: |
-------------------------+--------------------
Comment (by dustin):
In 0.8.x, logs are stored as netstrings in the filesystem, with one file
per log. The naive way to port that to the DB, and still allow per-line
access, would be to put each line in a DB row. And yes, messages are
related to nine's MQ stuff.
If this test support is optional, meaning that users won't find themselves
surprised by a 20GB sqlite DB and a slow master, then it might be OK to go
ahead and implement this in a fairly naive fashion, maybe a table with
columns (buildid, testname, result, logid, logline). If that proves
inefficient, we can revisit and optimize.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 02:19:37 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 02:19:37 -0000
Subject: [Buildbot-commits] [Buildbot] #739: HTML logs are included in
pickles
In-Reply-To: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
References: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
Message-ID: <054.4bf9e3fd3d4d88684146a86974f770e8@buildbot.net>
#739: HTML logs are included in pickles
---------------------+--------------------
Reporter: marcusl | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 0.8.+
Version: 0.7.12 | Resolution:
Keywords: sprint |
---------------------+--------------------
Comment (by dustin):
The issue of treating HTML as a single string is already fixed in nine,
where HTML logs are treated just like any other log -- streamed in chunks.
Fixing the problem of storing the HTML in a pickle is a good improvement
to the 0.8.x series, which I'm sure people will still be running for a
good while after nine is released, so this is definitely worthwhile.
That said, I really hate to see you mucking about in the awfulness that is
status plugins, pickles, !LogFile and HTMLLogFile, and so on. They're all
going to die in a fire in the nine branch, and be replaced with much less
awful things. You're correctly identifying lots of ways the old stuff is
awful.
Come to the nine side! We have cookies!
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From noreply at github.com Thu Feb 27 03:16:39 2014
From: noreply at github.com (GitHub)
Date: Wed, 26 Feb 2014 19:16:39 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 52fcac: fix syntax of python
code block
Message-ID: <530eae17a3345_3d9aa09d44129813@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 52fcac5454442ec2f16caf7d5c234d4c9eaf8266
https://github.com/buildbot/buildbot/commit/52fcac5454442ec2f16caf7d5c234d4c9eaf8266
Author: Dustin J. Mitchell
Date: 2014-02-26 (Wed, 26 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
Log Message:
-----------
fix syntax of python code block
From noreply at github.com Thu Feb 27 03:16:48 2014
From: noreply at github.com (GitHub)
Date: Wed, 26 Feb 2014 19:16:48 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 52fcac: fix syntax of python
code block
Message-ID: <530eae209464f_4e02d07d341451b3@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: 52fcac5454442ec2f16caf7d5c234d4c9eaf8266
https://github.com/buildbot/buildbot/commit/52fcac5454442ec2f16caf7d5c234d4c9eaf8266
Author: Dustin J. Mitchell
Date: 2014-02-26 (Wed, 26 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
Log Message:
-----------
fix syntax of python code block
Commit: f09ab351c5a4005f42b50e26c0f8e79b245a270f
https://github.com/buildbot/buildbot/commit/f09ab351c5a4005f42b50e26c0f8e79b245a270f
Author: Dustin J. Mitchell
Date: 2014-02-26 (Wed, 26 Feb 2014)
Changed paths:
M master/docs/manual/customization.rst
Log Message:
-----------
Merge branch 'master' into nine
Compare: https://github.com/buildbot/buildbot/compare/6a467d2ef5fc...f09ab351c5a4
From trac at buildbot.net Thu Feb 27 05:08:39 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 05:08:39 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Kxdtobbpc07
Message-ID: <20140227050839.AAA3111FAF1@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Kxdtobbpc07
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 09:09:10 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 09:09:10 -0000
Subject: [Buildbot-commits] [Buildbot] #739: HTML logs are included in
pickles
In-Reply-To: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
References: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
Message-ID: <054.b6c888577f3da75d233ecb9db34f896d@buildbot.net>
#739: HTML logs are included in pickles
---------------------+--------------------
Reporter: marcusl | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 0.8.+
Version: 0.7.12 | Resolution:
Keywords: sprint |
---------------------+--------------------
Comment (by jpommerening):
Haha, I will! Sooner rather than later.
I admit that I wasn't really aware of the sheer amount of work and thought
that already went into nine. The
[http://docs.buildbot.net/nine/developer/index.html developer docs] are a
great read and the new APIs look wonderful!
I'll put just a little more effort into giving 0.8.x a graceful way to die
(and really, I just want to see these "critical defect" tickets
disappear). But you're right ? I should have a closer look at nine first,
so I don't try to reinvent its concepts by myself :)
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 10:27:29 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 10:27:29 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: 0yufCl8
Message-ID: <20140227102729.ED0FD11FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user 0yufCl8
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 13:42:28 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 13:42:28 -0000
Subject: [Buildbot-commits] [Buildbot] #739: HTML logs are included in
pickles
In-Reply-To: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
References: <039.2b0ebe3105f086521fea6a5dd8cfc947@buildbot.net>
Message-ID: <054.f874f446586d2d7a40613548c2d08586@buildbot.net>
#739: HTML logs are included in pickles
---------------------+--------------------
Reporter: marcusl | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 0.8.+
Version: 0.7.12 | Resolution:
Keywords: sprint |
---------------------+--------------------
Comment (by dustin):
Awesome, thanks - I agree with your priorities!
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 14:04:27 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 14:04:27 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: AbigailAja101
Message-ID: <20140227140427.AA76B11FAF1@buildbot-trac.community.scl3.mozilla.com>
New user registration for user AbigailAja101
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 16:33:02 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 16:33:02 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Charlesbum
Message-ID: <20140227163302.F3E2211FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Charlesbum
--
Buildbot
Buildbot: build/test automation
From noreply at github.com Thu Feb 27 17:04:54 2014
From: noreply at github.com (GitHub)
Date: Thu, 27 Feb 2014 09:04:54 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] 7bac81: python2.5
compatibility
Message-ID: <530f7036d07a0_3b2fea7d387604@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: 7bac81442854e1fa2d9f77d07e531a2bbe9f7737
https://github.com/buildbot/buildbot/commit/7bac81442854e1fa2d9f77d07e531a2bbe9f7737
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_schedulers_timed_NightlyBase.py
Log Message:
-----------
python2.5 compatibility
Commit: a23ee860662f231332aa820623efe5a09055b5b8
https://github.com/buildbot/buildbot/commit/a23ee860662f231332aa820623efe5a09055b5b8
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M common/validate.sh
M master/contrib/github_buildbot.py
Log Message:
-----------
pep8 for contrib
Compare: https://github.com/buildbot/buildbot/compare/52fcac545444...a23ee860662f
From noreply at github.com Thu Feb 27 17:11:26 2014
From: noreply at github.com (GitHub)
Date: Thu, 27 Feb 2014 09:11:26 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] bd9201: Add functionality of
automatically scrolling outpu...
Message-ID: <530f71beb4f86_37041277d3c9828e@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: bd920171a81486595d2ffc8e33ba34fd6f0d062a
https://github.com/buildbot/buildbot/commit/bd920171a81486595d2ffc8e33ba34fd6f0d062a
Author: Ingo Budde
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M master/buildbot/status/web/templates/logs.html
Log Message:
-----------
Add functionality of automatically scrolling output log (scrolls down, as new data arrives, stops scrolling if you manually scroll up).
Commit: b5bf8c9ee42c3990572687c5f712541d53468ab7
https://github.com/buildbot/buildbot/commit/b5bf8c9ee42c3990572687c5f712541d53468ab7
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M master/buildbot/status/web/templates/logs.html
Log Message:
-----------
Merge ingo-budde/buildbot:autoscroll-log-output (PR #1078)
Compare: https://github.com/buildbot/buildbot/compare/a23ee860662f...b5bf8c9ee42c
From noreply at github.com Thu Feb 27 17:18:51 2014
From: noreply at github.com (GitHub)
Date: Thu, 27 Feb 2014 09:18:51 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] bd9201: Add functionality of
automatically scrolling outpu...
Message-ID: <530f737b9fe2a_2d8b845d3c30036@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: bd920171a81486595d2ffc8e33ba34fd6f0d062a
https://github.com/buildbot/buildbot/commit/bd920171a81486595d2ffc8e33ba34fd6f0d062a
Author: Ingo Budde
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M master/buildbot/status/web/templates/logs.html
Log Message:
-----------
Add functionality of automatically scrolling output log (scrolls down, as new data arrives, stops scrolling if you manually scroll up).
Commit: 7bac81442854e1fa2d9f77d07e531a2bbe9f7737
https://github.com/buildbot/buildbot/commit/7bac81442854e1fa2d9f77d07e531a2bbe9f7737
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_schedulers_timed_NightlyBase.py
Log Message:
-----------
python2.5 compatibility
Commit: a23ee860662f231332aa820623efe5a09055b5b8
https://github.com/buildbot/buildbot/commit/a23ee860662f231332aa820623efe5a09055b5b8
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M common/validate.sh
M master/contrib/github_buildbot.py
Log Message:
-----------
pep8 for contrib
Commit: b5bf8c9ee42c3990572687c5f712541d53468ab7
https://github.com/buildbot/buildbot/commit/b5bf8c9ee42c3990572687c5f712541d53468ab7
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M master/buildbot/status/web/templates/logs.html
Log Message:
-----------
Merge ingo-budde/buildbot:autoscroll-log-output (PR #1078)
Commit: 3be768ac7800077ff6cac3cf5bd7149eface6d3c
https://github.com/buildbot/buildbot/commit/3be768ac7800077ff6cac3cf5bd7149eface6d3c
Author: Dustin J. Mitchell
Date: 2014-02-27 (Thu, 27 Feb 2014)
Changed paths:
M common/validate.sh
M master/buildbot/process/buildstep.py
M master/buildbot/test/unit/test_schedulers_timed_NightlyBase.py
M master/contrib/github_buildbot.py
Log Message:
-----------
Merge branch 'master' into nine
Conflicts:
common/validate.sh
master/buildbot/status/web/templates/logs.html
Compare: https://github.com/buildbot/buildbot/compare/f09ab351c5a4...3be768ac7800
From trac at buildbot.net Thu Feb 27 20:13:36 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 20:13:36 -0000
Subject: [Buildbot-commits] [Buildbot] #2704: github status is pushed
twice
In-Reply-To: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
References: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
Message-ID: <056.b6d2f0c51f6ee3d019879c3b1b688132@buildbot.net>
#2704: github status is pushed twice
----------------------+------------------------
Reporter: liucougar | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: master | Resolution:
Keywords: |
----------------------+------------------------
Comment (by liucougar):
yes, there is only a single status listener configured
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Thu Feb 27 22:08:44 2014
From: trac at buildbot.net (Buildbot trac)
Date: Thu, 27 Feb 2014 22:08:44 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: uptO8gsl
Message-ID: <20140227220844.CCBCF11F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user uptO8gsl
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 04:24:55 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 04:24:55 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Svgrasissino
Message-ID: <20140228042455.7C73011FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Svgrasissino
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 10:45:24 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 10:45:24 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Orfgrddj
Message-ID: <20140228104524.8274711F7FC@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Orfgrddj
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 12:50:42 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 12:50:42 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: casehot
Message-ID: <20140228125042.DA5DC11FAD5@buildbot-trac.community.scl3.mozilla.com>
New user registration for user casehot
--
Buildbot
Buildbot: build/test automation
From noreply at github.com Fri Feb 28 16:58:29 2014
From: noreply at github.com (GitHub)
Date: Fri, 28 Feb 2014 08:58:29 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] d22728: Fixed configuration
of 'buildbot statuslog' for us...
Message-ID: <5310c035d876a_177b89d40834a5@hookshot-fe2-cp1-prd.iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/buildbot/buildbot
Commit: d22728aff6bccc8a903bf21128a10ae22592544b
https://github.com/buildbot/buildbot/commit/d22728aff6bccc8a903bf21128a10ae22592544b
Author: Patrick Valsecchi
Date: 2014-02-28 (Fri, 28 Feb 2014)
Changed paths:
M master/buildbot/scripts/runner.py
Log Message:
-----------
Fixed configuration of 'buildbot statuslog' for username and password
From noreply at github.com Fri Feb 28 17:07:20 2014
From: noreply at github.com (GitHub)
Date: Fri, 28 Feb 2014 09:07:20 -0800
Subject: [Buildbot-commits] [buildbot/buildbot] d22728: Fixed configuration
of 'buildbot statuslog' for us...
Message-ID: <5310c248558d9_1e1f13fbd3415756@hookshot-fe1-cp1-prd.iad.github.net.mail>
Branch: refs/heads/nine
Home: https://github.com/buildbot/buildbot
Commit: d22728aff6bccc8a903bf21128a10ae22592544b
https://github.com/buildbot/buildbot/commit/d22728aff6bccc8a903bf21128a10ae22592544b
Author: Patrick Valsecchi
Date: 2014-02-28 (Fri, 28 Feb 2014)
Changed paths:
M master/buildbot/scripts/runner.py
Log Message:
-----------
Fixed configuration of 'buildbot statuslog' for username and password
Commit: 4ff38ffd435b97cecb007b360d03206a88e490eb
https://github.com/buildbot/buildbot/commit/4ff38ffd435b97cecb007b360d03206a88e490eb
Author: Dustin J. Mitchell
Date: 2014-02-28 (Fri, 28 Feb 2014)
Log Message:
-----------
Merge branch 'master' into nine
Commit: e78cbe377773afb6e8c5b16c400ff7f63f728c56
https://github.com/buildbot/buildbot/commit/e78cbe377773afb6e8c5b16c400ff7f63f728c56
Author: Dustin J. Mitchell
Date: 2014-02-28 (Fri, 28 Feb 2014)
Changed paths:
M master/buildbot/scripts/runner.py
M master/buildbot/test/unit/test_scripts_runner.py
Log Message:
-----------
remove unused code
Compare: https://github.com/buildbot/buildbot/compare/3be768ac7800...e78cbe377773
From trac at buildbot.net Fri Feb 28 18:25:50 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 18:25:50 -0000
Subject: [Buildbot-commits] [Buildbot] #2707: Cannot configure username and
password for statuslog
Message-ID: <040.41ebace52f70dbc41e23909d5f9e2bc1@buildbot.net>
#2707: Cannot configure username and password for statuslog
----------------------+-----------------------
Reporter: pvalsecc | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords:
----------------------+-----------------------
If I put that in my .buildbot/options:
{{{
username = 'foo'
password = 'bar'
}}}
It is not taken into account when I run:
{{{
buildbot statuslog
}}}
Please have a look at the attached patch.
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 19:42:46 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 19:42:46 -0000
Subject: [Buildbot-commits] [Buildbot] #2704: github status is pushed
twice
In-Reply-To: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
References: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
Message-ID: <056.98c4ba960cf5ef6c77d6f98d1359df87@buildbot.net>
#2704: github status is pushed twice
----------------------+------------------------
Reporter: liucougar | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: master | Resolution:
Keywords: |
----------------------+------------------------
Comment (by liucougar):
actually, if I restart buildmaster, everything is fine.
however, everytime I reload buildmaster config file (reconfigure by
sending kill -HUP to the buildmaster process), there will be one extra
status update sent to github
sounds like these status object are not cleaned up on reconfig
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 19:46:08 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 19:46:08 -0000
Subject: [Buildbot-commits] [Buildbot] #2704: github status is pushed
twice
In-Reply-To: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
References: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
Message-ID: <056.ddf6e6868749ada219936d5136060095@buildbot.net>
#2704: github status is pushed twice
----------------------+------------------------
Reporter: liucougar | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: master | Resolution:
Keywords: |
----------------------+------------------------
Comment (by dustin):
Ah! That's a much better lead..
Can you put some prints in {{{PollingChangeSource.startService}}} and
{{{stopService}}} and similarly for {{{GitPoller}}}? I'm guessing that
during reconfig the old service's {{{stopService}}} isn't doing the right
thing (which is to call {{{stopLoop}}}).
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 20:41:00 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 20:41:00 -0000
Subject: [Buildbot-commits] [Buildbot] New user registration: Inviffpoolf
Message-ID: <20140228204100.18A0611F786@buildbot-trac.community.scl3.mozilla.com>
New user registration for user Inviffpoolf
--
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 21:13:17 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 21:13:17 -0000
Subject: [Buildbot-commits] [Buildbot] #2707: Cannot configure username
and password for statuslog
In-Reply-To: <040.41ebace52f70dbc41e23909d5f9e2bc1@buildbot.net>
References: <040.41ebace52f70dbc41e23909d5f9e2bc1@buildbot.net>
Message-ID: <055.436895b2954d0f704160aa55ba5ab4ce@buildbot.net>
#2707: Cannot configure username and password for statuslog
------------------------+---------------------
Reporter: pvalsecc | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: 0.8.9
Version: 0.8.8 | Resolution: fixed
Keywords: |
------------------------+---------------------
Changes (by dustin):
* status: new => closed
* type: undecided => enhancement
* resolution: => fixed
* milestone: undecided => 0.8.9
Comment:
Already landed the fix for this based on the mailing-list post. Thanks!
--
Ticket URL:
Buildbot
Buildbot: build/test automation
From trac at buildbot.net Fri Feb 28 21:40:31 2014
From: trac at buildbot.net (Buildbot trac)
Date: Fri, 28 Feb 2014 21:40:31 -0000
Subject: [Buildbot-commits] [Buildbot] #2704: github status is pushed
twice
In-Reply-To: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
References: <041.fc71a71b1f8d0d5fdf800d685ef004fa@buildbot.net>
Message-ID: <056.aebcddb85b0aa31b9a6851637de6b072@buildbot.net>
#2704: github status is pushed twice
----------------------+------------------------
Reporter: liucougar | Owner:
Type: defect | Status: new
Priority: minor | Milestone: undecided
Version: master | Resolution:
Keywords: |
----------------------+------------------------
Comment (by liucougar):
i am not using either of these modules you mentioned. however, with the
info you gave, I found a fix:
in buildbot/status/github.py, it misses a stopService function. when I add
the following to the file, reconfig won't trigger extra status reports
{{{
def stopService(self):
StatusReceiverMultiService.stopService(self)
self._status.unsubscribe(self)
}}}
--
Ticket URL:
Buildbot
Buildbot: build/test automation