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

introduce shell2junit #27825

Merged
merged 2 commits into from
Jun 27, 2016
Merged

introduce shell2junit #27825

merged 2 commits into from
Jun 27, 2016

Conversation

freehan
Copy link
Contributor

@freehan freehan commented Jun 22, 2016

@freehan freehan added the release-note-none Denotes a PR that doesn't merit a release note. label Jun 22, 2016
@freehan freehan self-assigned this Jun 22, 2016
@k8s-github-robot k8s-github-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 22, 2016
@spxtr
Copy link
Contributor

spxtr commented Jun 22, 2016

kubernetes/test-infra#76 cc @kubernetes/sig-testing

@freehan freehan force-pushed the jenkinjunit branch 2 times, most recently from d300d7e to 2e867fa Compare June 22, 2016 18:49
@lavalamp
Copy link
Member

LGTM, e2e failed though?

noleak=false
fi
record_command "${STAGE_CLEANUP}" "resource-leak" ${noleak}
if ! ${noleak} ; then
Copy link
Contributor

Choose a reason for hiding this comment

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

This is pretty confusing. At the least switch noleak to leak and get rid of this double negation, and I'd really rather explicitly check [[ "${leak}" == "true" ]].

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That is the feature of command recorder. It will record failure if false. For true, the testcase is consider passed. That is why I reversed it.

@ixdy
Copy link
Member

ixdy commented Jun 22, 2016

I'm not super excited about adding more bash, but this is probably better than not having anytihng, so I guess this is OK.

It might be helpful for the junit library if you
a) added a comment indicating where it came from and what version/revision
b) had a separate commit showing the changes you made

@freehan
Copy link
Contributor Author

freehan commented Jun 22, 2016

Will close this PR and come back with another one. I will put the original lib and modifications in separate commits.

@spxtr
Copy link
Contributor

spxtr commented Jun 22, 2016

You can do it in the same PR. That way we keep comments :)

@freehan freehan changed the title WIP: introduce junit command recorder introduce shell2junit Jun 22, 2016
@freehan
Copy link
Contributor Author

freehan commented Jun 22, 2016

Ready for review.

This part has to go in first because e2e-runner is a standalone script. I plan to source sh2ju library in e2e-runner using curl.

@freehan
Copy link
Contributor Author

freehan commented Jun 23, 2016

ping. Can anyone LGTM? This one has to go in first.

@freehan freehan added this to the v1.3 milestone Jun 23, 2016
@freehan freehan force-pushed the jenkinjunit branch 2 times, most recently from feefddb to 31d1f83 Compare June 23, 2016 23:06
@lavalamp lavalamp removed this from the v1.3 milestone Jun 24, 2016
@k8s-bot
Copy link

k8s-bot commented Jun 24, 2016

GCE e2e build/test passed for commit 5179ad2ec7b1cdb29e419295879bca22707f61ef.

@freehan freehan assigned lavalamp and unassigned freehan Jun 24, 2016
@lavalamp lavalamp assigned nikhiljindal and unassigned lavalamp Jun 24, 2016
@lavalamp
Copy link
Member

Nikhil volunteered to review

echo "name is: $name"
echo "class is: $class"

# echo "name is: $name"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this intentional?
Seems fine to keep the echos for debugging

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah. The lib already prints the complete command. Printing name and class are not very useful since they are from user input. And it makes the output some how crowded.

Copy link
Contributor

Choose a reason for hiding this comment

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

Delete the lines then? No need to keep commented out lines.

@nikhiljindal
Copy link
Contributor

One minor comment.
LGTM assuming those sed commands work :)

@k8s-bot
Copy link

k8s-bot commented Jun 27, 2016

GCE e2e build/test passed for commit ec3f0e9.

@nikhiljindal
Copy link
Contributor

LGTM, thx!

@nikhiljindal nikhiljindal added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 27, 2016
@k8s-github-robot
Copy link

@freehan
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 27, 2016
@freehan freehan added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 27, 2016
@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 0742bc0 into kubernetes:master Jun 27, 2016
k8s-github-robot pushed a commit that referenced this pull request Jul 9, 2016
Automatic merge from submit-queue

add junit recording in e2e runner

2nd part of #27825  

Injected junit recorder at a few places.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants