--- FAIL: filepath_test.TestEvalSymlinks (0.0 seconds)

[gopherbot]

by allard.guy.m:

What steps will reproduce the problem?
1. Attempt current build with symlinks already present higher in the subdirectory
hierarchy
2.
3.

What is the expected output?

A clean build and passing tests.

What do you see instead?

--- FAIL: filepath_test.TestEvalSymlinks (0.0 seconds)
    EvalSymlinks(/home/gmallard/hext/go/src/pkg/path/filepath/test)=/ad2/gma/home_ext/go/src/pkg/path/filepath/test, want /home/gmallard/hext/go/src/pkg/path/filepath/test
    EvalSymlinks(/home/gmallard/hext/go/src/pkg/path/filepath/test/dir)=/ad2/gma/home_ext/go/src/pkg/path/filepath/test/dir, want /home/gmallard/hext/go/src/pkg/path/filepath/test/dir
    EvalSymlinks(/home/gmallard/hext/go/src/pkg/path/filepath)=/ad2/gma/home_ext/go/src/pkg/path/filepath, want /home/gmallard/hext/go/src/pkg/path/filepath


Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

Ubuntu 10.4.2 LTS

Which revision are you using?  (hg identify)

f692a5e90f6f tip


Please provide any additional information below.

This failure occurs because in my setup there is a symbolic link further up in the
directory hierarchy.  In this particular case:

[gmallard@tjjackson ~]$ pwd
/home/gmallard
[gmallard@tjjackson ~]$ ls -ld hext
lrwxrwxrwx 1 gmallard gmallard 18 2011-01-16 20:50 hext -> /ad2/gma/home_ext/

I have:

GOROOT=/home/gmallard/hext/go

and I pull and build there.  But this is physically on the /ad2 device, not the device
where /home exists.

I can work around this by:
a) Changing GOROOT
b) Changing directories to the /ad2 device location

Only changing GOROOT is not sufficient, because then I get:

[gmallard@tjjackson src]$ ./all.bash 
Suspicious $GOROOT /ad2/gma/home_ext/go: does not match current directory.

[rsc]

Comment 1:

Owner changed to @adg.

Status changed to Accepted.

[adg]

Comment 2:

Status changed to Duplicate.

Merged into issue #1622.