Merge lp:~fwereade/juju-core/trivial-new-unit-test-charms into lp:~juju/juju-core/trunk

Proposed by William Reade
Status: Rejected
Rejected by: William Reade
Proposed branch: lp:~fwereade/juju-core/trivial-new-unit-test-charms
Merge into: lp:~juju/juju-core/trunk
Diff against target: 50 lines (+18/-0)
6 files modified
testing/repo/series/rel-peer/metadata.yaml (+5/-0)
testing/repo/series/rel-peer/revision (+1/-0)
testing/repo/series/rel-pro/metadata.yaml (+5/-0)
testing/repo/series/rel-pro/revision (+1/-0)
testing/repo/series/rel-req/metadata.yaml (+5/-0)
testing/repo/series/rel-req/revision (+1/-0)
To merge this branch: bzr merge lp:~fwereade/juju-core/trivial-new-unit-test-charms
Reviewer Review Type Date Requested Status
The Go Language Gophers Pending
Review via email: mp+132080@code.launchpad.net

Description of the change

testing: add useful charms

This is just 3 new charms, each of which supplies one relation of the type
indicated by its name. Nothing is using them yet; I'll be going through the
various tests step by step, to ensure that everything uses real relations,
in advance of changing AddRelation to verify that the related services
really do implement the endpoints suggested in the params.

I don't really expect these to be the *only* charms I'll need, but this is a
good start, and I'm keen to make the individual elements of this pipeline as
small and clean as possible, because the forces in play tend towards vast
and ugly diffs.

https://codereview.appspot.com/6811052/

To post a comment you must log in.
Revision history for this message
William Reade (fwereade) wrote :
Download full text (3.4 KiB)

Reviewers: mp+132080_code.launchpad.net,

Message:
Please take a look.

Description:
testing: add useful charms

This is just 3 new charms, each of which supplies one relation of the
type
indicated by its name. Nothing is using them yet; I'll be going through
the
various tests step by step, to ensure that everything uses real
relations,
in advance of changing AddRelation to verify that the related services
really do implement the endpoints suggested in the params.

I don't really expect these to be the *only* charms I'll need, but this
is a
good start, and I'm keen to make the individual elements of this
pipeline as
small and clean as possible, because the forces in play tend towards
vast
and ugly diffs.

https://code.launchpad.net/~fwereade/juju-core/trivial-new-unit-test-charms/+merge/132080

(do not edit description out of merge proposal)

Please review this at https://codereview.appspot.com/6811052/

Affected files:
   A [revision details]
   A testing/repo/series/rel-peer/metadata.yaml
   A testing/repo/series/rel-peer/revision
   A testing/repo/series/rel-pro/metadata.yaml
   A testing/repo/series/rel-pro/revision
   A testing/repo/series/rel-req/metadata.yaml
   A testing/repo/series/rel-req/revision

Index: [revision details]
=== added file '[revision details]'
--- [revision details] 2012-01-01 00:00:00 +0000
+++ [revision details] 2012-01-01 00:00:00 +0000
@@ -0,0 +1,2 @@
+Old revision: <email address hidden>
+New revision: <email address hidden>

Index: testing/repo/series/rel-peer/metadata.yaml
=== added file 'testing/repo/series/rel-peer/metadata.yaml'
--- testing/repo/series/rel-peer/metadata.yaml 1970-01-01 00:00:00 +0000
+++ testing/repo/series/rel-peer/metadata.yaml 2012-10-30 11:48:17 +0000
@@ -0,0 +1,5 @@
+name: peer
+summary: Test charm with a peer relation
+description: Test charm with a peer relation
+peers:
+ name: ifce

Index: testing/repo/series/rel-peer/revision
=== added file 'testing/repo/series/rel-peer/revision'
--- testing/repo/series/rel-peer/revision 1970-01-01 00:00:00 +0000
+++ testing/repo/series/rel-peer/revision 2012-10-30 11:48:17 +0000
@@ -0,0 +1,1 @@
+1

Index: testing/repo/series/rel-pro/metadata.yaml
=== added file 'testing/repo/series/rel-pro/metadata.yaml'
--- testing/repo/series/rel-pro/metadata.yaml 1970-01-01 00:00:00 +0000
+++ testing/repo/series/rel-pro/metadata.yaml 2012-10-30 11:48:17 +0000
@@ -0,0 +1,5 @@
+name: pro
+summary: Test charm with a provider relation
+description: Test charm with a provider relation
+provides:
+ pname: ifce

Index: testing/repo/series/rel-pro/revision
=== added file 'testing/repo/series/rel-pro/revision'
--- testing/repo/series/rel-pro/revision 1970-01-01 00:00:00 +0000
+++ testing/repo/series/rel-pro/revision 2012-10-30 11:48:17 +0000
@@ -0,0 +1,1 @@
+1

Index: testing/repo/series/rel-req/metadata.yaml
=== added file 'testing/repo/series/rel-req/metadata.yaml'
--- testing/repo/series/rel-req/metadata.yaml 1970-01-01 00:00:00 +0000
+++ testing/repo/series/rel-req/metadata.yaml 2012-10-30 11:48:17 +0000
@@ -0,0 +1,5 @@
+name: req
+summary: Test charm with a requirer relation
+description: Test ...

Read more...

Revision history for this message
John A Meinel (jameinel) wrote :
Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

We have charms which are used as requirer/provider/peer examples.

Do we need more? Can we get rid of existing ones?

https://codereview.appspot.com/6811052/

Revision history for this message
William Reade (fwereade) wrote :

On 2012/10/30 14:55:30, niemeyer wrote:
> We have charms which are used as requirer/provider/peer examples.

> Do we need more? Can we get rid of existing ones?

Discussed live; rejecting.

https://codereview.appspot.com/6811052/

Unmerged revisions

699. By William Reade

add test charms to allow future relationy unit tests to add verified relations to services

698. By Dave Cheney

worker/provisioner: fix race on config reload

Bug #1064144 was cause by a race between the PA reloading it's config -or-
observing a change to the machines collection. This proposal adds an observer
that the tests can use to wait until the PA has ack'd the configuration
change.

R=fwereade, niemeyer
CC=
https://codereview.appspot.com/6742049

697. By William Reade

state: drop obsolete relation lifecycle

drop:

* Relation.EnsureDying
* Relation.EnsureDead
* State.RemoveRelation

...and use Relation.Destroy and RelationUnit.LeaveScope instead throughout.

R=niemeyer
CC=
https://codereview.appspot.com/6812047

696. By William Reade

state: Relation.Destroy

...and `juju remove-relation`, because it's trivial now that Destroy exists.

Points to note:

* Relation.EnsureDying, Relation.EnsureDead, and State.RemoveRelation are
  now obsolete, and will be remove entirely in a followup CL; omitted here
  due to volume of change.
* It's still called remove-relation, instead of destroy-relation + alias,
  because it seems more sensible to fix remove-unit at the same time and it
  also deserves a separate CL IMO.

R=niemeyer
CC=
https://codereview.appspot.com/6783051

695. By Roger Peppe

worker/uniter: make logger predictable

The stdout pipe is closed too early by os/exec;
do the work ourselves to prevent this.

R=dfc, niemeyer
CC=
https://codereview.appspot.com/6774050

694. By William Reade

juju:implement add-relation

R=niemeyer
CC=
https://codereview.appspot.com/6761044

693. By William Reade

upstart: use better Out value

We now use the same value for upstart conf Out fields as we do --log-file
params. No idea what I did to lead myself to think it didn't work...

Also, made log file names more consistent (ie $kind-$name.log, with no
explicit "-agent")

R=rog, niemeyer
CC=
https://codereview.appspot.com/6766051

692. By William Reade

uniter/charm: verify upgrade symlink overwrite

Verifies non-existence of lp:988115 in juju-core

R=niemeyer
CC=
https://codereview.appspot.com/6760046

691. By Frank Mueller

firewaller: integrated global mode

Firewaller now recognizes the global mode. It dies a
port usage counting usage counting and opens each
used port only once and closes it after the last using unit
has gone. The handling of ports in case of a restart has
been removed from this CL to a later one.

R=
CC=
https://codereview.appspot.com/6713054

690. By Roger Peppe

cmd/builddb: fix ssl build

Also add a couple of log messages.

R=fwereade, dfc
CC=
https://codereview.appspot.com/6776051

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== added directory 'testing/repo/series/rel-peer'
2=== added file 'testing/repo/series/rel-peer/metadata.yaml'
3--- testing/repo/series/rel-peer/metadata.yaml 1970-01-01 00:00:00 +0000
4+++ testing/repo/series/rel-peer/metadata.yaml 2012-10-30 11:53:25 +0000
5@@ -0,0 +1,5 @@
6+name: peer
7+summary: Test charm with a peer relation
8+description: Test charm with a peer relation
9+peers:
10+ name: ifce
11
12=== added file 'testing/repo/series/rel-peer/revision'
13--- testing/repo/series/rel-peer/revision 1970-01-01 00:00:00 +0000
14+++ testing/repo/series/rel-peer/revision 2012-10-30 11:53:25 +0000
15@@ -0,0 +1,1 @@
16+1
17
18=== added directory 'testing/repo/series/rel-pro'
19=== added file 'testing/repo/series/rel-pro/metadata.yaml'
20--- testing/repo/series/rel-pro/metadata.yaml 1970-01-01 00:00:00 +0000
21+++ testing/repo/series/rel-pro/metadata.yaml 2012-10-30 11:53:25 +0000
22@@ -0,0 +1,5 @@
23+name: pro
24+summary: Test charm with a provider relation
25+description: Test charm with a provider relation
26+provides:
27+ pname: ifce
28
29=== added file 'testing/repo/series/rel-pro/revision'
30--- testing/repo/series/rel-pro/revision 1970-01-01 00:00:00 +0000
31+++ testing/repo/series/rel-pro/revision 2012-10-30 11:53:25 +0000
32@@ -0,0 +1,1 @@
33+1
34
35=== added directory 'testing/repo/series/rel-req'
36=== added file 'testing/repo/series/rel-req/metadata.yaml'
37--- testing/repo/series/rel-req/metadata.yaml 1970-01-01 00:00:00 +0000
38+++ testing/repo/series/rel-req/metadata.yaml 2012-10-30 11:53:25 +0000
39@@ -0,0 +1,5 @@
40+name: req
41+summary: Test charm with a requirer relation
42+description: Test charm with a requirer relation
43+requires:
44+ rname: ifce
45
46=== added file 'testing/repo/series/rel-req/revision'
47--- testing/repo/series/rel-req/revision 1970-01-01 00:00:00 +0000
48+++ testing/repo/series/rel-req/revision 2012-10-30 11:53:25 +0000
49@@ -0,0 +1,1 @@
50+1

Subscribers

People subscribed via source and target branches