I will commit the uniata update that fixes the boot.
We have 2 bugs about it.
 
Kind regards,



Sylvain Petreolle


De : Hermès BÉLUSCA - MAÏTO <hermes.belusca@sfr.fr>
À : 'ReactOS Development List' <ros-dev@reactos.org>
Envoyé le : Mercredi 29 octobre 2014 19h37
Objet : Re: [ros-dev] BuildBot changes

(ntoskrnl/io/iomgr/driver.c:1630) '\Driver\sacdrv' initialization failed,
status (0xc0000037)
(ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\sacdrv'
(hal/halx86/legacy/bussupp.c:1159) Slot assignment for 5 on bus 0
(hal/halx86/legacy/bus/pcibus.c:719) WARNING: PCI Slot Resource Assignment
is FOOBAR
[SYSREG] timeout
Exception occured in the LogReader.Run():
Thread was being aborted.

Normally, if I recall correctly, the next drivers to be loaded are Uniata /
disk drivers... Something failing at this point?

H.



-----Message d'origine-----
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Colin Finck
Envoyé : mercredi 29 octobre 2014 19:12
À : ros-dev@reactos.org
Objet : Re: [ros-dev] BuildBot changes

Thomas Faber wrote:
> Looks like VBoxManage fails to communicate with the RPC server due to
> session 0 isolation.

Thomas, that was it indeed, many thanks for the hint!
While it wasn't running as a service but from Task Scheduler, it was also
running in session 0. VBoxVMService was no option for us, but I could put
the Buildslave task into a user session now by starting it only when the
user logs in and then auto-logging in that user on system startup.

With the help of Amine and Sylvain, sysreg3 is also getting its debug log
now.

What's still not working is ReactOS itself though:
* bootcd works well, but bootcdregtest doesn't boot up at all, see
http://build.reactos.org/builders/Carrier-Win7%20VBox-Testbot/builds/43/step
s/test/logs/stdio
I've put up this bootcdregtest for download at
http://iso.reactos.org/temp/bootcdregtest_win7_broken.7z

* The building process of the bootcdregtest also leaves out the gnutls files
in the modules/optional folder, see
http://build.reactos.org/builders/Trunk_x86_GCCWin%20Debug/builds/48/steps/c
ompile_5/logs/stdio
They definitely exist though, I've checked it in Explorer.

Can anybody help here? Maybe these problems are even reproducible on Windows
hosts?

Cheers,

Colin


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev