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

List failed tests and the content of the .failed files #8

Merged
merged 1 commit into from Nov 12, 2015

Conversation

jhoblitt
Copy link
Member

We list the failed tests after dumping the contents of the
.failed files so that eups distrib will be able to report
the failed tests properly.

Switch to .format() for string formatting so as to not repeat
"testsDir" four distinct times.

We list the failed tests after dumping the contents of the
.failed files so that eups distrib will be able to report
the failed tests properly.

Switch to .format() for string formatting so as to not repeat
"testsDir" four distinct times.
if [ $$nfail -gt 0 ]; then \
echo "Failed test output:" >&2; \
find {0} -name \*.failed -exec cat {{}} \; >&2; \
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The >&2; has essentially no effect. It probably needs to be something like find {0} -name \*.failed -exec cat {} \; | cat >&2 (may require some fiddling).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although this code does do what I want: send the output to the log files.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've done some experimentation and that >&2 does work as I expect so I don't think this needs to be changed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jhoblitt What's your objection to the >&2? I would have naively thought that would work fine.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spoke to @jhoblitt and the confusion was over the escaped semi-colon that goes with the -exec and is not actually a command separator. There is no issue.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a comprehension failure on my part -- I was thrown off by the escape line endings and didn't catch that the escaped ; was part of the -exec arg. @timj and I just discussed this and I think it's good as-is.

@jhoblitt
Copy link
Member Author

👍

@timj timj merged commit f6a7bb4 into master Nov 12, 2015
@ktlim ktlim deleted the tickets/DM-3829 branch August 25, 2018 06:16
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

Successfully merging this pull request may close these issues.

None yet

3 participants