Champion Level 3If you see https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops, section Download and configure the agent mentions changing the processor architecture to either x86 or x64 of the agent.
All of the agents have Windows 64 bit on them. But, are you thinking that if the Agent is setup as x86, then when TestExecute is kicked off, it will run the 32 bit version?
you should see what bitness is used in your vs test task log:
or go to your agent pools in Azure and check the capabilities from there:
Those all appear to be 64 bit. We have a 32 application (slowly being converted) and that is why we're wanting to launch TestExecute in 32 bit so we could query Oracle 32 bit.
Those images tell me about the Agent versions. I am just wanting to try and force TestExecute to be kicked of using the 32bit version.
You would need to reconfigure your agent to use 32 bit or create a new agent; all tasks run under that agent should be performed under the same bitness. The x64 agent version is intended for 64-bit Windows, whereas the x86 version is intended for 32-bit Window - found in the link rraghvani provided.
You could also look into using Session Creator w/command line parameters [here]. More info on TC bitness [here].
