[00:10] <axw> hml: if you're going to update goose again any time soon, can you please remove the StatusBuildSpawning constant from nova?
[00:10] <axw> assuming we don't reference it anywhere else
[00:11] <hml> axw: sure - will add it to the list of clean up for goose.v2
[00:11] <axw> hml: thanks
[00:12] <veebers> axw, hml: Is this related to https://github.com/juju/juju/pull/7300 at all? (please note that I'm investigating this job as there has been a bunch of unexpected failures with it)
[00:12] <axw> veebers: yes
[00:13] <hml> veebers: i tried running the tests before the merge, it was a moving target with results over 4 tries, i was a little surprised the merge went thru.
[00:14] <veebers> hml: which merge was that?
[00:14] <hml> veebers: for PR 7300
[00:16] <veebers> hml: it didn't go through, that failed (unless I'm missing something?)
[00:17] <hml> veebers: i got confused.  i was thinking of a different one.
[00:18] <veebers> hml: ack
[00:18] <hml> veebers: there is a merge conflict with dependences.tsv causing the issues… with pr7300 it looks like
[00:19] <hml> veebers, i need to straighten out the goose dependency before i do the merge
[00:19] <hml> pr 7289 was getting the ci merge failures.
[00:24] <veebers> hml: ack, I've just changed what machine the merges run on which seems to have helped. I need to have a look and see if that other machine is sick or so
[00:25] <hml> veebers: ok, i fixed the merge conflict on 7300, not ready to merge yet though
[00:27] <veebers> hml: ack
[00:28] <veebers> axw, hml: Please alert me to any check/merge job failures that seem unwarranted. I'll be keeping an eye, but let me know if I miss anything :-)
[00:28] <axw> veebers: will do
[00:28] <hml> veebers: sure
=== frankban|afk is now known as frankban
[10:32] <rogpeppe> axw: here's a little cleanup of the migrate command to make it use the ModelCommandBase: https://github.com/juju/juju/pull/7302
=== petevg is now known as petevg_afk
=== bdx_ is now known as bdx
[15:26] <wpk> axw: could you comment on PR7204 about the bridge_ports issue? Is it a problem or not?
[16:23] <mup> Bug #1688028 opened: Juju fails to request deploy after busy node returns OK <juju-core:New> <https://launchpad.net/bugs/1688028>
[20:08] <mup> Bug #1688028 changed: Juju fails to request deploy after busy node returns OK <cdo-qa> <cdo-qa-blocker> <juju:New> <juju-core:Invalid> <https://launchpad.net/bugs/1688028>
[23:47] <babbageclunk> gah, does anyone else have trouble remembering which checkers are in gc and which are in jc? I'm tempted to refer to the gc ones in jc so it's a superset and then just use them from there all the time.