If a DOMAIN_MODE environment variable or a domain.mode system property is set, TorqueSpec will fire up a domain controller, hopefully configured with at least one host controller and one server group. There seems to be a problem with in-container testing interfering with results being relayed back to RSpec, so I'm disabling them when TorqueSpec.domain_mode is true. This effectively turns remote_describe into a no-op.
Upstream AS 7.1 builds no longer accept nor need a -logmodule argument.
The problem occurs when the client side lacks the class of the exception tossed by the server. Also don't think we need to fail_filtered_examples on the client since the server already did it.
…sons, apparently) I was adding the TorqueSpec::Daemon to a services block that already had one, but the write check was failing to detect that it was changed from the original. There's no real value from not always writing, I don't think.
…rs errors" on failed builds. Nested examples contain graphs of other "anonymously classless" things that won't marshal. So we're now going to completely punt and create entirely new ExampleGroups to act as the parent of every example returned by the daemon. Seems to work on [un]nested groups fairly well. We'll see!