Troy,
I like where this is going. Here are the immediate hurdles. I am
indeed just another ISP customer behind NAT layers. I've been
interested in setting up dynamic DNS, but have not yet done it. My
travel schedule for the week changed today, which will prevent me from
working on the debian
Thanks everyone who replied. There was a lot of email on this thread,
so I'm going to write a quick summary.
There are concerns that this would increase the support load on
organizational helpdesks that support AFS internally, and on the
OpenAFS community overall.
There are concerns that
How about an effort to get nightly builds of master available on as many
platforms as possible, and getting thousands of bored college students to
download, install, and test them?
I think that's still overly optimistic. There's a lot of moving parts here; you
just can't just install a
I'm looking to get all the low-hanging fruit with unskilled testing.
Particularly with regressions like this:
hozer@six:~/src/openafs-fuse-git/tests/fuse$
/home/hozer/src/openafs-fuse-git/tests/fuse/../../src/afsd/afsd.fuse -dynroot
-fakestat -d -confdir
On Mon, Sep 17, 2012 at 1:15 PM, Troy Benjegerdes ho...@hozed.org wrote:
I'm looking to get all the low-hanging fruit with unskilled testing.
Particularly with regressions like this:
hozer@six:~/src/openafs-fuse-git/tests/fuse$
Troy Benjegerdes ho...@hozed.org writes:
I'm looking to get all the low-hanging fruit with unskilled testing.
Particularly with regressions like this:
hozer@six:~/src/openafs-fuse-git/tests/fuse$
/home/hozer/src/openafs-fuse-git/tests/fuse/../../src/afsd/afsd.fuse -dynroot
-fakestat -d
On Mon, Sep 17, 2012 at 2:28 PM, Russ Allbery r...@stanford.edu wrote:
Troy Benjegerdes ho...@hozed.org writes:
I'm looking to get all the low-hanging fruit with unskilled testing.
Particularly with regressions like this:
hozer@six:~/src/openafs-fuse-git/tests/fuse$
Hi,
Well, we used the fuse rather extensively for locking and dirformat testing.
It's experimental, but science experiment might be a little strong.
Matt
- Russ Allbery r...@stanford.edu wrote:
Troy Benjegerdes ho...@hozed.org writes:
I'm looking to get all the low-hanging fruit
FUSE library version: 2.8.6
nullpath_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.17
flags=0x047b
max_readahead=0x0002
Starting AFS cache scan...found 0 non-empty cache files (0%).
afsd: All AFS daemons started.
Segmentation fault
The fuse code
On Mon, Sep 17, 2012 at 2:54 PM, Troy Benjegerdes ho...@hozed.org wrote:
FUSE library version: 2.8.6
nullpath_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.17
flags=0x047b
max_readahead=0x0002
Starting AFS cache scan...found 0 non-empty cache files (0%).
On 17 Sep 2012, at 19:54, Troy Benjegerdes wrote:
If 'rebuild with debug' symbols is the answer to find the segfault, then why
don't we change './regen ./configure make check' to turn on debug
symbols
by default (at least in master.. we can turn it back off in a release)
If you are
On 17 Sep 2012, at 17:25, David Boyes wrote:
'make check' on a single machine will never give you useful testing results
other than to find packaging or smoke test errors, which aren't all that
helpful overall.
I agree with you with regards to crowd sourced testing, but I just wanted to
Derrick Brashear sha...@gmail.com writes:
On Mon, Sep 17, 2012 at 2:28 PM, Russ Allbery r...@stanford.edu wrote:
The fuse code currently in the tree was primarily a science experiment
by one developer and is not something that's really ready for
production use. That's not to say this isn't a
Matt W. Benjamin m...@linuxbox.com writes:
Well, we used the fuse rather extensively for locking and dirformat
testing. It's experimental, but science experiment might be a little
strong.
Ah, okay, it's gotten more attention than I thought.
--
Russ Allbery (r...@stanford.edu)
-Original Message-
From: Simon Wilkinson [mailto:s...@your-file-system.com]
On 17 Sep 2012, at 17:25, David Boyes wrote:
'make check' on a single machine will never give you useful testing
results other than to find packaging or smoke test errors, which aren't all
that helpful
On 9/17/2012 5:41 PM, Andrew Deason wrote:
Isn't this what we already have? If you have a source tree that's not
exactly the commit for e.g. openafs-stable-1_6_1, you get a string
saying how many commits you are from a known point, and a git hash. So,
we should be able to identify exactly
On Mon, September 17, 2012 5:50 pm, Jeffrey Altman wrote:
On 9/17/2012 5:41 PM, Andrew Deason wrote:
Isn't this what we already have? If you have a source tree that's not
exactly the commit for e.g. openafs-stable-1_6_1, you get a string
saying how many commits you are from a known point,
On Mon, Sep 17, 2012 at 3:41 PM, Andrew Deason adea...@sinenomine.net wrote:
On Mon, 17 Sep 2012 10:25:38 -0600
Ken Dreyer ktdre...@ktdreyer.com wrote:
I think a good next step would be to decide how we should handle
version numbers in snapshot packages. For example: should configure.ac
in
On Mon, September 17, 2012 5:50 pm, Jeffrey Altman wrote:
The challenge is how should version numbers be generated so that
tonight's build will upgrade yesterday's build while not interfering
with the stable release numbering.
Ah, okay, I wasn't thinking of this as like an unstable channel
more than a certain number of version
segments, or something?
For Debian, the best solution is generally for some snapshot taken on
20120917 of source from the 1.6 branch after 1.6.1 to be versioned as
1.6.1+20120917. This sorts after 1.6.1 but before 1.6.1.1.
You can use - instead of + provided
On Mon, 17 Sep 2012 17:10:35 -0500
Ken Dreyer ktdre...@ktdreyer.com wrote:
Isn't this what we already have? If you have a source tree that's
not exactly the commit for e.g. openafs-stable-1_6_1, you get a
string saying how many commits you are from a known point, and a git
hash. So, we
Andrew Deason adea...@sinenomine.net writes:
I don't think you can make that say something based on 1.6.1, since the
head of the 1.6.x branch right now is a different branch than 1.6.1. I
mean, if git-version said something like this is 1.6.1 plus N patches,
that would be incorrect. Since,
On 17 Sep 2012, at 23:18, Andrew Deason wrote:
I don't think you can make that say something based on 1.6.1, since the
head of the 1.6.x branch right now is a different branch than 1.6.1. I
mean, if git-version said something like this is 1.6.1 plus N patches,
that would be incorrect.
Simon Wilkinson s...@your-file-system.com writes:
We're not consistent about whether we release from trunk, or release
from a branch. This means that on some occasions the trunk has the tag,
and on others the branch. In a traditional git world, we would have
branched for 1.6.1, committed the
On Mon, Sep 17, 2012 at 6:12 PM, Andrew Deason adea...@sinenomine.net wrote:
On Mon, September 17, 2012 5:50 pm, Jeffrey Altman wrote:
The challenge is how should version numbers be generated so that
tonight's build will upgrade yesterday's build while not interfering
with the stable
So. Were you perchance using it on a Mac? Probably a 64 bit Intel mac?
http://gerrit.openafs.org/#change,8132
As nearly as I can tell, this is a very specific problem. The code is fine. The
circumstances of building afsd.fuse meant it was collateral damage when we
started using roken, but only
Nope, Debian x86-64
Any chance the buildbots can be easily modified to run make check/make tests?
I'm really curious what debian ppc32/ppc64 will do. I have an arm build, but
no fuse kernel module (debian on an sdcard on an android tablet).
On Mon, Sep 17, 2012 at 11:39:55PM -0400, Derrick
the tests are not ready to be run on the buildslaves. it's been
working toward that point, but not yet.
On Tue, Sep 18, 2012 at 12:08 AM, Troy Benjegerdes ho...@hozed.org wrote:
Nope, Debian x86-64
Any chance the buildbots can be easily modified to run make check/make tests?
I'm really
And I don't think OS X can handle more than a certain number of version
segments, or something?
OSX is special, but, we already have the problem and define something
special there.
What we'd need to do is define everything as an dev version of
whatever, but then the problem is
you can
29 matches
Mail list logo
