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.

Sign up for GitHub

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

Jump to bottom

Logs are not taking the leap second into account #17

Open
vmarkovtsev opened this issue Jan 5, 2017 · 0 comments
Open

Logs are not taking the leap second into account #17

vmarkovtsev opened this issue Jan 5, 2017 · 0 comments

Comments

@vmarkovtsev
Copy link
Contributor

The log messages are not strictly ordered with time. E.g.

2017/01/01 00:00:00 scheduler.go:103 ▶ DEBUG github-stars - Job started "0d97c4adebbf" - "/bin/sh -c ..."
2016/12/31 23:59:59 scheduler.go:120 ▶ ERROR github-stars - Job finished "0d97c4adebbf" in "-992.473897ms", failed: true, skipped: false, error: error starting exec: Unrecognized input header

I believe this happened because of the leap second.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vmarkovtsev