721779 - Win debug builds failing in purge_builds.py: "NameError: global name 'any' is not defined"

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Matt Brubeck (:mbrubeck)]

Starting with this push, all Win and WinXP debug builds are failing:
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=108db1fb5501

========= Started set props: purge_target (results: 2, elapsed: 10 secs) ==========
'python' 'tools/buildfarm/maintenance/purge_builds.py' '-s' '1.0' '-n' 'info' '-n' 'rel-*' '..' '/scratchbox/users/cltbld/home/cltbld/build'
 in dir c:\talos-slave\test\. (timeout 3600 secs)
 watching logfiles {}
 argv: ['python', 'tools/buildfarm/maintenance/purge_builds.py', '-s', '1.0', '-n', 'info', '-n', 'rel-*', '..', '/scratchbox/users/cltbld/home/cltbld/build']
 environment:
  ALLUSERSPROFILE=C:\ProgramData
  APPDATA=C:\Users\cltbld\AppData\Roaming
  COMMONPROGRAMFILES=C:\Program Files\Common Files
  COMPUTERNAME=TALOS-R3-W7-058
  COMSPEC=C:\Windows\system32\cmd.exe
  CVS_RSH=ssh
  DevEnvDir=D:\msvs8\Common7\IDE
  FP_NO_HOST_CHECK=NO
  FrameworkDir=C:\WINDOWS\Microsoft.NET\Framework
  FrameworkSDKDir=D:\msvs8\SDK\v2.0
  FrameworkVersion=v2.0.50727
  HOMEDRIVE=C:
  HOMEPATH=\Users\cltbld
  LIBPATH=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;D:\msvs8\VC\ATLMFC\LIB
  LOCALAPPDATA=C:\Users\cltbld\AppData\Local
  LOGONSERVER=\\TALOS-R3-W7-058
  MINIDUMP_SAVE_PATH=c:\talos-slave\test/minidumps
  MINIDUMP_STACKWALK=c:\talos-slave\test\tools/breakpad/win32/minidump_stackwalk.exe
  MOZILLABUILD=D:\mozilla-build
  MOZILLABUILDDRIVE=C:
  MOZILLABUILDPATH=\mozilla-build\
  MOZ_AIRBAG=1
  MOZ_CRASHREPORTER_NO_REPORT=1
  MOZ_HIDE_RESULTS_TABLE=1
  MOZ_MSVCVERSION=8
  MOZ_NO_REMOTE=1
  MOZ_TOOLS=D:\mozilla-build\moztools
  MSVCDir=D:\msvs8\VC
  NO_EM_RESTART=1
  NO_FAIL_ON_TEST_ERRORS=1
  NUMBER_OF_PROCESSORS=2
  OS=Windows_NT
  PATH=buildbotve\scripts;C:\Program Files\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files\gnuwin32\bin;c:\Program Files\Vim\vim72\;c:\Python24\;c:\Python24\Scripts\;c:\Windows\;C:\Program Files\Microsoft Windows Performance Toolkit\
  PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
  PROCESSOR_ARCHITECTURE=x86
  PROCESSOR_IDENTIFIER=x86 Family 6 Model 23 Stepping 10, GenuineIntel
  PROCESSOR_LEVEL=6
  PROCESSOR_REVISION=170a
  PROGRAMDATA=C:\ProgramData
  PROGRAMFILES=C:\Program Files
  PROMPT=$P$G
  PSMODULEPATH=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
  PUBLIC=C:\Users\Public
  PWD=c:\talos-slave\test
  SYSTEMDRIVE=C:
  SYSTEMROOT=C:\Windows
  TEMP=C:\Users\cltbld\AppData\Local\Temp
  TMP=C:\Users\cltbld\AppData\Local\Temp
  USERDOMAIN=TALOS-R3-W7-058
  USERNAME=cltbld
  USERPROFILE=C:\Users\cltbld
  VCINSTALLDIR=D:\msvs8\VC
  VCVARS=D:\msvs8\VC\bin\vcvars32.bat
  VSINSTALLDIR=D:\msvs8
  WINDIR=C:\Windows
  XPCOM_DEBUG_BREAK=warn
 using PTY: False
Traceback (most recent call last):
  File "tools/buildfarm/maintenance/purge_builds.py", line 202, in ?
    purge(base_dirs, options.size, options.skip, cutoff_time, options.dry_run)
  File "tools/buildfarm/maintenance/purge_builds.py", line 94, in purge
    if any([fnmatch(d, pattern) for pattern in ignore]):
NameError: global name 'any' is not defined
program finished with exit code 1
elapsedTime=2.302000
purge_target: '1.0GB'
======== Finished set props: purge_target (results: 2, elapsed: 10 secs) ========

My guess is that Python 2.4 (which does not include the "any" builtin) is being used for some reason.

Comment 1

[Rail Aliiev [:rail]]

It looks like fallout of bug 705403

Comment 2

[Matt Brubeck (:mbrubeck)]

It affected all the Win PGO tests on this build:
https://tbpl.mozilla.org/?rev=206305cbbeb1

I think it's probably affecting all Windows tests since the problem started.  I'm going to close the trees until we have a fix...

Comment 3

[[e-mail] (:bhearsum)]

Looking into it.

Comment 4

[[e-mail] (:bhearsum)]

(In reply to Rail Aliiev [:rail] from comment #1)
> It looks like fallout of bug 705403

I agree. I backed this out and am in the process of reconfiging the masters now. Should be fixed shortly, and I'll retrigger failed tests.

Comment 5

[[e-mail] (:bhearsum)]

All masters have been updated with the backout, I've retriggered failed jobs, and I see that some of them have gotten past the point of failure already -> FIXED.