Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up the junk spewed by the flocker.volume.functional.test_script suite #171

Closed
exarkun opened this issue Jun 27, 2014 · 3 comments
Closed

Comments

@exarkun
Copy link
Contributor

exarkun commented Jun 27, 2014

Replaced by https://clusterhq.atlassian.net/browse/FLOC-171

Many of these dump stuff onto stderr. For example:

  ReceiveTests
    test_creates_files ... cannot open 'testpool_c7fb14d9-49d5-4a3e-ad35-4043e6f281a9/e68b4669-9884-476f-a4ec-c551c0788c94.thevolume': dataset does not exist
[OK]
@wallrj
Copy link
Contributor

wallrj commented Jul 2, 2014

See #183 (comment) for another example of this.

@exarkun
Copy link
Contributor Author

exarkun commented Jul 7, 2014

Capturing stdout and stderr from child processes is mostly just a matter of passing the right arguments to Popen (or check_output or spawnProcess). We should do this so we capture this output in memory (probably by way of some kind of file object, since that's how all these APIs work). Then we can dump the information from memory into an appropriate log.

@adamtheturtle
Copy link
Contributor

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-171. You are welcome to file additional issues in GitHub if that's easier for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants