testing on buildserver is broken

[Christoph von Wittich]

hangs with endless

ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!
(ARM³::MDLSUP:692) MDL PROBE FAILED!

[Timo Kreuzer]

It's still broken.

@ros-arm-bringup: Ignoring it doesn't make it go away! Fix please.


Christoph von Wittich schrieb:
>   hangs with endless
>
>  ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>  (ARMł::MDLSUP:692) MDL PROBE FAILED!
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>
>

[Dmitry Gorbachev]

Timo Kreuzer wrote:
>   It's still broken.
>
>  @ros-arm-bringup: Ignoring it doesn't make it go away! Fix please. 
It can take some time, I guess. They maybe even cannot reproduce the
bug on their machine. Please be patient...

[Timo Kreuzer]

I'd have less problem to be patient, if I knew they cared, but they
could as well be on vacation for a month.
And I don't like the idea of broken sysreg for a month.
It's the refusal to respond/provide information that is kinda annoying.

Yeah, yeah, they are code-ninjas-whatever, hiding in the dark, silently
sneaking into the code and stuff... but then they should stop breaking
things or they might suddenly face a code-samurai, screaming and jumping
at them ;)

Dmitry Gorbachev wrote:
>   Timo Kreuzer wrote:
>    
> >   It's still broken.
> >
> >  @ros-arm-bringup: Ignoring it doesn't make it go away! Fix please.
> >       
>  It can take some time, I guess. They maybe even cannot reproduce the
>  bug on their machine. Please be patient...
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>
>

[Thomas Bluemel]

Why don't you just talk to the "people" behind "them" directly? 
Isn't 
it pretty obvious by now who "they" are?  Broad denial, secrecy and 
breaking our own rules just sucks...

- Thomas

Timo Kreuzer wrote:
>   I'd have less problem to be patient, if I knew
> they cared, but they 
>  could as well be on vacation for a month.
>  And I don't like the idea of broken sysreg for a month.
>  It's the refusal to respond/provide information that is kinda annoying.
>  
>  Yeah, yeah, they are code-ninjas-whatever, hiding in the dark, silently 
>  sneaking into the code and stuff... but then they should stop breaking 
>  things or they might suddenly face a code-samurai, screaming and jumping 
>  at them ;)
>  
>  Dmitry Gorbachev wrote:
> >   Timo Kreuzer wrote:
> >    
> > >   It's still broken.
> > >
> > >  @ros-arm-bringup: Ignoring it doesn't make it go away! Fix please.
> > >       
> >  It can take some time, I guess. They maybe even cannot reproduce the
> >  bug on their machine. Please be patient...
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >     
>  
>  
>  ------------------------------------------------------------------------
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[KJK::Hyperion]

Thomas Bluemel wrote:
>   Why don't you just talk to the "people"
> behind "them" directly?  Isn't 
>  it pretty obvious by now who "they" are? 
who are they, Thomas? go ahead and tell us