I use screen all the time, including for keeping wiab running On Fri, Oct 1, 2010 at 1:50 PM, Joseph Gentle <[email protected]> wrote: > I'm happy to show you screen if you haven't used it before. (I love > that program.) > > -J > > > On Fri, Oct 1, 2010 at 1:37 PM, Alex North <[email protected]> wrote: >> Probably because I'm running it as a background task in a shell and it keeps >> stopping. I'll investigate using screen or something. >> >> >> On 1 October 2010 11:55, Joseph Gentle <[email protected]> wrote: >>> >>> ... Hmm.. the continuous build site (http://google2.osuosl.org:9090/) >>> doesn't seem to be loading for me. >>> >>> -J >>> >>> On Fri, Oct 1, 2010 at 11:28 AM, Alex North <[email protected]> wrote: >>> > I've set up a basic continuous build system on one of the machines >>> > (generously donated by Oregon State University) which hosts our example >>> > instances. >>> > >>> > https://sites.google.com/a/waveprotocol.org/wave-protocol/code/continuous-build >>> > The build currently tracks the libraries and default repositories and >>> > re-builds and tests whenever something changes. If something's not >>> > working >>> > for you this is a good place to check whether it might be just you or if >>> > things are known to be failing. For example, there are a couple of >>> > failing >>> > tests in the libraries project at the moment that we're looking into. >>> > We're >>> > experimenting with the set-up so please excuse any initial instability. >>> > I think it should probably be policy that no-one submits any changes >>> > while a >>> > build/test is failing* since this will further destabilize the build, >>> > make >>> > it harder to pin down the change introducing the failure, and mask new >>> > regressions introduced. Check the build before you "hg push". >>> > Cheers, >>> > Alex >>> > * With some exceptions. For example, the paste tests in libraries have >>> > never >>> > passed (but pass for us at Google in a slightly different environment). >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups >>> > "Wave Protocol" group. >>> > To post to this group, send email to [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> > http://groups.google.com/group/wave-protocol?hl=en. >>> > >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Wave Protocol" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/wave-protocol?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
