Workflow error: Install Win32OpenSSL fails

[fdcastel]

I'm working on a PR for #153, but I’m having trouble reproducing the build process.

I only changed main.yml to run on pushes from any branch:

on:
  push:
    branches: [ "*" ]
  pull_request:
    branches: [ "*" ]

But it is failing with

Also, do we really need to build PostgreSQL from source just to test the ODBC driver? Couldn’t we use the latest stable installer or prebuilt artifacts instead?

[davecramer]

You don't need to build it from source.
In order to fix the above problem, it is the version. They update this pretty regularly.

currently 3.3.6 https://slproweb.com/products/Win32OpenSSL.html

[fdcastel]

Thank you, @davecramer!

Updating OPENSSL_VERSION to 3_3_6 indeed did the trick! The workflow is now moving forward (building postgres now). 👍🏻

That said, I’m still a bit puzzled, though. I went through the (failed) logs and couldn’t spot the actual reason it was failing. It looks like the download completed successfully:

So why did the install step fail?

Is there another place where 3_3_5 / 3_3_6 is being referenced that I’m missing?

Mostly asking because it might be worth improving the error message and saving the next “noob” from running into the same thing the next time the OpenSSL version bumps again 😄

[fdcastel]

Oh man… the build is still running. 😅

I suppose this is probably only on the first run because of the GitHub cache -- but still…

Would you be open to a PR to modernize the current workflow?

Possible improvements:

• install PostgreSQL from a pinned release (instead of building from source), and
• run x86 and x64 test jobs in parallel

Of course, I'm a complete newbie, so I might be missing something 😄 -- If there are solid reasons for keeping it as-is, I totally understand.