[21:10] <rharper> powersj: magicalChicken:  so when a test fails, I get a nice dir in /tmp which includes the collect data ... if I want to modify that data (instead of recollecting it) and then re-run the unittest, is that possible?
[21:10] <powersj> sure
[21:11] <powersj> Instead of running "run" you can run "verify"
[21:11] <powersj> python3 -m tests.cloud_tests verify -d <your dir>
[21:12] <powersj> I believe is all you need.
[21:12] <rharper> sweet
[21:12] <powersj> I did this when writing the tests so I didn't have to collect each time :)
[21:12] <powersj> you were the one who pushed for this too :P
[21:12] <rharper> btw, I figured how how to pass all the args
[21:12] <rharper> yes, yes I did
[21:12] <rharper> pain in curtin
[21:12] <powersj> I can imagine
[21:12] <rharper> waiting 120 seconds per change in the unittest
[21:12] <rharper> this is faster
[21:13] <rharper> not by much (2m15 seconds) to run a single ntp_server test; that's mostly image download
[21:13] <rharper> which magicalChicken said he'd look at getting a sync-images
[21:13] <rharper> as we just throw them away
[21:14] <magicalChicken> rharper: I'm hoping to get to that today
[21:14] <magicalChicken> rharper: Still working on finishing up deb build/run from tree script
[21:15] <rharper> cool
[21:15] <magicalChicken> rharper: I'm basing this + saving image on the pylxd 2.1.3 version so it can merge soon
[21:15] <rharper> currently I'm passing --deb to the run command after doing a package/bddeb locally
[21:15] <rharper> so that works nicely with the tox env
[21:15] <rharper> tox -e citest -- run -v -n xenial --deb cloud-init_0.7.9-2-gca191a2-1~bddeb_all.deb -t tests/cloud_tests/configs/modules/ntp_servers.yaml
[21:16] <rharper> updated the citest tox command to just have {posargs}
[21:16] <magicalChicken> rharper: This is pretty much same thing, just building in a container to keep the host clean
[21:16] <rharper> yep
[21:16] <rharper> nice
[21:16] <magicalChicken> rharper: I pulled in tox with {posargs}
[21:16] <magicalChicken> probably going to have a citest_run env and a citest env separate
[21:16] <magicalChicken> where citest_run is shortcut to just run with local tree on default systme
[21:16] <rharper> eah
[21:17] <rharper> nice
[22:56] <rharper> smoser: when maas deploys, does it typically write a 'user_data.sh' script ? or is that something a maas user would add ?