On Tue, 10 Dec 2013, Nicolas Vigier wrote:
In order to help me doing that, I'm very interested to receive from
developers of any tor components :
- a description or ticket number of bugs that you wish could have been
detected earlier with automated tests
Nicolas Vigier:
In addition to this, an other thing that we could do automatically is
rebasing the tor-browser patches onto the unreleased next mozilla esr
from http://hg.mozilla.org/releases/mozilla-esr24/ in the default branch.
This allows to see in advance if rebasing the patches on the
On Mon, 09 Dec 2013, Georg Koppen wrote:
Hi Nicolas,
some remarks are below.
Hi Georg,
Thanks for your remarks.
Nicolas Vigier:
In order to help me doing that, I'm very interested to receive from
developers of any tor components :
- a description or ticket number of bugs that
Nicolas Vigier:
Ok, we can have a test rebuilding several times the files that are most
likely to become non deterministic. However it would be better if we can
find some way to trigger those non-deterministic builds with only two
builds. Maybe we can try something like this :
- a library
Hi Nicolas,
some remarks are below.
Nicolas Vigier:
In order to help me doing that, I'm very interested to receive from
developers of any tor components :
- a description or ticket number of bugs that you wish could have been
detected earlier with automated tests
Hello,
If you don't know me yet, I am the new person working on automation :
https://www.torproject.org/about/jobs-lead-automation.html.en
To get started working on tor automation, I am currently looking at all
components that are part of tor project, to find what is the current
status regarding
