Project

General

Profile

Actions
Copy link

Bug #15083

closed

Bug #14465: Generation fails with "Task FutureTask rejected from ThreadPoolExecutor" due to timeout in JS computation

Use human-readable durations in policy generation summary

Added by Vincent MEMBRÉ almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
5.0.12
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

Policy generation summary looks like this

[2019-06-13 16:20:02] INFO  policy.generation - Timing summary:
[2019-06-13 16:20:02] INFO  policy.generation - Run pre-gen scripts hooks     :          1 ms
[2019-06-13 16:20:02] INFO  policy.generation - Run pre-gen modules hooks     :          0 ms
[2019-06-13 16:20:02] INFO  policy.generation - Fetch all information         :       1213 ms
[2019-06-13 16:20:02] INFO  policy.generation - Historize names               :       1952 ms
[2019-06-13 16:20:02] INFO  policy.generation - Build current rule values     :        490 ms
[2019-06-13 16:20:02] INFO  policy.generation - Build target configuration    :     139890 ms
[2019-06-13 16:20:02] INFO  policy.generation - Write node configurations     :     259061 ms
[2019-06-13 16:20:02] INFO  policy.generation - Save expected reports         :       8056 ms
[2019-06-13 16:20:02] INFO  policy.generation - Run post generation hooks     :         17 ms
[2019-06-13 16:20:02] INFO  policy.generation - Number of nodes updated       :       2743   
[2019-06-13 16:20:02] INFO  policy.generation - Policy generation completed in: PT7M32.547S

But the period is not displayed correctly, it should be a human readable value

Actions
Copy link

Also available in: Atom PDF