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

serenity report : stackoverflow error #972

Closed
mmanach opened this issue Oct 16, 2017 · 4 comments
Closed

serenity report : stackoverflow error #972

mmanach opened this issue Oct 16, 2017 · 4 comments

Comments

@mmanach
Copy link

mmanach commented Oct 16, 2017

Hello,

  • serenity core / gradle : 1.6.5
  • serenity jbehave : 1.30
  • Windows 10 64 bits

Since upgrading serenity core / gradle from 1.5.9 and jbehave from 1.27, I have this error log when I execute

gradle clean test aggregate
        at net.thucydides.core.reports.html.Breadcrumbs$BreadcrumbsBuilder.fromTagsIn(Breadcrumbs.java:32)
SOME REPORT PAGES COULD NOT BE GENERATED
 * Failed to generate report for TagReportingTask for TestTag{name='Logout/Logout', type='story'} - java.util.concurrent.ExecutionException: java.lang.StackOverflowError
net.thucydides.core.reports.html.Breadcrumbs$BreadcrumbsBuilder.elementsOf(Breadcrumbs.java:43)

(but the build is green)

It seems that the reason of this error is in my logout.story :

Meta:
@issue #TPSVC-3373

When I remove the '@issue' tag, there is no longer this stacktrace.

@wakaleo
Copy link
Member

wakaleo commented Oct 16, 2017

Can you provide a sample project?

@mmanach
Copy link
Author

mmanach commented Oct 16, 2017

Yep I will tomorrow. Seems that the same name for folder and story is involved too.

@mmanach mmanach changed the title report : @issue meta tag causing stackoverflow error serenity report : stackoverflow error Oct 17, 2017
@mmanach
Copy link
Author

mmanach commented Oct 17, 2017

https://github.com/mmanach/serenity-issue-972

So it seems that the cause is a combination of same folder name / story name and story meta tag "@issue"

wakaleo added a commit that referenced this issue Oct 17, 2017
@wakaleo
Copy link
Member

wakaleo commented Oct 17, 2017

Should be fixed in 1.6.6

@wakaleo wakaleo closed this as completed Oct 17, 2017
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

2 participants