pywin32_testall.py should show failure to run adodbapi tests as them being "skipped" rather than as failing.

[futuremotiondev]

Expected behavior and actual behavior.

Expected: The script to complete successfully without error. Actual: Failure with 21 errors.

Steps to reproduce the problem.

1. Install Python 3.10.5 amd64 for Windows (I have mine installed in C:\Python\Python310)
2. Download and run pywin32-304.win-amd64-py3.10.exe
3. Let the install complete and then open an admin command prompt to C:\Python\Python310\Scripts
4. Paste this to the command line: python pywin32_testall.py and press enter to run.
5. Wait for the script to finish.
6. On my machine the script reported FAILED (errors=21)

Here is the full error log:

https://pastebin.com/E4TMtg1W

Version of Python and pywin32 Python: Python 3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)] on win32 pywin32: pywin32-304.win-amd64-py3.10.exe

Any help or clarification whether this is in-fact a problem would be great.

[mhammond]

pywin32_testall.py accepts a -skip-adodbapi. I really should ensure that these tests don't actually "fail" by default though (but I still want them to run of the adodbapi drivers are available), so I'll adopt this to do that.

[vernondcole]

I have attempted to always keep an Internet enabled copy of Microsoft SQL Server running to serve as a test bed for adodbapi. Microsoft provides the VM for that on an Azure cloud server, but that has its own set of problems. Perhaps there would be a better solution, now that we have tooling for CI-CD in place -- so that a copy of SQL Server (or the express version) could be maintained as part of the CI-CD facility. That would be nice.

But this, the lack of a "provider" driver, is a different problem. I thought that there was at least one ADO provider which shipped with stock copies of Windows 10. And I thought that I had identified it as MSOLEDBSQL. Apparently I was wrong. I no longer use SQL Server on a regular basis, so I get out of touch. Is there someone out there who can advise which ADO provider might be a better option?

Lacking any of that, perhaps we could tool up to do a regular test of adodbapi using a subset of its capabilities on a simple on-machine data source, such as ACCESS or spreadsheets? Then more extensive tests could be run on some more occasional schedule to test the full operation.

I'm open for any suggestions.

On Sun, Jul 24, 2022 at 5:35 PM Mark Hammond @.***> wrote:

pywin32_testall.py accepts a -skip-adodbapi. I really should ensure that these tests don't actually "fail" by default though (but I still want them to run of the adodbapi drivers are available), so I'll adopt this to do that.

— Reply to this email directly, view it on GitHub https://github.com/mhammond/pywin32/issues/1918#issuecomment-1193418128, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEZOBOUREQFNXAQIXMPROTVVXHMLANCNFSM54OXXONA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[mhammond]

The perfect scenario would probably be for github actions to arrange for an adodb. It looks like azure is possible, but that requires an account and seems a little overkill.

[xflatkds1]

I'm not sure why I got this email, but your trying from what I read a 32 bit test function on a 64 bit version , I would figure 32 errors not 21.

It looks like your using 64 bit because you have a 64 bit computer. You can run a 32 but on 64 bit machine , but using a 32 on 64 if it's testing it logic stimulates a negative response.

Pywin 32 on a 64 bit version at least to me would error out and fail.

UpTo you I'd try a 32bit install if using 32bit test and 32 bit version of pywin 32. Not familiar with pywin32_testall.py but to me memory holes due to a 64bit python. I could be wrong though but if testing something a 64bit running a 32bit seems to me address issues. I'd look up try googling differences on 64bit vs 32bit addressing logic.

Hammond would know better, I use 32bit python on a 64bit machine and pywin32 so not to cause memory issues. As I said if test all is checking 32bit addresses on a python 64 bit version, I'd think errors because pywin32 on 64bit software.

On Sat, Jul 23, 2022, 6:51 PM Jay @.***> wrote:

Expected behavior and actual behavior.

Expected: The script to complete successfully without error. Actual: Failure with 21 errors.

Steps to reproduce the problem.

1. Install Python 3.10.5 amd64 for Windows (I have mine installed in C:\Python\Python310)
2. Download and run pywin32-304.win-amd64-py3.10.exe
3. Let the install complete and then open an admin command prompt to C:\Python\Python310\Scripts
4. Paste this to the command line: python pywin32_testall.py and press enter to run.
5. Wait for the script to finish.
6. On my machine the script reported FAILED (errors=21)

[image: cmd_fcvuizziLS] https://user-images.githubusercontent.com/33441569/180626366-19faadd0-43eb-40e2-86d1-a10d543637cb.png

Here is the full error log:

https://pastebin.com/E4TMtg1W

Version of Python and pywin32 Python: Python 3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)] on win32 pywin32: pywin32-304.win-amd64-py3.10.exe

Any help or clarification whether this is in-fact a problem would be great.

— Reply to this email directly, view it on GitHub https://github.com/mhammond/pywin32/issues/1918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASDFKH7DZ4BL6COG2DJMUXTVVSAPHANCNFSM54OXXONA . You are receiving this because you are subscribed to this thread.Message ID: @.***>