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

Execution times 2hours gap #2526

Open
MathisSenicourt opened this issue Apr 18, 2024 · 1 comment
Open

Execution times 2hours gap #2526

MathisSenicourt opened this issue Apr 18, 2024 · 1 comment

Comments

@MathisSenicourt
Copy link
Contributor

There is a strange behavior on execution times.
Campaigns that take 14 seconds or less to execute have a duration time of 120 minutes on tag information.

image

Somehow it seems that we have different hours on executions on the same campaign:

image
(table testcasestepexecution)

As you can see we have a difference of 2 hours on the same campaign.

image

@vertigo17
Copy link
Member

Can you share the result of SQL:

select id, Start, End, DateCreated , DateModif from cerberus.testcaseexecution order by id desc;

by filtering around the timing where those things happen.

Can you check
1/ the timezone of the application server (tomacat) ?
2/ the timezone of the database server ?

FYI, start and end are coming from Application server.
DateCreated and DateModif are set from database.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants