Re: [Oorexx-devel] Side effects of the recent rollback for Windows?

2021-08-17 Thread Erich Steinböck
>
> I am not sure how this should be fixed
>
I fixed the test to skip the assert if the WMI interface cannot determine a
default printer

all 6 Windows builds (32 and 64) are reported as failures for this reason
> meaning no fresh Win builds are uploaded to Sourceforge
>
Uploads should still happen.  Build artifact uploads depend on a successful
build, not as successful test
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Side effects of the recent rollback for Windows?

2021-08-17 Thread P.O. Jonsson
Ok, so I checked a bit more. All Win machines have 3-4 physical or virtual 
printers defined per default, there is no difference for the W10 machine and 
the W7/W8.1 VMs.

It seems no printer is defined as a default printer in Windows unless the user 
defines one. I marked one printer as default for all 3 Wins and tested again 
but the result is similar

Interpreter:REXX-ooRexx_5.0.0(MT)_32-bit 6.05 12 Aug 2021
OS Name:WindowsNT
SysVersion: Windows 10.0.19043

Tests ran:  24292
Assertions: 375393
Failures:   1
Errors: 0

[failure] 20210816 10:07:05.825000
  svn:r12287   Change date: 2021-08-15 17:56:43 +0200
  Test:   TESTDEFAULTPRINTER
  Class:  Printers.testgroup
  File:   ...\ooRexx\extensions\platform\windows\ole\Printers.testGroup
  Line:   93
  Failed: assertSame
Expected: (none)
Actual:   Microsoft Print to PDF
Message:  when run in a VM, this test may fail due to redirected printers

Interpreter:REXX-ooRexx_5.0.0(MT)_32-bit 6.05 12 Aug 2021
OS Name:WindowsNT
SysVersion: Windows 10.0.19043

Tests ran:  24292
Assertions: 375393
Failures:   1
Errors: 0

File search:00:00:06.737000
Suite construction: 00:00:01.234000
Test execution: 00:08:02.953000
Total time: 00:08:10.925000

I could not find a way to „undefine“ the default printer. I tried to delete the 
printer and attach it again but Windows marked it as the default printer again.

I am not sure how this should be fixed. This may not be a serious problem but 
currently all 6 Windows builds (32 and 64) are reported as failures for this 
reason meaning no fresh Win builds are uploaded to Sourceforge.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 15.08.2021 um 18:01 schrieb Erich Steinböck :
> 
> Hi P.O., the VM'ed Windows shows the default printer of the host from which 
> it is being executed.
> This is a situation the test case cannot easily handle, but in a typical (non 
> VM'ed) scenario it will work and successfully tests SysWinGetDefaultPrinter.
> I've fixed the NOVALUE issue and added a message that the test may fail in 
> run in a VM.
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel