-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b11
-
other
-
other
-
Verified
To reproduce:
1) Setup a master for dolhin
2) bringover from this new dolphin master (using gnumake bringover) and all the workspaces under there bringover from the correct new master except for the sponsors workspace, it still brings over from the old mustang master.
This prevents the full automation of the RE bringover process.
See log:
Parent workspace: /net/mizu.sfbay/n/dolphin/jdk7/DOLMASTER/control
Child workspace: /net/mizu.sfbay/n/dolphin/jdk7/ws/control
Examined files: 33
Bringing over contents changes: 33
Examined files: 33
Contents Summary:
33 create
Parent workspace: /net/mizu.sfbay/n/dolphin/jdk7/DOLMASTER/hotspot
Child workspace: /net/mizu.sfbay/n/dolphin/jdk7/ws/hotspot
.
.
.
.
.
Parent workspace: /net/jdk.sfbay/export/disk7/jdk1.6.0/sponsors
Child workspace: /net/mizu.sfbay/n/dolphin/jdk7/ws/sponsors
1) Setup a master for dolhin
2) bringover from this new dolphin master (using gnumake bringover) and all the workspaces under there bringover from the correct new master except for the sponsors workspace, it still brings over from the old mustang master.
This prevents the full automation of the RE bringover process.
See log:
Parent workspace: /net/mizu.sfbay/n/dolphin/jdk7/DOLMASTER/control
Child workspace: /net/mizu.sfbay/n/dolphin/jdk7/ws/control
Examined files: 33
Bringing over contents changes: 33
Examined files: 33
Contents Summary:
33 create
Parent workspace: /net/mizu.sfbay/n/dolphin/jdk7/DOLMASTER/hotspot
Child workspace: /net/mizu.sfbay/n/dolphin/jdk7/ws/hotspot
.
.
.
.
.
Parent workspace: /net/jdk.sfbay/export/disk7/jdk1.6.0/sponsors
Child workspace: /net/mizu.sfbay/n/dolphin/jdk7/ws/sponsors