search

chriseldredge / vulcan

Continuous Integration server
GNU General Public License v2.0
0 stars 1 forks source link

Project dependency may not prevent concurrent builds #146

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create two projects, "a" and "b" where "b" depends on "a"
2. Create two build daemons
3. Manually build "a" and "b."  "b" will block while "a" builds.
4. Once "b" starts building, manually build "a" again.

What is the expected output? What do you see instead?

"a" begins building immediately, possibly breaking "b"

"a" should block in the queue until after "b" is finished.

Original issue reported on code.google.com by chris.eldredge@gmail.com on 19 Nov 2008 at 5:03

GoogleCodeExporter commented 9 years ago 
Fixed in r625.

Original comment by chris.eldredge@gmail.com on 19 Nov 2008 at 6:11

GoogleCodeExporter commented 9 years ago 
r627 fixes bug introduced where a blocked project could disappear from build 
queue.

Original comment by chris.eldredge@gmail.com on 24 Nov 2008 at 9:25

GoogleCodeExporter commented 9 years ago 
Fixed in builds 375 and up.

Original comment by chris.eldredge@gmail.com on 5 Dec 2008 at 4:34

GoogleCodeExporter commented 9 years ago 
Additional regression: when blocked project completes with FAIL, SKIP or ERROR,
dependent project will not SKIP as it should.

Original comment by chris.eldredge@gmail.com on 5 Feb 2009 at 5:19

GoogleCodeExporter commented 9 years ago 
r679 fixes an additional problem and should address comment 4.

Original comment by chris.eldredge@gmail.com on 31 Mar 2009 at 7:00

GoogleCodeExporter commented 9 years ago 
Issue 160 has been merged into this issue.

Original comment by chris.eldredge@gmail.com on 31 Mar 2009 at 7:01

GoogleCodeExporter commented 9 years ago 
Closing as no known issues are outstanding.

Original comment by chris.eldredge@gmail.com on 12 Nov 2010 at 4:17