Since May 14, 2017, most Scute tests systematically FAIL when Scute is build by Jenkins in the "native" configuration. Here is an excerpt from the build output for May 14:
03:23:15 PASS: t-link 03:23:16 PASS: t-getfunctionlist 03:23:16 PASS: t-initialize 03:23:16 PASS: t-getinfo 03:23:16 FAIL: t-getslotlist 03:23:16 FAIL: t-getslotinfo 03:23:16 FAIL: t-gettokeninfo 03:23:16 FAIL: t-getmechanismlist 03:23:16 FAIL: t-getmechanisminfo 03:23:16 FAIL: t-opensession 03:23:16 FAIL: t-closeallsessions 03:23:16 FAIL: t-getsessioninfo 03:23:16 FAIL: t-findobjects 03:23:16 FAIL: t-getattribute 03:23:16 FAIL: t-auth 03:23:16 FAIL: t-generaterandom
According to some (quick) tests I have done, the only situation where I could get the t-getslotlist test to FAIL is if Scdaemon is not available on the system.
With Scdaemon present, and without a card reader, we should expect the t-getslotlist and t-getslotinfo tests to PASS and all the subsequent tests to SKIP. That's what I observe on my own test system, and that's also we used to have on Jenkins in all builds prior to May 14, such as this May 7 build:
03:21:47 PASS: t-link 03:21:47 PASS: t-getfunctionlist 03:21:48 PASS: t-initialize 03:21:48 PASS: t-getinfo 03:21:48 PASS: t-getslotlist 03:21:50 PASS: t-getslotinfo 03:21:50 SKIP: t-gettokeninfo 03:21:50 SKIP: t-getmechanismlist 03:21:50 SKIP: t-getmechanisminfo 03:21:50 SKIP: t-opensession 03:21:50 SKIP: t-closeallsessions 03:21:50 SKIP: t-getsessioninfo 03:21:50 SKIP: t-findobjects 03:21:50 SKIP: t-getattribute 03:21:50 SKIP: t-auth 03:21:50 SKIP: t-generaterandom
So I am guessing that something must have changed on the system where Jenkins performs its builds, sometimes between May 7 and May 14.
Could someone investigate that? Has Scdaemon been removed from the Jenkins system?
Is it possible to get the tests/test-suite.log file (generated by the tests) from a Jenkins build, in order to understand what caused the tests to fail (if it's not, as a I suspect, due to the absence of Scdaemon)?