Hmm, is the try server master overdue for a reload/restart? The
master.cfg is right, but it's still checking out chrome-deps.

On Tue, Dec 15, 2009 at 4:40 PM, Lei Zhang <thes...@chromium.org> wrote:
> Ok, I think I fixed it. Running a test job right now. *fingers crossed*
>
> http://build.chromium.org/buildbot/try-server/builders/linux_view/builds/1474
>
> On Tue, Dec 15, 2009 at 4:29 PM, Scott Violet <s...@chromium.org> wrote:
>> They need:
>>
>>  { "name" : "cros deps",
>>    "url" : "svn://chrome-svn/chrome/trunk/cros_deps",
>>  },
>>
>> in .gclient, but there may be syncing problems unless you have git > 1.6.1 .
>>
>> "cros deps" is the new way dependency are managed between the two projects.
>>
>>  -Scott
>>
>> On Tue, Dec 15, 2009 at 4:26 PM, Lei Zhang <thes...@chromium.org> wrote:
>>> The 3 linux_views bots currently have Git 1.5.
>>>
>>> Can someone answer my question regarding chrome-deps vs cros_deps? I
>>> don't think chrome-deps/DEPS is correct. It has:
>>>
>>> deps = {
>>> # Cros library that's dynamically linked to by Chrome
>>>  "src/third_party/cros" :
>>>    "/trunk/src/platform/c...@146",
>>> # Source for the chrome os login manager to be built along with the
>>> # chrome os build of chrome
>>>  "src/third_party/chromeos_login_manager" :
>>>    "/trunk/src/platform/login_manager/chromeos_login_mana...@48",
>>> # dependency for login manager in chrome os
>>>  "src/third_party/chromeos_login_manager/include" :
>>>    "/trunk/src/third_party/pam-...@30",
>>> }
>>>
>>> but /trunk/src/platform/login_manager/chromeos_login_manager doesn't
>>> seem to exist?
>>>
>>> On the linux_views valgrind bot, I see it has cros_deps/DEPS instead, which 
>>> has:
>>>
>>> deps = {
>>>  "src/third_party/cros":
>>>    Var("chromium_git") + "/cros....@767ada11",
>>>  "src/third_party/chromeos_login_manager":
>>>    Var("chromium_git") + "/login_manager....@c51b4b0a",
>>> }
>>>
>>> On Tue, Dec 15, 2009 at 4:15 PM, Scott Violet <s...@google.com> wrote:
>>>> There's been some recent Chrome OS changes that have caused a world of
>>>> hurt on the try servers/build infrastructure. I believe we need to
>>>> update the try bots to > git 1.6.1. Marc-Antoine has done a slew of
>>>> changes, and I believe the last step is updating the install build
>>>> script to take care of installing/updating git. Dave Moore, Chris
>>>> Masone and myself spoke about this about an hour ago and I believe one
>>>> of them is actively looking into this now.
>>>>
>>>>  -Scott
>>>>
>>>> On Tue, Dec 15, 2009 at 3:37 PM, Lei Zhang <thes...@chromium.org> wrote:
>>>>> It has a custom .gclient entry for chrome-deps, should that be cros_deps?
>>>>>
>>>>> On Tue, Dec 15, 2009 at 3:24 PM, James Robinson <jam...@chromium.org> 
>>>>> wrote:
>>>>>> Every patch sent to the linux_view trybot lately dies with this error
>>>>>> in the 'gclient' step:
>>>>>>
>>>>>> Exception: 
>>>>>> /b/slave/linux_view/build/src/third_party/chromeos_login_manager/chromeos_login_manager/chromeos_login_manager.gyp
>>>>>> not found (cwd: /b/slave/linux_view/build) while loading dependencies
>>>>>> of /b/slave/linux_view/build/src/chrome/chrome.gyp while loading
>>>>>> dependencies of /b/slave/linux_view/build/src/build/all.gyp while
>>>>>> trying to load src/build/all.gyp
>>>>>> failed to run command: /usr/bin/python src/build/gyp_chromium
>>>>>>
>>>>>> It seems like this bot is pretty much 100% useless right now.  Is
>>>>>> someone looking into it?
>>>>>>
>>>>>> - James
>>>>>>
>>>>>> --
>>>>>> Chromium Developers mailing list: chromium-dev@googlegroups.com
>>>>>> View archives, change email options, or unsubscribe:
>>>>>>    http://groups.google.com/group/chromium-dev
>>>>>>
>>>>>
>>>>> --
>>>>> Chromium Developers mailing list: chromium-dev@googlegroups.com
>>>>> View archives, change email options, or unsubscribe:
>>>>>    http://groups.google.com/group/chromium-dev
>>>>>
>>>>
>>>
>>
>

-- 
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev

Reply via email to