We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am seeing same date time for same test case but different runs.
I am running this job in every 5 minute interval from Jenkins and some times I am seeing this abnormalities. BTW this is the demo test file I am using: https://github.com/fescobar/allure-docker-service-examples/blob/master/allure-docker-python-pytest-example/tests/demo_test.py
For different test case runs, there should be different date time.
The text was updated successfully, but these errors were encountered:
closed as duplicate https://github.com/orgs/allure-framework/discussions/2407
Sorry, something went wrong.
No branches or pull requests
I'm submitting a ...
What is the current behavior?
I am seeing same date time for same test case but different runs.
I am running this job in every 5 minute interval from Jenkins and some times I am seeing this abnormalities. BTW this is the demo test file I am using: https://github.com/fescobar/allure-docker-service-examples/blob/master/allure-docker-python-pytest-example/tests/demo_test.py
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
For different test case runs, there should be different date time.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information
The text was updated successfully, but these errors were encountered: