Magicians.
I have updated the rules that test merges to abort when there are ci
regressions and the PR doesn't claim to fix one of them
Three bugs currently block merges into master. CI is looking for one
of these three token:
$$fixes-1347715$$
$$fixes-1342725$$
$$fixes-1342937$$
Adding $$fixes-<lp-bug-number>$$ as a comment to the PR will signal it
is allowed to test. The token can be in any comment and in any part of
the comment.
A bug blocks merges when it is of critical importance, in the triaged
or in-progress state, and it is tagged with "ci regression". Updating
the status of a bug to fix committed will remove it from the list of
blockers.
It's me, not you, but maybe it should be you.
I am spending 4 out of 5 days reviewing all the broken test runs
looking for new evidence to help close the regressions. The
regressions are mutating. As I am the only person on operations duties
this week because of vacations, I cannot keep up. Juju developers must
stop landing branches that compound the regressions.
As devel has been broken since 2014-06-25, and devel was broken for
many weeks in June. it is fair to say juju devel has not worked for a
month and only 2 weeks in the last 2 months. There is little point in
adding features to devel because I cannot release an alpha with
regressions.
I hope with a working devel, or at least a slower moving broken devel,
the Juju QA Team can write new tests that ensure new juju is
compatible with old juju so that Ubuntu will it in trusty.
--
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
