Thus said "Joe Mistachkin" on Thu, 03 Mar 2016 17:31:18 -0800:
> The way trunk works is probably not the best model.
I did not mean to imply that the way it works in trunk is the best
model, and in fact, I admitted as much in a previous email. Having to
take extra measures to avoid clut
Andy Bradford wrote:
>
> I think this will work, but I still wonder if it used to work this way
> before (e.g. test results ended up in current working directory, not
> elsewhere), why it should not continue to work that way? The reason why
> I suggested [pwd] is because that is how it cur
Thus said "Joe Mistachkin" on Thu, 03 Mar 2016 13:58:54 -0800:
> Slightly different solution checked-in. I'm not really a fan of
> relying on [pwd] in tests. Instead, we can just use the system
> temporary file location -OR- force the user to set FOSSIL_TEST_TEMP.
I think this will
Andy Bradford wrote:
>
> I think a safer default for tempPath is [pwd] and not where the
> tester.tcl is found. The following change permits the testing to resume
> for me:
>
Slightly different solution checked-in. I'm not really a fan of relying on
[pwd] in tests. Instead, we can j
Thus said "Joe Mistachkin" on Thu, 03 Mar 2016 10:53:41 -0800:
> My guess is that you had a pre-existing checkout recorded for that
> directory. Please "fossil all ignore" that checkout manually and then
> try again.
The problem appears to be that tempPath has gained new meaning...
Specific
Ross Berteig wrote:
I imagine that defining TEMP is the same issue Andy has.
Yeah, I was just looking into this on a Linux VM and found the same
thing. If TEMP isn't set, the tester script should probably check if
/tmp exists and just use that.
___
On 3/3/2016 11:34 AM, Andy Bradford wrote:
I'll see if I can track it down later if there is no more progress
elsewhere.
Try setting TEMP somewhere sane, perhaps:
$ export TEMP=/tmp
$ tclsh
That fixed it for me.
--
Ross Berteig r...@cheshireeng.
On 3/3/2016 10:53 AM, Joe Mistachkin wrote:
Ross Berteig wrote:
My Ubuntu VM saw this exact message. I was running tester.tcl in a
testing folder that is neither the build nor source tree.
My guess is that you had a pre-existing checkout recorded for that
directory. Please "fossil all ign
Thus said "Joe Mistachkin" on Thu, 03 Mar 2016 10:53:06 -0800:
> My guess is that you had a pre-existing checkout recorded for that
> directory. Please "fossil all ignore" on that checkout manually and
> then try again.
$ pwd
/tmp/test-fossil
$ fossil all ls -c | grep test-fossil
$ echo $?
Andy Bradford wrote:
>
> $ tclsh $SRC/test/tester.tcl $FOSSIL
> * amend **
> already within an open tree rooted at /tmp/fossil-test/
>
My guess is that you had a pre-existing checkout recorded for that
directory. Please "fossil all ignore" that checkout manually and
then try again.
--
Ross Berteig wrote:
>
> My Ubuntu VM saw this exact message. I was running tester.tcl in a
> testing folder that is neither the build nor source tree.
>
My guess is that you had a pre-existing checkout recorded for that
directory. Please "fossil all ignore" on that checkout manually
and then
On 3/3/2016 7:19 AM, Andy Bradford wrote:
$ tclsh $SRC/test/tester.tcl $FOSSIL
* amend **
already within an open tree rooted at /tmp/fossil-test/
while executing
My Ubuntu VM saw this exact message. I was running tester.tcl in a
testing folder that is neither the build nor so
Thus said "Joe Mistachkin" on Wed, 02 Mar 2016 10:47:39 -0800:
> Please review and/or run tests against the test suite changes on the
> "testerCleanup" branch.
I get the following when I try to run the same commands that I normally
do (which work fine on trunk):
$ echo $SRC
/tmp/fossil-test
$
On Thu, Mar 3, 2016 at 12:38 PM, Luca Ferrari wrote:
> Could it be repo.cksum off?
>
No - that one controls whether or not the so-called "R-card" is generated
and/or validated (the R-card is another level of integrity checking, but is
expensive to calculate, so it is optional).
--
- stepha
On Thu, Mar 3, 2016 at 12:11 PM, Stephan Beal wrote:
> Please update if at all possible. 1.33 is almost a year old, and the past 12
> months have seen lots of activity:
Yes, I'm updating.
> My currently hypotheses is that you perhaps had an editor session active,
> but unsaved, for one of the co
On Thu, Mar 3, 2016 at 8:17 AM, Luca Ferrari wrote:
> My fossil version is 1.33 [bd97cb7306].
> ANy other idea?
>
Please update if at all possible. 1.33 is almost a year old, and the past
12 months have seen lots of activity:
http://www.fossil-scm.org/index.html/reports?type=a&view=bymonth
My
16 matches
Mail list logo
