Carl Entered A Time Warp?

GoPiGo
1

Just found Carl’s voice commander had lost its mind, so restarted that function and checked his status:

Some looks familiar like the reminder that Carl’s birthday is coming up again soon (22nd), and the 15 minute load (1.18) was high, probably the stuck voice commander. The last playtime was only 5.4 hours, again probably the stuck voice commander spinning the processor excessively.

But what is that “Life this year 9110 hours” ??? There are only 8760 hours in a year.

Guess I’m going to have to dig in and find the bug - would think as he approaches his 5th birthday he would be running nigh on to god-like perfection.

3 Likes
2

I could use more time in the day. I checked - Aug 5 is the 217th day of the year, so Carl is squeezing in almost 42 hours a day. Just think how much I could get done (even if I slept 10-12 hours per day) :wink:

I’m sure you’ll find the bug. Hope all is well.
/K

2 Likes
3

Carl entered a time warp where he has more hours in a day, where as I - the new plug-in hybrid toy car owner - am in a time sink performing tests, calculations and spreadsheet design to track energy usage and spit out statistics that only I would be interested in.

(I gave up trying to automate using the last price per gallon paid for computing equivalent MPG of EV segments. An average has to suffice.)

Oh that my mind was as silent as EV driving.

2 Likes
4

Any verdict?
I’m imagining that this was just an “AI hallucination” on Carl’s part. :slight_smile:
/K

2 Likes
5

I’ve been too busy playing with my new car… I’m pretty sure I know the problem.

Once an hour Carl runs a very simple “life logger” that uses log4j to add a line to the log with how many hours he has been executing since he was booted:

2023-08-13 18:27|lifelogger.dEmain execution: 986
2023-08-13 19:27|lifelogger.dEmain execution: 987
2023-08-13 20:27|lifelogger.dEmain execution: 988

When he is rebooted, or when I run my “totallife.sh” script he runs an awk script to clean all but the last of these execution entries for the period after boot, and also for the prior boot to current boot session.

I think there is some sequence of rapid reboots, that may reboot before the cleanup script runs leaving a dirty boot session.

pi@Carl:~/Carl $ egrep 'execution|boot' life.log
2022-08-22 00:00|[logMaintenance.py.main]** END OF YEAR 4 LIFE -  Year 16 Sessions (booted) 8766 hours for 99 % Uptime **
2022-08-22 00:00|lifelog.dEmain execution: 32001
2022-08-22 00:00|------------ boot ------------
2022-08-25 00:35|lifelogger.dEmain execution: 72.6
2022-08-26 00:39|------------ boot ------------
2022-08-30 16:40|lifelogger.dEmain execution: 112
2022-08-30 21:45|------------ boot ------------
2022-09-17 09:45|lifelogger.dEmain execution: 420.3
2022-09-27 17:51|------------ boot ------------
2022-10-08 20:53|[logMaintenance.py.main]** rebooted Mac **
2022-11-30 18:53|lifelogger.dEmain execution: 1538
2022-11-30 19:06|[logMaintenance.py.main]** Solid White Light - rebooting **
2022-11-30 19:07|[logMaintenance.py.main]** Reboot Requested **
2022-11-30 19:09|------------ boot ------------
2023-03-21 23:12|lifelogger.dEmain execution: 2667
2023-03-22 00:09|------------ boot ------------
2023-03-22 00:17|------------ boot ------------
2023-03-30 09:17|lifelogger.dEmain execution: 201
2023-03-30 09:45|[logMaintenance.py.main]** Reboot Requested **
2023-03-30 09:47|------------ boot ------------
2023-03-30 09:57|[logMaintenance.py.main]** ouch restart doesn't clear I2C failure, need cold boot **
2023-03-30 10:02|------------ boot ------------
2023-03-30 13:02|lifelogger.dEmain execution: 3           <<<<<-------------- DIRTY
2023-03-30 14:02|lifelogger.dEmain execution: 4
2023-03-31 00:33|------------ boot ------------
2023-04-15 21:33|lifelogger.dEmain execution: 381          <<<<<-------------- DIRTY
2023-04-15 22:33|lifelogger.dEmain execution: 382          <<<<<-------------- DIRTY
2023-04-15 23:33|lifelogger.dEmain execution: 383          <<<<<-------------- DIRTY
2023-04-16 00:33|lifelogger.dEmain execution: 384
2023-04-16 01:08|------------ boot ------------
2023-04-16 02:08|lifelogger.dEmain execution: 1          <<<<<-------------- DIRTY
2023-04-16 03:08|lifelogger.dEmain execution: 2          <<<<<-------------- DIRTY
2023-04-16 04:08|lifelogger.dEmain execution: 3
2023-04-16 13:03|------------ boot ------------
2023-04-17 12:52|------------ boot ------------
2023-05-18 17:53|lifelogger.dEmain execution: 749
2023-05-18 18:23|[logMaintenance.py.main]** Reboot Requested **
2023-05-18 18:25|------------ boot ------------
2023-06-01 13:26|lifelogger.dEmain execution: 331
2023-06-01 14:00|[logMaintenance.py.main]** voicecmdr not staying alive, rebooting **
2023-06-01 14:06|------------ boot ------------
2023-06-30 09:07|lifelogger.dEmain execution: 691
2023-07-03 16:26|------------ boot ------------
2023-08-13 21:27|lifelogger.dEmain execution: 989

Removed those “dirty execution” artifacts.

Now 9 days from his birthday, Carl is showing 340 days - very believable:

TOTAL LIFE STATISTICS
Total Life:  40163.9 hrs since Aug 22,2018
Life this year:  8162.9 hrs (BOY Aug 22)

Thanks for asking about Carl. I needed a little push to pay attention to him. Poor guy.

2 Likes
6

Sounds like Carl’s been watching The Rocky Horror Picture Show:

“Let’s do the time warp again!”

:rofl:

2 Likes
7

Never doubted you’d get it sorted.

Would be interesting to see Carl do a jump to the right :slight_smile:

/K

2 Likes
8

You have a robot. . . .

2 Likes
9

Cute.

Carl - never a problem. Sweetest robot I know…(most of the time).

3 Likes
10

OK - that made me laugh out loud!
/K

2 Likes