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

[PublishTestResultsV2] Add option to fail task if no test result files are found #14868

Closed
wants to merge 5 commits into from

Conversation

walliski
Copy link

Task name: PublishTestResultsV2

Description:
Adds an option that lets the user configure the task to fail in case no
test result files have been found. This serves as a safeguard to make
sure that the test-run task and this task has been configured properly
to find the test result files.

We are defaulting to not failing the task on missing files, to keep current behavior.

Documentation changes required: Y
I guess this option should be documented.

Added unit tests: N
Not sure how this should be tested, as the "Warning" functionality doesn't seem to be tested either?

Attached related issue: Y
Solves #13275

Checklist:

  • Task version was bumped - please check instruction how to do it
  • Checked that applied changes work as expected

I have no idea if this works, or how to test it. I have ran the build and existing tests for the task, but haven't manually tested the task anywhere (and have no idea how anything here works...).

@walliski walliski requested a review from shailesh-sk as a code owner May 21, 2021 13:09
@ghost
Copy link

ghost commented May 21, 2021

CLA assistant check
All CLA requirements met.

@walliski walliski force-pushed the fail-if-no-results branch 2 times, most recently from 964f70b to 12ccb49 Compare May 21, 2021 13:27
@walliski walliski changed the title Add option to fail task if no test results are found [PublishTestResultsV2] Add option to fail task if no test results are found May 21, 2021
@walliski walliski changed the title [PublishTestResultsV2] Add option to fail task if no test results are found [PublishTestResultsV2] Add option to fail task if no test result files are found May 21, 2021
@github-actions
Copy link

This PR is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the PR otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Nov 17, 2021
@walliski
Copy link
Author

Soooo is this going somewhere?

@github-actions github-actions bot removed the stale label Nov 17, 2021
@Alexander-Bartosh
Copy link

Why is that a problem to review this nice improvement for 7 months !?

@mathiash98
Copy link

mathiash98 commented Dec 9, 2021

@shailesh-sk Could you do a review on this PR.

Or maybe some of the more active contributers could do a review?
Perhaps @anatolybolshakov or @nadesu @v-jkarri

Merging this would allow closing #13275 and #14786

@sonnyhcl
Copy link

reping here since it's a really really useful feature! could anyone go through the code review?

@the-rule
Copy link

the-rule commented May 30, 2022

Could we merge this essential feature any time soon? @walliski @shailesh-sk

@walliski
Copy link
Author

@the-rule I can't really do anything about it, its up for the maintainers to merge it.

To me its infuriating that such a simple change, a feature that exists in pretty much all CI systems, has not been merged yet, and has been actively ignored for over a year.

@the-rule
Copy link

@shailesh-sk ping-ping

@the-rule
Copy link

To me its infuriating that such a simple change, a feature that exists in pretty much all CI systems, has not been merged yet, and has been actively ignored for over a year.

Totally agree, to me this change is not even a feature but a bug fix!

@Alexander-Bartosh
Copy link

Alexander-Bartosh commented May 30, 2022

@shailesh-sk I would completely agree with @the-rule !
@microsoft/akvelon-build-task-team is @shailesh-sk still the code owner of Tasks/PublishTestResultsV2/ ?
@anatolybolshakov could you please help us checking that ?

@JoostvdB94
Copy link

Maybe anyone else who can review this PR? @DenisRumyantsev?
Very strange that such a small improvement is stuck on review.

Adds an option that lets the user configure the task to fail in case no
test result files have been found. This serves as a safeguard to make
sure that the test-run task and this task has been configured properly
to find the test result files.

Solves microsoft#13275
Instead of using hardcoded English string, lets use the localized
version that already exists.
@eholman
Copy link

eholman commented Jan 11, 2023

@navin22 can you maybe help? This is such a small PR with incredibly added value... I've seen you've done a review on this task in the past hence I'm mentioning you :-)

@navin22
Copy link
Member

navin22 commented Jan 11, 2023

Sorry folks, let me find the current maintainers.
Meanwhile @rasunkar any help ?

@eholman
Copy link

eholman commented Feb 22, 2023

@navin22 or @rasunkar is there no one to be found?

@github-actions
Copy link

This PR is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the PR otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Aug 21, 2023
@walliski
Copy link
Author

Beep boop

@github-actions github-actions bot removed the stale label Aug 21, 2023
@triptijain2112
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@triptijain2112
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@triptijain2112
Copy link
Contributor

Merged in Pull request: #18931
This would be available in version 2.228.0

@walliski walliski deleted the fail-if-no-results branch September 11, 2023 08:44
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.

9 participants