Project

General

Profile

Actions

Bug #22339

closed

Hook timeout may not have the good value

Added by Vincent MEMBRÉ about 1 year ago. Updated 9 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

We have inverted a value for sync run of hooks between warn and kill timeout.
This mostly affects tests, but also node acceptance hooks.

We also have too much errors on our ci about timeout so let's augment them to 5 seconds


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #18915: We don't know when generation hooks takes more time than expected, massively impacting generation timeReleasedNicolas CHARLESActions
Actions

Also available in: Atom PDF