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

Persistent "Could not parse into format" error #38

Open
brightshine1111 opened this issue Feb 25, 2021 · 1 comment
Open

Persistent "Could not parse into format" error #38

brightshine1111 opened this issue Feb 25, 2021 · 1 comment

Comments

@brightshine1111
Copy link

I have the working hours plugin installed on my Jenkins master, and whenever the local time is outside of the configured working hours, the log gets filled with hundreds of these error messages:

Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
Could not parse into format HHmm
2021-02-25 23:33:48.642+0000 [id=133]    INFO    o.j.p.w.WorkingHoursQueueTaskDispatcher#log: Blocking item 345921
021-02-25 23:33:48.643+0000 [id=133]    INFO    o.j.p.w.WorkingHoursQueueTaskDispatcher#log: Blocking item 345922

I'm running the latest available version of the working hours plugin (1.1) with Jenkins 2.263.3, but this has been an issue for months now.

My configuration for the working hours plugin looks like so:
Screen Shot 2021-02-25 at 5 32 56 PM

I've tried changing 00:00 to 0:00, no change in the logging. The working hours plugin is working as expected - it's blocking jobs outside the configured working hours - yet it's still spamming the system log with these parse errors.

@brightshine1111 brightshine1111 changed the title Persistent "Could nor parse into format" error Persistent "Could not parse into format" error Feb 25, 2021
@yo-cleon
Copy link

yo-cleon commented Dec 7, 2022

I'd got the same problem. Is there any solution? Jenkins version 2.332.2, plugin version 1.1

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

No branches or pull requests

2 participants