• Brad Roberts via Digitalmars-d (12/12) May 24 2014 As discussed a little at the conference, the auto-tester is almost alway...
• monarch_dodra (9/25) May 25 2014 Would there be any way to be able to set-up and configure the
• Brad Roberts via Digitalmars-d (8/30) May 25 2014 Don't worry about the fairness to me. I actually want remote access so ...
• Jerry (5/24) May 27 2014 I'd be willing to run some autotesting in my house. Granting remote
• Brad Roberts via Digitalmars-d (4/28) May 27 2014 All of it's 'steady state' operations are pull, or rather driven from th...
• Walter Bright (2/4) May 27 2014 That's why god made garages :-)

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

As discussed a little at the conference, the auto-tester is almost always
hardware bound.  In other 
words, it's building flat out 24/7.  More hardware == faster updates to build
status.  If anyone 
wants to provide hardware to help there's a number of ways to do so.  Here's my
order of preference:

1) you have a machine you host somewhere and can provide me remote access to.
     - this could be a bare metal host or a vm
2) you have a machine that you're willing to send to me
3) you're willing to fund equipment purchase or vm rental

At this point, I'd MUCH rather have hardware that doesn't live in my house. 
I've got too many 
already.  But I also don't want to turn down good equipment.  So, please reach
out to me privately 
if you'd like to help out: braddr puremagic.com

Thanks,
Brad

"monarch_dodra" <monarchdodra gmail.com> writes:

On Saturday, 24 May 2014 at 17:58:08 UTC, Brad Roberts via 
Digitalmars-d wrote:
 As discussed a little at the conference, the auto-tester is 
 almost always hardware bound.  In other words, it's building 
 flat out 24/7.  More hardware == faster updates to build 
 status.  If anyone wants to provide hardware to help there's a 
 number of ways to do so.  Here's my order of preference:

 1) you have a machine you host somewhere and can provide me 
 remote access to.
     - this could be a bare metal host or a vm
 2) you have a machine that you're willing to send to me
 3) you're willing to fund equipment purchase or vm rental

 At this point, I'd MUCH rather have hardware that doesn't live 
 in my house.  I've got too many already.  But I also don't want 
 to turn down good equipment.  So, please reach out to me 
 privately if you'd like to help out: braddr puremagic.com

 Thanks,
 Brad

Would there be any way to be able to set-up and configure the 
machines on our end, and to "register" them into the auto-testers 
once they are ready to go?

It feels unfair that even if the machine is in my home, that it's 
still you who has to maintain it. In particular, I imagine you'd 
be powerless to do much of anything when you can't remote into 
the machine...

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

On 5/25/14, 7:54 AM, monarch_dodra via Digitalmars-d wrote:
 On Saturday, 24 May 2014 at 17:58:08 UTC, Brad Roberts via Digitalmars-d wrote:
 As discussed a little at the conference, the auto-tester is almost always
hardware bound.  In
 other words, it's building flat out 24/7.  More hardware == faster updates to
build status.  If
 anyone wants to provide hardware to help there's a number of ways to do so. 
Here's my order of
 preference:

 1) you have a machine you host somewhere and can provide me remote access to.
     - this could be a bare metal host or a vm
 2) you have a machine that you're willing to send to me
 3) you're willing to fund equipment purchase or vm rental

 At this point, I'd MUCH rather have hardware that doesn't live in my house. 
I've got too many
 already.  But I also don't want to turn down good equipment.  So, please reach
out to me privately
 if you'd like to help out: braddr puremagic.com

 Thanks,
 Brad

 Would there be any way to be able to set-up and configure the machines on our
end, and to "register"
 them into the auto-testers once they are ready to go?

 It feels unfair that even if the machine is in my home, that it's still you
who has to maintain it.
 In particular, I imagine you'd be powerless to do much of anything when you
can't remote into the
 machine...

Don't worry about the fairness to me.  I actually want remote access so that I
can fix things when 
they need to be fixed, at least within the realm of the tester breaking.  In
terms of the host (be 
it a vm or the physical machine) breaking, I'd certainly turn that over to the
owner to deal with. 
Regardless, it's a pretty rare event that I need to login, but when I do I want
to be able to do it 
right then and not need to wait for some back and forthing over email or
whatever.

Later,
Brad

Jerry <jlquinn optonline.net> writes:

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

 On 5/25/14, 7:54 AM, monarch_dodra via Digitalmars-d wrote:
 On Saturday, 24 May 2014 at 17:58:08 UTC, Brad Roberts via Digitalmars-d wrote:
 As discussed a little at the conference, the auto-tester is almost always
hardware bound.  In
 other words, it's building flat out 24/7.  More hardware == faster updates to
build status.  If
 anyone wants to provide hardware to help there's a number of ways to do so. 
Here's my order of
 preference:

 1) you have a machine you host somewhere and can provide me remote access to.
     - this could be a bare metal host or a vm

 At this point, I'd MUCH rather have hardware that doesn't live in my house. 
I've got too many
 already.  But I also don't want to turn down good equipment.  So, please reach
out to me privately
 if you'd like to help out: braddr puremagic.com

 Thanks,
 Brad

 Would there be any way to be able to set-up and configure the machines on our
end, and to "register"
 them into the auto-testers once they are ready to go?


I'd be willing to run some autotesting in my house.  Granting remote
access, not so much :-)

How hard would it be to turn the autotester client into such a pull system?

Jerry

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

On 5/27/14, 1:41 PM, Jerry via Digitalmars-d wrote:
 Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

 On 5/25/14, 7:54 AM, monarch_dodra via Digitalmars-d wrote:
 On Saturday, 24 May 2014 at 17:58:08 UTC, Brad Roberts via Digitalmars-d wrote:
 As discussed a little at the conference, the auto-tester is almost always
hardware bound.  In
 other words, it's building flat out 24/7.  More hardware == faster updates to
build status.  If
 anyone wants to provide hardware to help there's a number of ways to do so. 
Here's my order of
 preference:

 1) you have a machine you host somewhere and can provide me remote access to.
      - this could be a bare metal host or a vm

 At this point, I'd MUCH rather have hardware that doesn't live in my house. 
I've got too many
 already.  But I also don't want to turn down good equipment.  So, please reach
out to me privately
 if you'd like to help out: braddr puremagic.com

 Thanks,
 Brad

 Would there be any way to be able to set-up and configure the machines on our
end, and to "register"
 them into the auto-testers once they are ready to go?


 I'd be willing to run some autotesting in my house.  Granting remote
 access, not so much :-)

 How hard would it be to turn the autotester client into such a pull system?

 Jerry

All of it's 'steady state' operations are pull, or rather driven from the
client (pull tasks to 
perform, push results).  It's maintenance and debugging that's interactive. 
That's the part I'm 
reluctant to loose.

Walter Bright <newshound2 digitalmars.com> writes:

On 5/24/2014 10:57 AM, Brad Roberts via Digitalmars-d wrote:
 At this point, I'd MUCH rather have hardware that doesn't live in my house.
 I've got too many already.

That's why god made garages :-)