Re: [m5-dev] bogus rebuild clue

2011-04-17 Thread Ali Saidi
Some more hints about what is going on from the SCons mailing list. Definitely 
could be our problem

Ali


Hi!
I am currently tracking down a weird error that causes scons to rebuild files 
in my project when I run scons a 2nd time, even though the files were 
successfully built the first time.
I have been tracking this in winpdb quite far, and I was hoping that someone 
would be able to accelerate my search.
This is how far I have gotten:
My project is a multi env project where I build a generator tool (exe) in one 
build environment and then I use that exe in a different environment (I use 
multiple envs as the exe is for win32 and the target is for arm)
The exe is using precompiled headers and the PCH file is regenerated the 2nd 
time I run a clean build. The PCH has two target files, the .pch file and the 
.obj file. The reason why the PCH command is rerun is that that the dependency 
comparison retursn up_to_date False for the .obj file (whats strage is that the 
.pch file dependency is up to date!) When I looked closer _why_ the 
dependencies are not up to date, I noticed that the first entry of 
self.implicit for the .obj file was "..\cl.exe". This did not match the sig of 
the stored dependency. No wonder as the stored sig was the sig of a completely 
different file! The second time the build is run, the first implicit dependency 
has changed to match the stored sig and self.implicit now contained "..\cl.exe" 
at the end of the list. As the list of implicit dependencies look different 
between the two runs, I am not surprised that the target looks out of date and 
'fortunately' the implicit list will eventually 'stabilize' with "..
 \cl.exe" at the end so this only causes rebuild once. However, as my project 
is rather large, I'd rather avoid the rebuild ;)

Whats strange here is:
Why is the implicit list different for the .pch and .obj? They are generated by 
the same emitter!
Why is the implicit list for .obj changing beteween runs?

If this sparks any ideas, let me know, in the meantime, I will keep looking and 
hopefully be able to write a test case that can trigger this.

regards,
Stefan Burstrom


I think I have been able to narrow this down quite a bit. Here is the flow and 
what I think goes wrong:

env.PCH() sets up a node with two targets: .pch and .obj

In my env.PCH call I supply a file name that does not exist, it is generated 
during the build.

When the build tree is considered and the .pch node is encountered, this 
triggers the generation of my file. This causes the implicit list in the .pch 
node to be cleared and recreated (in the call to Node.scan()) this will 
eventually trickle down to add_to_implicit which is going to add the new 
implicit dependencies. However, as the .obj node is also a part of the target, 
add_to_implicit is also called on the .obj node. But this time, the existing 
implicit list in the .obj node is not empty.

The .pch and .obj node now has 2 lists of implicit dependencies that are 
differen (only the order though) even though they are targets depending on the 
same source file! These two lists are stored in the .sconsign file. Next time 
the build is run, the generated file exists, so the generation of the implicit 
deps lists will now result in two lists that are identical for .pch and for 
.obj. But as the previous stored info in the .sconsign file had the 
dependencies for .obj in a different order, .obj will now of course be out of 
date. This causes the .PCH command to be rerun. When the result from this build 
is stored in the .sconsign file, the new order of the deps is used which will 
now be consistent accross the runs.

I guess I could fix this making the input file to the .PCH call be a static 
file. But at the end of the day, this really seem to be pointing out a flaw in 
the way scons deals with generated include files that are used as sources for 
builders with multiple targets. I dont yet have a test case for this, but my 
guess is that it should be fairly trivial to set one up that does not depend on 
using .PCH for triggering the problem (A simple custom builder with 2 target 
nodes should do it)

A further investigation revealed the following:
My build has a dependency in the .PCH call to a generated file. During the 
build process, the built() function is called when my generated file is ready. 
This causes scons to clear the implicit dependencies in the parent node to the 
generated file. However, the way my build executes, only the .pch file has been 
added as a waiting parent. The .obj file is not yet considered as a parent by 
the taskmaster. This causes the implicit list in the .pch file to be cleared 
(and subsequently updated), however, the implicit list for the .obj file will 
now contain the same entries but in a different order. It seems natural to 
clear the implicit list in all targets of a node when the one of the sources 
for the node has been built. (Instead of just clearing the implicit lists for 
the parents that 

[m5-dev] changeset in m5: style: fix all_regions code and remove bogus re...

2011-04-17 Thread Nathan Binkert
changeset d8ec0a7b3f0c in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=d8ec0a7b3f0c
description:
style: fix all_regions code and remove bogus region type

diffstat:

 util/style.py |  6 +-
 1 files changed, 1 insertions(+), 5 deletions(-)

diffs (23 lines):

diff -r b83e07b4541d -r d8ec0a7b3f0c util/style.py
--- a/util/style.py Sun Apr 17 13:57:40 2011 -0700
+++ b/util/style.py Sun Apr 17 14:21:04 2011 -0700
@@ -45,7 +45,7 @@
 import sort_includes
 from file_types import lang_type
 
-all_regions = Region(neg_inf, pos_inf)
+all_regions = Regions(Region(neg_inf, pos_inf))
 
 tabsize = 8
 lead = re.compile(r'^([ \t]+)')
@@ -114,10 +114,6 @@
 def write(self, string):
 sys.stdout.write(string)
 
-class Region(object):
-def __init__(self, asdf):
-self.regions = Foo
-
 class Verifier(object):
 def __init__(self, ui, repo=None):
 self.ui = ui
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev


Re: [m5-dev] Cron /z/m5/regression/do-regression --scratch all

2011-04-17 Thread nathan binkert
Argh.  I guess different versions of python deal with this differently
too.  I'll try to fix this tonight.  Stupid demandimport.

  Nate

> Deleting build didn't seem to do anything.
>
> Traceback (most recent call last):
>  File "", line 1, in 
>  File "/z/m5/regression/zizzer/m5/src/python/importer.py", line 73, in
> load_module
>    exec code in mod.__dict__
>  File "/z/m5/regression/zizzer/m5/src/python/m5/__init__.py", line 38,
> in 
>    internal.core.__package__
> AttributeError: 'module' object has no attribute '__package__'
> Traceback (most recent call last):
>  File "", line 1, in 
>  File "/z/m5/regression/zizzer/m5/src/python/importer.py", line 73, in
> load_module
>    exec code in mod.__dict__
>  File "/z/m5/regression/zizzer/m5/src/python/m5/__init__.py", line 38,
> in 
>    internal.core.__package__
> AttributeError: 'module' object has no attribute '__package__'
> M5 exited with non-zero status 1
> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/inorder-timing
> FAILED!
>
> On 04/17/11 03:51, Cron Daemon wrote:
>> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/inorder-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing 
>> FAILED!
>> * 
>> build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-atomic 
>> FAILED!
>>  * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/inorder-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-atomic FAILED!
>> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing FAILED!
>> * 
>> build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-atomic 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/o3-timing FAILED!
>> * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp 
>> FAILED!
>> * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing 
>> FAILED!
>> * 
>> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer
>>  FAILED!
>> * 
>> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer
>>  FAILED!
>> * 
>> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer
>>  FAILED!
>> * 
>> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer
>>  FAILED!
>> * 
>> build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/50.memtest/alpha/linux

[m5-dev] changeset in m5: style: remove extra debugging print

2011-04-17 Thread Nathan Binkert
changeset b83e07b4541d in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=b83e07b4541d
description:
style: remove extra debugging print

diffstat:

 util/style.py |  1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diffs (11 lines):

diff -r a660cabc3ea6 -r b83e07b4541d util/style.py
--- a/util/style.py Sun Apr 17 13:57:03 2011 -0700
+++ b/util/style.py Sun Apr 17 13:57:40 2011 -0700
@@ -243,7 +243,6 @@
 
 mod = modified_regions(old, new)
 modified = mod & regions
-print mod, regions, modified
 
 if modified:
 self.write("invalid sorting of includes\n")
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev


[m5-dev] changeset in m5: file_types: Make code work in Python 2.4

2011-04-17 Thread Nathan Binkert
changeset a660cabc3ea6 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=a660cabc3ea6
description:
file_types: Make code work in Python 2.4

diffstat:

 util/file_types.py |  5 -
 1 files changed, 4 insertions(+), 1 deletions(-)

diffs (15 lines):

diff -r 6381dc8bcfcc -r a660cabc3ea6 util/file_types.py
--- a/util/file_types.pyFri Apr 15 10:45:11 2011 -0700
+++ b/util/file_types.pySun Apr 17 13:57:03 2011 -0700
@@ -140,7 +140,10 @@
 
 if isinstance(src, str):
 # if a filename was provided, open the file
-mode = 'r+' if inplace else 'r'
+if inplace:
+mode = 'r+'
+else:
+mode = 'r'
 src = file(src, mode)
 
 orig_lines = []
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev


Re: [m5-dev] Cron /z/m5/regression/do-regression --scratch all

2011-04-17 Thread Gabe Black
Deleting build didn't seem to do anything.

Traceback (most recent call last):
  File "", line 1, in 
  File "/z/m5/regression/zizzer/m5/src/python/importer.py", line 73, in
load_module
exec code in mod.__dict__
  File "/z/m5/regression/zizzer/m5/src/python/m5/__init__.py", line 38,
in 
internal.core.__package__
AttributeError: 'module' object has no attribute '__package__'
Traceback (most recent call last):
  File "", line 1, in 
  File "/z/m5/regression/zizzer/m5/src/python/importer.py", line 73, in
load_module
exec code in mod.__dict__
  File "/z/m5/regression/zizzer/m5/src/python/m5/__init__.py", line 38,
in 
internal.core.__package__
AttributeError: 'module' object has no attribute '__package__'
M5 exited with non-zero status 1
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/inorder-timing
FAILED!

On 04/17/11 03:51, Cron Daemon wrote:
> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/inorder-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-atomic 
> FAILED!
>  * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-timing FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/simple-timing FAILED!
> * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/inorder-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-atomic FAILED!
> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-atomic 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/simple-atomic FAILED!
> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-atomic 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing 
> FAILED!
> * build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/o3-timing FAILED!
> * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp 
> FAILED!
> * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing 
> FAILED!
> * 
> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer
>  FAILED!
> * 
> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer
>  FAILED!
> * 
> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer
>  FAILED!
> * 
> build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer
>  FAILED!
> * 
> build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MESI_CMP_directory
>  FAILED!
> * 
> build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory
>  FAILED!
> * 
> build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby

[m5-dev] Cron /z/m5/regression/do-regression --scratch all

2011-04-17 Thread Cron Daemon
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/inorder-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic 
FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby 
FAILED!
* build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby 
FAILED!
* build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-atomic 
FAILED!
 * build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing 
FAILED!
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/inorder-timing FAILED!
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/long/40.perlbmk/alpha/tru64/simple-timing 
FAILED!
* build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby 
FAILED!
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing 
FAILED!
* build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/inorder-timing FAILED!
* build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/long/30.eon/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/long/70.twolf/alpha/tru64/simple-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp 
FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby 
FAILED!
* build/ALPHA_SE/tests/fast/long/00.gzip/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/simple-atomic FAILED!
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/inorder-timing 
FAILED!
* build/ALPHA_SE/tests/fast/long/60.bzip2/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/long/50.vortex/alpha/tru64/o3-timing FAILED!
* build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp 
FAILED!
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing 
FAILED!
* 
build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer
 FAILED!
* 
build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer
 FAILED!
* 
build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer
 FAILED!
* 
build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer
 FAILED!
* 
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_CMP_token
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token
 FAILED!
* 
build/ALPHA_SE_MOESI_CMP_token/tests/fa