Bug 12428 - Check your system clock
Summary: Check your system clock
Status: RESOLVED NOTABUG
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 2.4.1
Hardware: Other x86_64
: Low major
Target Milestone: 2.5
Assignee: prsolucoes
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-12-15 22:16 UTC by prsolucoes
Modified: 2018-10-12 16:37 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description prsolucoes 2017-12-15 22:16:40 UTC
Hi,

I get system clock error when i try build image.

All errors and logs is available here:

https://github.com/prsolucoes/docker-yocto

Thanks on any help to solve it.
Comment 1 Richard Purdie 2017-12-19 09:36:01 UTC
Have you tried making sure the clock is set correctly in your docker image? What does running "date" before you start the build say?

The bugzilla isn't really a way to ask for help, its for reporting problems in the codebase and I don't believe this is a problem in the codebase.
Comment 2 prsolucoes 2017-12-19 13:49:49 UTC
I make all changes trying solve it changing the clock. I put UTC as timezone, put the same of my machine (America/Sao_Paulo), but not solve. I use docker with a lot of other things, never get this problem.

I have an issue trying get a solution to this problem on stackoverflow:
https://stackoverflow.com/questions/47833647/yoctoproject-error-with-automake-and-system-clock/47834034?noredirect=1#comment82719945_47834034

The only way is make a patch removing the system clock check. Already have one patch to sanity.m4 (performance.patch) but not to other files.
Comment 3 Richard Purdie 2017-12-19 16:38:53 UTC
Rather than hacking it to remove the test, I'd *strongly* recommend trying to understand why this test is breaking and figure out how to fix it properly. It does sound like there is something very wrong with your environment. What does the "date" command show the date/time as?
Comment 4 prsolucoes 2017-12-19 16:43:25 UTC
Hi,

My date command now return:

Tue Dec 19 16:42:56 UTC 2017

Thanks.
Comment 5 Ross Burton 2017-12-21 15:41:53 UTC
The date output looks right.  It's possible that the timezone/time was wrong when the files were unpacked and although you've now set the correct time the old files are being used.  Can you delete build/tmp/ and try again, to remove the possibility that old files (from the future) are being used?
Comment 6 Stephano Cetola 2018-02-08 16:15:55 UTC
We believe this is a user error with the system clock. If not please reopen and ping us.