Call for testing in preparation to 0.3.14

[Aleksey Bragin]

Hello testers,
your help is greatly needed.

Trunk needs to be tested using this template as a guideline 
http://www.reactos.org/wiki/Tests_for_0.3.14
Imagine that trunk is a 0.3.14 RC (I don't want to branch because I 
already called for a feature freeze, so essentially trunk is in "release 
mode" right now, and branching would just require merging all revisions 
from trunk to the branch).

Fill in the revision number in the "comments" section of that page when 
you test.

Also, please be prepared that this might be a double work because after 
testing more changes (fixes) would come in and eventually require 
retesting, but it is vital to get clear non-biased understanding on how 
well trunk performs right now.

Thank you,
looking forward to see results,
Aleksey Bragin.

[Ged Murphy]

When was feature freeze called?
I noticed Caemyr said the same thing in the HDD geo discussion.
I didn't see anything on ros-dev, did I miss it?

Ged.

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Aleksey Bragin
Sent: 06 December 2011 20:40
To: ReactOS Development List
Subject: [ros-dev] Call for testing in preparation to 0.3.14

Hello testers,
your help is greatly needed.

Trunk needs to be tested using this template as a guideline 
http://www.reactos.org/wiki/Tests_for_0.3.14
Imagine that trunk is a 0.3.14 RC (I don't want to branch because I 
already called for a feature freeze, so essentially trunk is in "release 
mode" right now, and branching would just require merging all revisions 
from trunk to the branch).

Fill in the revision number in the "comments" section of that page when 
you test.

Also, please be prepared that this might be a double work because after 
testing more changes (fixes) would come in and eventually require 
retesting, but it is vital to get clear non-biased understanding on how 
well trunk performs right now.

Thank you,
looking forward to see results,
Aleksey Bragin.

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

[Aleksey Bragin]

On 07.12.2011 0:45, Ged Murphy wrote:
> When was feature freeze called?
> I noticed Caemyr said the same thing in the HDD geo discussion.
> I didn't see anything on ros-dev, did I miss it?
>
> Ged.

This one - 
http://www.reactos.org/archives/public/ros-dev/2011-October/014898.html

WBR,
Aleksey.

[Ged Murphy]

Haha, nice try.
That was a request for a 'bugfixing week' as you called it, and was 2 months
ago.

Ged.

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Aleksey Bragin
Sent: 06 December 2011 21:54
To: ReactOS Development List
Subject: Re: [ros-dev] Call for testing in preparation to 0.3.14

On 07.12.2011 0:45, Ged Murphy wrote:
> When was feature freeze called?
> I noticed Caemyr said the same thing in the HDD geo discussion.
> I didn't see anything on ros-dev, did I miss it?
>
> Ged.

This one - 
http://www.reactos.org/archives/public/ros-dev/2011-October/014898.html

WBR,
Aleksey.

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev

[Colin Finck]

Aleksey Bragin [e-mail] wrote:
> Trunk needs to be tested using this template as a guideline
> http://www.reactos.org/wiki/Tests_for_0.3.14

If I was a tester, I'd like to know exactly what build to test. 
Especially considering that we have RBuild and CMake builds now, and 
both from Windows and Linux slaves.

And if you still want to release this year, someone should already begin 
collecting important changes since 0.3.13 for the Changelog and press 
release.
I recall numerous branch remerges along with many vital fixes, would be 
a shame if any important one is forgotten.

- Colin

[Bernd Blaauw]

Op 6-12-2011 21:40, Aleksey Bragin schreef:
> Hello testers,
> your help is greatly needed.
>
> Trunk needs to be tested using this template as a guideline
> http://www.reactos.org/wiki/Tests_for_0.3.14

Testing against [ http://www.reactos.org/wiki/Installing_ReactOS ] is 
much more entertaining. How are applications tested and approved as 
working? Just a 'most normal/regular actions work' I guess followed by a 
'didn't try exotic things like printing from this program'.

Are you providing win32 QEMU 1.0 binaries as test environment?

bootcd-dbgwin-54599 on QEMU (84MB) gives the following for example:

(P:\Trunk_slave\x86_CMake\build\base\services\svchost\svchost.c:65) 
Could not open service key 
(SYSTEM\CurrentControlSet\Services\☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥►☻►☻►☻►☻►☻►☻é♥é♥é♥é♥é♥é♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥
☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥►☻►☻►☻►☻ ☻\Parameters)
(P:\Trunk_slave\x86_CMake\build\base\services\svchost\svchost.c:65) 
Could not open service key (SYSTEM\CurrentControlSet\Services\☻ 
☻►☻☻♥►☻►☻►☻►☻\Parameters)
(P:\Trunk_slave\x86_CMake\build\base\services\svchost\svchost.c:65) 
Could not open service key (SYSTEM\CurrentControlSet\Services\♥►☻☺♥►☻☺♥ 
☻☺♥ ☻ ☻►☻►☻►☻►☻►☻►☻►☻\Parameters)
(P:\Trunk_slave\x86_CMake\build\base\services\svchost\svchost.c:65) 
Could not open service key (SYSTEM\CurrentControlSet\Services\☻\Parameters)
(P:\Trunk_slave\x86_CMake\build\base\services\svchost\svchost.c:65) 
Could not open service key (SYSTEM\CurrentControlSet\Services\☻☻♥►☻☻♥ 
☻☻♥☺♥H☻►☻►☻►☻►☻►☻►☻►☻►☻►☻↕♥►☻►☻0☻►☻►☻►☻►☻¶☻¶☻►☻↕♥►☻►☻►☻¶☻↕♥►☻►
☻►☻►☻►☻☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥☺♥►☻☺♥☺♥☺♥☺♥☺♥☺♥☺♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥►☻☻♥☻♥☻♥☻♥☻♥☻♥☻♥☻♥¶♦c\Parameters)
WARNING:  RtlSetUnhandledExceptionFilter at 
P:\Trunk_slave\x86_CMake\build\lib\rtl\exception.c:186 is UNIMPLEMENTED!
(P:\Trunk_slave\x86_CMake\build\ntoskrnl\ps\query.c:1268) Unsupported or 
unimplemented: 22
Boot took 16472240478 cycles!
Interrupts: 1623 System Calls: 13988 Context Switches: 2004

[Pierre Schweitzer]

Hi,

in case you were having issues for testing due to broken rapps links,
please retest now. They have been fixed.

Regards,
Pierre

Le mercredi 07 décembre 2011 à 00:40 +0400, Aleksey Bragin a écrit :
> Hello testers,
> your help is greatly needed.
>
> Trunk needs to be tested using this template as a guideline 
> http://www.reactos.org/wiki/Tests_for_0.3.14
> Imagine that trunk is a 0.3.14 RC (I don't want to branch because I 
> already called for a feature freeze, so essentially trunk is in "release 
> mode" right now, and branching would just require merging all revisions 
> from trunk to the branch).
>
> Fill in the revision number in the "comments" section of that page when 
> you test.
>
> Also, please be prepared that this might be a double work because after 
> testing more changes (fixes) would come in and eventually require 
> retesting, but it is vital to get clear non-biased understanding on how 
> well trunk performs right now.
>
> Thank you,
> looking forward to see results,
> Aleksey Bragin.
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev