Access CI doesn't work consistently

[ghuysmans]

No description provided.

[ghuysmans]

Once it's done, publish it as a standalone GitHub Action.

[ghuysmans]

This works on a self-hosted runner.

[mohitsaxenaknoldus]

You can give me some more info on this? Like why does it work on a self-hosted runner and what kind of inconsistency are we talking about here?

[ghuysmans]

There are two kinds of inconsistencies:

• It looks like AccessDatabaseEngine_X64.exe silently fails: the driver is present but you can't use it.

  SOURCES_PARSENAME   : {3BE786A0-0366-4F5C-9434-25CF162E475E}
  SOURCES_DESCRIPTION : Microsoft Office 12.0 Access Database Engine OLE DB Provider
  SOURCES_TYPE        : 1
  SOURCES_ISPARENT    : False
  SOURCES_CLSID       : {3BE786A0-0366-4F5C-9434-25CF162E475E}
  ...
  Run cscript.exe //nologo utils\dump_access_views.vbs utils\sample.accdb >views.sql
  Provider cannot be found. It may not be properly installed.
  Error: Process completed with exit code 1.
  

• VBScript's stderr sometimes doesn't appear in GH Actions log:

  ...
  Run cscript.exe //nologo utils\dump_access_views.vbs utils\sample.accdb
    cscript.exe //nologo utils\dump_access_views.vbs utils\sample.accdb
    shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
  Error: Process completed with exit code 1.
  

[ghuysmans]

I suspect the driver to require a reboot...

[mohitsaxenaknoldus]

Does your app run on 32 bits architecture? Because AccessDatabaseEngine_X64.exe is 64 bits version that we are downloading.

[ghuysmans]

The scripts runs on the 64-bit interpreter. It worked just once (!) for the same commit (af00855, basically 4a19301 + f52aadb):

1. Success
2. Failure