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

Artifacts directory name can be too long #84

Open
elv1s42 opened this issue Jun 7, 2023 · 4 comments
Open

Artifacts directory name can be too long #84

elv1s42 opened this issue Jun 7, 2023 · 4 comments

Comments

@elv1s42
Copy link
Contributor

elv1s42 commented Jun 7, 2023

When I have a long test name (for [TestCase] tests with several arguments or for the tests with long namespaces) the teamcity-event-listener may produce the folder names that are too long for Windows (longer than 255 symbols). As a result, the artifacts cannot be published because the folder cannot be created

@elv1s42
Copy link
Contributor Author

elv1s42 commented Jun 8, 2023

I'm going to try this fix:
image

Do we need a test name in the path for the TeamCity artifacts?

NikolayPianikov added a commit that referenced this issue Aug 28, 2023
@hn100823
Copy link

hi @NikolayPianikov may I ask when will we have the new release for this?
As I see here
https://www.nuget.org/packages/NUnit.Extension.TeamCityEventListener
The latest version is 1.0.7 from 2019
Will this be included in the newer version of Nunit (which version)
or we have to install it separately?

@NikolayPianikov
Copy link
Member

1.0.9 was published

@hn100823
Copy link

hn100823 commented Oct 9, 2023

Thank you, when will you add this to the release page?
https://github.com/nunit/teamcity-event-listener/releases

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