Call for help on testing core tor releases
Hello Tor community! The Core Tor Team would like to improve our release process by getting it more tested so bugs are found earlier, so stable releases can get out faster and without any big bugs. During Tor's Meeting in Seattle a couple of weeks ago, we discussed this topic and decided to organize a QA team (with the help of the community) for core tor. So we decided to make a call for volunteers to help us with testing our 0.2.9 release so we can catch bugs asap. We are planning on freezing our alpha release this Monday, October 17th, the test period is from 17-31 of October. [release calendar: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam#Releases ] But if you can test it on the week of the 17, please do so because the sooner the better for us to be able to fix the bugs. Also, please understand that giving so many things we have on our plates, we will have to triage and prioritize bugs reported. This means some might be defer to another release. Below you can read more about what we are asking from you ;) and what our goals are. If you think you can help us, please reply to this email letting us know. What we are asking volunteers: * Validate release signature/checksum * Does it build with _no_ Warnings? * Does "make test" pass? * Does "make test-network-all" pass? (you'll need chutney for this - chutney does not work on Windows) * Does it work as a client? As a relay? As a hidden service ? * Does it work if you drop the binary into (eg) torpbrowser? We are hoping to find enough people that we can test the releases on as many OS's as possible. Some OS-specific notes: * on Linux and BSD, Tor requires some dependencies (read INSTALL). * on OS X, you'll need to choose a package manager (HomeBrew, MacPorts, Fink), or install dependencies from source, * either way, you will need to tell configure where the dependencies are located. * on Windows, people sometimes have trouble building Tor. Help us update our build instructions for Windows! Our goals: * We hope to have tor alpha releases tested within a week of it going out * We hope to have people testing it on as many OS's as possible * Reduce the number of bugs found when we launch a release candidate and/or stable release * We want operating systems and configurations other than the ones we use in development to get tested BEFORE we declare the release stable. If you read so far, like the idea but, this is just bad timing for you to join us and help out with the project. No problem! luckily we will have more core tor releases in the future :) so that means there will always be an opportunity to help. We will keep this list updated as we move forward with this project so hopefully you can join us latter! Please let us know if you have any questions about this - and thank you in advance. Cheers, Isabela / on behalf of core tor ps: email from Nick on 0.2.9 freeze dates if you miss it https://lists.torproject.org/pipermail/tor-dev/2016-October/011513.html
Isabela / Core Tor I'd love to help. I use 99% Linux and will be able help with everything you listed. I'm pastly on trac and oftc. Matt isabela@riseup.net:
What we are asking volunteers:
* Validate release signature/checksum
* Does it build with _no_ Warnings?
* Does "make test" pass?
* Does "make test-network-all" pass? (you'll need chutney for this - chutney does not work on Windows)
* Does it work as a client? As a relay? As a hidden service ?
* Does it work if you drop the binary into (eg) torpbrowser?
We are hoping to find enough people that we can test the releases on as many OS's as possible. Some OS-specific notes:
* on Linux and BSD, Tor requires some dependencies (read INSTALL).
* on OS X, you'll need to choose a package manager (HomeBrew, MacPorts, Fink), or install dependencies from source,
* either way, you will need to tell configure where the dependencies are located.
* on Windows, people sometimes have trouble building Tor. Help us update our build instructions for Windows!
Our goals:
* We hope to have tor alpha releases tested within a week of it going out
* We hope to have people testing it on as many OS's as possible
* Reduce the number of bugs found when we launch a release candidate and/or stable release
* We want operating systems and configurations other than the ones we use in development to get tested BEFORE we declare the release stable.
I would love to help, but can you also volunteer when cannot give ALL the feedback? On Oct 13, 2016 10:53 PM, "Matt Traudt" <sirmatt@ksu.edu> wrote:
Isabela / Core Tor
I'd love to help. I use 99% Linux and will be able help with everything you listed.
I'm pastly on trac and oftc.
Matt
isabela@riseup.net:
What we are asking volunteers:
* Validate release signature/checksum
* Does it build with _no_ Warnings?
* Does "make test" pass?
* Does "make test-network-all" pass? (you'll need chutney for this - chutney does not work on Windows)
* Does it work as a client? As a relay? As a hidden service ?
* Does it work if you drop the binary into (eg) torpbrowser?
We are hoping to find enough people that we can test the releases on as many OS's as possible. Some OS-specific notes:
* on Linux and BSD, Tor requires some dependencies (read INSTALL).
* on OS X, you'll need to choose a package manager (HomeBrew, MacPorts, Fink), or install dependencies from source,
* either way, you will need to tell configure where the dependencies are located.
* on Windows, people sometimes have trouble building Tor. Help us update our build instructions for Windows!
Our goals:
* We hope to have tor alpha releases tested within a week of it going
out
* We hope to have people testing it on as many OS's as possible
* Reduce the number of bugs found when we launch a release candidate and/or stable release
* We want operating systems and configurations other than the ones we use in development to get tested BEFORE we declare the release stable.
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On 14 Oct 2016, at 08:03, blacklight . <pandakaasftw@gmail.com> wrote:
I would love to help, but can you also volunteer when cannot give ALL the feedback?
On 14 Oct 2016, at 11:30, ng0 <ng0@we.make.ritual.n0.is> wrote:
Do all these task have to apply to make the test valid/useful for you? On one of my test systems - I contribute to Guix - there is no chance of a (system-specific, unofficial) torbrowser build so far (but I/we keep looking into this). So long story short, I can run tests on some amd64_x86 based gnu-systems, but on one of them I need to exclude torbrowser.
We only do source releases for tor alphas and release candidates. (Except for Debian, which has experimental alphas built nightly.) So you must build tor from source in order to run the tests. All the other tests are optional, but the more you can do, the better! If you can't build tor from source, you can still help by giving us feedback on the Tor Browser alpha series, or the Tor Expert Bundles on Windows. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
teor <teor2345@gmail.com> writes:
[ Unknown signature status ]
On 14 Oct 2016, at 08:03, blacklight . <pandakaasftw@gmail.com> wrote:
I would love to help, but can you also volunteer when cannot give ALL the feedback?
On 14 Oct 2016, at 11:30, ng0 <ng0@we.make.ritual.n0.is> wrote:
Do all these task have to apply to make the test valid/useful for you? On one of my test systems - I contribute to Guix - there is no chance of a (system-specific, unofficial) torbrowser build so far (but I/we keep looking into this). So long story short, I can run tests on some amd64_x86 based gnu-systems, but on one of them I need to exclude torbrowser.
We only do source releases for tor alphas and release candidates. (Except for Debian, which has experimental alphas built nightly.)
So you must build tor from source in order to run the tests.
This is doable, I can even hack together a rough guix.scm for tor source like I did for gnunet in svn r38071. The other build systems will be Gentoo.
All the other tests are optional, but the more you can do, the better!
If you can't build tor from source, you can still help by giving us feedback on the Tor Browser alpha series, or the Tor Expert Bundles on Windows.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
Thanks, ng0
2016-10-13 22:48 GMT-03:00, teor <teor2345@gmail.com>:
On 14 Oct 2016, at 08:03, blacklight . <pandakaasftw@gmail.com> wrote:
I would love to help, but can you also volunteer when cannot give ALL the feedback?
On 14 Oct 2016, at 11:30, ng0 <ng0@we.make.ritual.n0.is> wrote:
Do all these task have to apply to make the test valid/useful for you? On one of my test systems - I contribute to Guix - there is no chance of a (system-specific, unofficial) torbrowser build so far (but I/we keep looking into this). So long story short, I can run tests on some amd64_x86 based gnu-systems, but on one of them I need to exclude torbrowser.
We only do source releases for tor alphas and release candidates. (Except for Debian, which has experimental alphas built nightly.)
So you must build tor from source in order to run the tests.
All the other tests are optional, but the more you can do, the better!
If you can't build tor from source, you can still help by giving us feedback on the Tor Browser alpha series, or the Tor Expert Bundles on Windows.
T
-- Tim Wilson-Brown (teor)
quick and dirty feedback; 6 relays running well 0.3.0.0-alpha-dev (>=git-d1bcba19a9790a37) for quite a while (3 in dual stack). 4freebsd and 2netbsd machines. 5static binary, 1shared (freebsd 10.3-R-p7, i386). every single relay that now is running -dev was running 0.2.9.4-alpha since its release date (or one/two days after it was available on your distfiles/archives ftp). I was following the releases available on the ftp, not ports/pkg/pkgsrc/pkgin/... *EXCEPT* for one machine that runs freebsd10.3r-p7 (i386); it was working good with 0.2.9.2-alpha only (again, with shared libs). sorry for not providing proper feedback or patch on Tor's trac. I plan to do that ASAP. PS: http://lists.nycbug.org/pipermail/tor-bsd/2016-October/000467.html might be interesting for those running Tor (security/tor-devel) with FreeBSD. ty. -- Vinícius Zavam keybase.io/egypcio/key.asc
isabela@riseup.net writes:
Hello Tor community!
The Core Tor Team would like to improve our release process by getting it more tested so bugs are found earlier, so stable releases can get out faster and without any big bugs.
During Tor's Meeting in Seattle a couple of weeks ago, we discussed this topic and decided to organize a QA team (with the help of the community) for core tor.
So we decided to make a call for volunteers to help us with testing our 0.2.9 release so we can catch bugs asap. We are planning on freezing our alpha release this Monday, October 17th, the test period is from 17-31 of October. [release calendar: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam#Releases ]
What we are asking volunteers:
* Validate release signature/checksum
* Does it build with _no_ Warnings?
* Does "make test" pass?
* Does "make test-network-all" pass? (you'll need chutney for this - chutney does not work on Windows)
* Does it work as a client? As a relay? As a hidden service ?
* Does it work if you drop the binary into (eg) torpbrowser?
Do all these task have to apply to make the test valid/useful for you? On one of my test systems - I contribute to Guix - there is no chance of a (system-specific, unofficial) torbrowser build so far (but I/we keep looking into this). So long story short, I can run tests on some amd64_x86 based gnu-systems, but on one of them I need to exclude torbrowser.
Please let us know if you have any questions about this - and thank you in advance.
Cheers,
Isabela / on behalf of core tor
ps: email from Nick on 0.2.9 freeze dates if you miss it https://lists.torproject.org/pipermail/tor-dev/2016-October/011513.html
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-- ng0
Hi there! First, thanks again for offering to help test our 0.2.9.4-alpha release! This release came out actually last week but I was mostly offline and could not send this note to you / sorry about that. I organized the information related to what to test and how to report bugs here: https://pad.riseup.net/p/V5ysw5cWFIbz A new thing you will find there is a link to download a nightly build of Tor Browser with Tor 0.2.9.4-alpha -- this is actually the easiest way to test it if you only have a few minutes. There are some instructions on how to submit a bug to us as well. This is the first time we are doing this (call for help testing) sorry for the bumps along the way We will continue to ask for help and hopefully get better over time. If you have some time this week, please do test our alpha release, this will help us a lot! Thanks again for the help o/ Isabela
Isabela, Great idea, count me in. Most interested in testing Ubuntu Trusty, but Debian stable and testing also relevant to my interests. Regarding the Riseup Pad, could you toss in some links for reading up on Chutney? I'd like to reuse this Pad to as a catch-all resource for bootstrapping Tor tests. Conor On 10/25/2016 09:10 AM, isabela@riseup.net wrote:
Hi there!
First, thanks again for offering to help test our 0.2.9.4-alpha release!
This release came out actually last week but I was mostly offline and could not send this note to you / sorry about that.
I organized the information related to what to test and how to report bugs here:
https://pad.riseup.net/p/V5ysw5cWFIbz
A new thing you will find there is a link to download a nightly build of Tor Browser with Tor 0.2.9.4-alpha -- this is actually the easiest way to test it if you only have a few minutes.
There are some instructions on how to submit a bug to us as well.
This is the first time we are doing this (call for help testing) sorry for the bumps along the way We will continue to ask for help and hopefully get better over time.
If you have some time this week, please do test our alpha release, this will help us a lot!
Thanks again for the help o/
Isabela
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On 10/25/16 5:03 PM, Conor Schaefer wrote:
Isabela,
Great idea, count me in. Most interested in testing Ubuntu Trusty, but Debian stable and testing also relevant to my interests.
Regarding the Riseup Pad, could you toss in some links for reading up on Chutney? I'd like to reuse this Pad to as a catch-all resource for bootstrapping Tor tests.
Conor
Thanks for the help! I added a link with some good tips on how to get started with Chutney o/
On Thu, Oct 13, 2016 at 02:29:19PM -0400, isabela@riseup.net wrote:
Hello Tor community!
The Core Tor Team would like to improve our release process by getting it more tested so bugs are found earlier, so stable releases can get out faster and without any big bugs.
During Tor's Meeting in Seattle a couple of weeks ago, we discussed this topic and decided to organize a QA team (with the help of the community) for core tor.
There are some people on the tor-qa who test Tor Browser before release; maybe some of them will help? Or maybe you want to do core tor QA on this list? https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
participants (8)
-
blacklight . -
Conor Schaefer -
David Fifield -
isabela＠riseup.net -
Matt Traudt -
ng0 -
teor -
Vinícius Zavam