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

Do not dump lots and lots of text on certain failures in tests #1909

Merged

Conversation

mulkieran
Copy link
Member

@mulkieran mulkieran commented Mar 27, 2020

Related: #1656.
Related: #1892

@mulkieran mulkieran self-assigned this Mar 27, 2020
@mulkieran mulkieran force-pushed the develop-2.0.1-remove-dump branch 2 times, most recently from 2141fae to 04ffbdf Compare March 27, 2020 14:13
@mulkieran mulkieran added this to In progress (long term) in 2020March via automation Mar 27, 2020
@mulkieran
Copy link
Member Author

This is related to #1892, in the sense that I was looking to see if the volume of code that has pylint errors could be reduced. I decided to be more conservative than I had planned, so I haven't reduced the number of pylint errors, just split them across more directories.

@mulkieran mulkieran moved this from In progress (long term) to In review in 2020March Mar 27, 2020
It is way too much to read through in logs.

Move _stratis_id.py and code that only it depends on to the stratisd
scripts directory.

_stratis_id.py was originally written for two reasons.
* It allowed dumping out lots of signature block information if udev tests
failed. This was written to attempt to find out the cause of an
intermittent failure in the udev tests. But the output is voluminous and
turned out not to be very useful as it was found that the cause of the
intermittent failures was that occasionally the CreatePool command would
fail, because it was called before the loopbacked devices were properly
set up, but that the test would ignore that failure and proceed. This
problem has been fixed.
* The version of libblkid that recognizes Stratis devices was not yet
generally available, so the _stratis_id.py script provided a programmatic
way to identify Stratis block devices. In most cases, however, blkid
is now just as good.

The reason to keep the stratis_id.py script around in the scripts
directory, is that it provides a structured view of a Stratis signature
buffer that it has read. This is not yet provided by other tools, although
the plan is to ultimately provide it by means of a Rust program that uses
the metadata module which is currently part of stratisd, but which could
be exported as a separate crate. In the meantime, it seems reasonable to
leave the script where it is accessible to us to possibly be helpful in
looking for Stratis metadata on devices. This is not a script that we
would choose to release. Add the usual infrastructure for the newly
introduced directory, but do not try to improve the script at this time.
We can wait until it either gets more use or withers away entirely.

Signed-off-by: mulhern <amulhern@redhat.com>
@mulkieran
Copy link
Member Author

rebased.

@mulkieran mulkieran merged commit ed0e1f1 into stratis-storage:develop-2.0.1 Mar 27, 2020
2020March automation moved this from In review to Done Mar 27, 2020
@mulkieran mulkieran deleted the develop-2.0.1-remove-dump branch March 27, 2020 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
2020March
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

5 participants