3 Commits

Author	SHA1	Message	Date
Colin Walters	222d730cce	vmcheck/misc-2: Make compatible with staged default ... First the pinning tests would try to pin a staged deployment, and some of the later tests here depend on a subtle way on the state of the system. It's tempting to do a `reset` before each one and reboot but this makes things work. There's some additional assertions here as I went through and was debugging. Prep for making staging the default. Closes: #1438 Approved by: jlebon	2018-07-03 19:14:54 +00:00
Jonathan Lebon	bff3a54e1e	daemon/upgrader: Consistently remove transient state ... With the new support for pinning deployments, we need to also update rpm-ostree to clean up the transient state as is now done in the ostree sysroot upgrader. This addresses that issue as well as tries to be a little cleaner in how we clean up other transient state. Notably, we add a new helper function to `RpmOstreeOrigin` to do this for us and use it in the upgrader. In other cases, we do want this transient information since it allows us to describe the deployment. Closes: https://github.com/ostreedev/ostree/issues/1595 Closes: #1372 Approved by: cgwalters	2018-05-23 16:27:10 +00:00
Colin Walters	1c8c755e81	tests: Split test-basic into misc-{1,2} ... Our test suite originated when package layering was still being developed, but now that that's mature, the logic where layering tests are distinct makes less sense. The `basic` test had grown to really be a collection of many miscellaneous things. Let's make that more explicit. Further, let's avoid having each test suite grow too large; when a single test fails we don't have an easy way to rerun just that test, so a crude way to have faster local iteration is to split into groups. My plan is to reintroduce a `basic` test that covers the basics of all functionality - update, deploy, layering, etc. The advanced/corner cases of layering like the `rm -rf /` test would still live in a `test-layering.sh` or so. Closes: #1336 Approved by: jlebon	2018-04-16 17:53:20 +00:00