In a visual/manual check, all tests also passed.
Has anyone else experienced something like this?
In a visual/manual check, all tests also passed.
Has anyone else experienced something like this?
Are you running the tests locally? Care to share your code and the test output? It’s pretty hard to debug issues without seeing any details. The more details you can provide, the better able we are to help you!
(Please use codeblocks to share text and not screenshots!!)
Sorry for that!
Here’s my code:
UPDATE gigasecond
SET result =
STRFTIME('%FT%T', DATETIME(UNIXEPOCH(moment) + 1000000000, 'UNIXEPOCH'))
;
and here the local output:
main: "" r/w
+-------------------------------------------------+--------+---------+
| name | status | message |
+-------------------------------------------------+--------+---------+
| date only specification of time | pass | null |
| second test for date only specification of time | pass | null |
| third test for date only specification of time | pass | null |
| full time specified | pass | null |
| full time with day roll-over | pass | null |
+-------------------------------------------------+--------+---------+
The website reports that all tests failed, but doesn’t give me any clues as to what’s wrong.
I still have not yet messed around with the test runners. @glennj would you perhaps have time to poke at this? I see failed tests but no details. We may not be generating the json report correctly.
If I run this locally, stderr is empty, stdout is:
gigasecond: testing...
gigasecond: done
and results.json is:
{
"version": 1,
"status": "fail",
"message": ""
}
The 3.44.0 change log includes:
New conversion letters on the strftime() SQL function: %e %F %I %k %l %p %P %R %T %u
Those might not be supported on the test runner.
The installation doc says,
Testing for this track is based on version 3.37.
3.38 change log says,
Added the unixepoch() function.
Thank you for your help!
I can dig into the test runner with that specific sqlite version, but not today.