Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Duplicate history trends

See original GitHub issue

It seems like the history trend is invalid.

Here is a simple repro case using the sample data:

In the allure-api-usage directory call python send_results.py
In the hosted api run generate-report on the default project

After a single test run I’m seeing a trend chart like:

Notice there are two entries for #1 this seems invalid.

Running allure server allure-results-example/ locally renders it like: which is what I expect to see.

It seems like the history is getting duplicated somehow.

Logs:

Starting reporting_allure_1 ... done
Attaching to reporting_allure_1
allure_1  | Not checking results automatically
allure_1  | ALLURE_VERSION: 2.13.4
allure_1  | Generating default report
allure_1  | ls: cannot access '/app/allure-docker-api/static/projects/default/reports': No such file or directory
allure_1  | Creating results directory for PROJECT_ID: default
allure_1  | Creating executor.json for PROJECT_ID: default
allure_1  | Generating report for PROJECT_ID: default
allure_1  | Report successfully generated to /app/allure-docker-api/static/projects/default/reports/latest
allure_1  | Status: 200
allure_1  | 2020-07-27 17:27:33.819:INFO::main: Logging initialized @699ms to org.eclipse.jetty.util.log.StdErrLog
allure_1  | Creating history on results directory for PROJECT_ID: default ...
allure_1  | Copying history from previous results...
allure_1  | Status: 200

This is my compose file:

version: '3'
services:
  allure:
    image: "frankescobar/allure-docker-service"
    environment:
      CHECK_RESULTS_EVERY_SECONDS: NONE
      KEEP_HISTORY: "TRUE"
      KEEP_HISTORY_LATEST: 25
    ports:
      - "5050:5050"
    volumes:
      - ${PWD}/projects:/app/projects

Issue Analytics

State:
Created 3 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

2reactions

fescobarcommented, Jul 28, 2020

@apulverizer you are right, I will fix soon. Thank you so much for your feedback.

1reaction

apulverizercommented, Jul 30, 2020

Verified with version 2.13.5. Thanks for the quick turn-around @fescobar

Top Results From Across the Web

How to avoid missing chrome history due to duplicate urls?

So there are situations you'd want to look at the complete history log. With the extension History Trends Unlimited you can do this....

Delete History Duplicate On Google Chrome | Short VD #1

Hello everyone, today I introduce one tip to delete multiple duplicate history url in google chrome.First, You open History by Ctrl+HSecond, ...

Duplicate Opportunities Showing on Historical Trending Report

Working with an Opportunities with Historical Treding Report and noticed that some opps are showing up twice in the details of the report,...

See your activity history, trends, and awards in Fitness on ...

In the Fitness app on iPhone, you can see your activity history, trends, and awards to keep track of your progress. See your...

Duplicate entry 'xx-xx' for key 'PRIMARY' - trends & history tables

Duplicate entry 'xx-xx' for key 'PRIMARY' - trends & history tables. 07-01-2011, 22:37. I've been seeing these messages since ramping up our monitoring...