I left that program running overnight. This morning I found: root@builder:~# go get github.com/gin-gonic/gin go get gopkg.in/robfig/cron.v2 root@builder:~# go get gopkg.in/robfig/cron.v2 root@builder:~# go run x.go [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. - using env: export GIN_MODE=release - using code: gin.SetMode(gin.ReleaseMode) [GIN-debug] Listening and serving HTTP on :8085 2020/05/09 00:00:00 Job started at 12:00AM 2020/05/09 01:00:00 Job started at 01:00AM 2020/05/09 02:15:00 Job started at 02:15AM 2020/05/09 03:05:00 Job started at 03:05AM 2020/05/09 04:35:00 Job started at 04:35AM 2020/05/09 05:50:00 Job started at 05:50AM This is under Linux (Ubuntu 16.04) with go 1.13.4 It's possible that the cron library doesn't work properly under Windows, and/or it doesn't work properly under go 1.14. What exact version of go did you use - when you say 1.14 do you mean 1.14.0 ? There were some major changes (in particular preemptive scheduling), and subsequent patch releases have fixed some bugs. If you didn't use 1.14.2, then retest with that. If it still fails with 1.14.2, then I suggest you either take this to the github tracker for the cron package, or look at what cron is doing under the hood and see if you can reproduce the problem under Windows in a few lines of code that *doesn't* use the cron library. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/cfda6002-8d49-4b50-83a2-a9d191f01031%40googlegroups.com.
