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

Report link generated by AET Maven client doesn't work #76

Closed
jwadolowski opened this issue Mar 8, 2017 · 1 comment
Closed

Report link generated by AET Maven client doesn't work #76

jwadolowski opened this issue Mar 8, 2017 · 1 comment

Comments

@jwadolowski
Copy link
Contributor

Hey,

something odd just happened for one of our test suites. AET run finally went green (build 115), but report link that was generated at the very end of processing suddenly stopped working. Links generated for previous attempts (builds 106-114) worked without issues. Here's what exactly happened:

  • Jenkins job that runs AET finally turns green
    aet_report_issue00
    aet_report_issue01
  • when I click on the link the following gets displayed in the browser
    aet_report_issue02
  • when I click "OK" button, report says it can't load metadata
    aet_report_issue03

This is a bit related to #71. Build is green, theoretically all was successfully committed to MongoDB, but for some reason report doesn't work anymore.

Do you have any ideas what went wrong and how we can get that resolved?

Thanks,
Kuba

@jwadolowski
Copy link
Contributor Author

Discussed that with @Skejven and it turned out there there were additional AET executions after Mar 6, 4:50 PM (triggered by different pipeline). Due to default cleaner configuration only 2 last reports are kept in the database and that was the root cause of the problem.

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

1 participant