Ah, I found them (what a pain...).

Here's a couple of changeset removing these legacy stats. Maybe this will
solve the issue. I'm heading out for the day, but I'll check on it tomorrow
morning.

https://gem5-review.googlesource.com/c/public/gem5/+/52503
https://gem5-review.googlesource.com/c/public/gem5/+/52504

Cheers,
Jason

On Fri, Nov 5, 2021 at 4:55 PM Jason Lowe-Power <ja...@lowepower.com> wrote:

> Well, now I got the segfault in a stats++ operator (I can't tell you
> exactly where as the templates in stats hid all of the useful information).
> It happened ~10 cycles before the end of simulation this time.
>
> I am thinking it might be a "legacy" stat bug. But, again because of the
> template magic in stats I can't find the statistic name that is "legacy".
>
> Jason
>
> On Fri, Nov 5, 2021 at 4:48 PM Gabe Black <gabe.bl...@gmail.com> wrote:
>
>>
>>
>> On Fri, Nov 5, 2021 at 11:18 AM Jason Lowe-Power <ja...@lowepower.com>
>> wrote:
>>
>>> Here's what the undefined behavior sanitizer says with these patches
>>> applied. Also, the backtrace from the core dump is shown.
>>>
>>>
>>> build/ARM_clang/base/stats/text.cc:234:13: runtime error: load of value
>>> 32, which is not a valid value for type 'bool'
>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>> build/ARM_clang/base/stats/text.cc:234:13 in
>>> gem5 has encountered a segmentation fault!
>>>
>>
>> I think this will fix the undefined behavior at least:
>>
>> https://gem5-review.googlesource.com/c/public/gem5/+/52483
>>
>> The fact that the segfault happens after this point says even more that
>> this is some sort of cleanup thing, since the undefined behavior is from
>> when it's printing stats to a text file.
>>
>>
>>>
>>> --- BEGIN LIBC BACKTRACE ---
>>> build/ARM_clang/gem5.opt[0x1c7684a]
>>> build/ARM_clang/gem5.opt[0x1cc6255]
>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7feaafd103c0]
>>>
>>> /lib/x86_64-linux-gnu/libtcmalloc.so.4(_ZN8tcmalloc11ThreadCache21ReleaseToCentralCacheEPNS0_8FreeListEji+0x93)[0x7feaaf9b9f83]
>>>
>>> /lib/x86_64-linux-gnu/libtcmalloc.so.4(_ZN8tcmalloc11ThreadCache8ScavengeEv+0x4e)[0x7feaaf9ba2de]
>>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2707e8)[0x7feaaff8e7e8]
>>>
>>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyState_ClearModules+0xb5)[0x7feaafead745]
>>>
>>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(PyImport_Cleanup+0x4f7)[0x7feaafec61c7]
>>>
>>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(Py_FinalizeEx+0x90)[0x7feaafeb1690]
>>> build/ARM_clang/gem5.opt[0x1cc8a07]
>>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7feaaf28e0b3]
>>> build/ARM_clang/gem5.opt[0x5e078e]
>>> --- END LIBC BACKTRACE ---
>>>
>>
>> Is there some sort of bookkeeping bug in the stats interaction between
>> c++ and python? This is a crash in the heap manager triggered by the python
>> interpreter doing some sort of cleanup. I can imagine this being a latent
>> bug where something was corrupted earlier and it's just falling over now,
>> but this makes sense for three reasons. First, python stats related
>> problems would likely show up at the end when the stats are printed out
>> which is done partially through python. Second, python's reference counting
>> stuff would be easy to make a mistake with since it's complicated and
>> sometimes has to be handled manually. Third, when running valgrind, I
>> suppressed errors in the python library which would hide any bad behavior
>> right before the segfault.
>>
>>
>>
>>>
>>> Cheers,
>>> Jason
>>>
>>> On Fri, Nov 5, 2021 at 7:28 AM Gabe Black <gabe.bl...@gmail.com> wrote:
>>>
>>>> Can you try this pair of changes?
>>>>
>>>> https://gem5-review.googlesource.com/c/public/gem5/+/52485/1
>>>>
>>>> I think this should at least fix the undefined behavior, but when I
>>>> tried to test it it took an hour and a half to unsuccessfully compile with
>>>> the sanitizers for build/ARM so I gave up.
>>>>
>>>> I'm hopeful this could also fix the segfault?
>>>>
>>>> Gabe
>>>>
>>>> On Thu, Nov 4, 2021 at 4:18 PM Gabe Black <gabe.bl...@gmail.com> wrote:
>>>>
>>>>> Oh, yes, that does look very suspicious. I'll have to take a closer
>>>>> look at that!
>>>>>
>>>>> Gabe
>>>>>
>>>>> On Thu, Nov 4, 2021 at 3:02 PM Jason Lowe-Power <ja...@lowepower.com>
>>>>> wrote:
>>>>>
>>>>>> Glad you asked! I didn't look closely enough at the output.
>>>>>>
>>>>>> Here's an error that looks suspicious (The whole file is attached.)
>>>>>>
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:252:29: runtime error: constructor
>>>>>> call on misaligned address 0x00001c1ed9ac for type 'gem5::PhysRegId *',
>>>>>> which requires 8 byte alignment
>>>>>> 0x00001c1ed9ac: note: pointer points here
>>>>>>   00 00 00 00 00 00 00 00  50 d9 1e 1c 00 00 00 00  70 8d 20 1c 00 00
>>>>>> 00 00  40 58 1e 1c 00 00 00 00
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:252:29 in
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:335:13: runtime error: store to
>>>>>> misaligned address 0x00001c1ed9bc for type 'gem5::PhysRegIdPtr' (aka
>>>>>> 'gem5::PhysRegId *'), which requires 8 byte alignment
>>>>>> 0x00001c1ed9bc: note: pointer points here
>>>>>>   70 8d 20 1c 00 00 00 00  40 58 1e 1c 00 00 00 00  1a 00 00 00 00 00
>>>>>> 00 00  1a 00 00 00 00 00 00 00
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:335:13 in
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:307:13: runtime error: store to
>>>>>> misaligned address 0x00001c1ed9ac for type 'gem5::PhysRegIdPtr' (aka
>>>>>> 'gem5::PhysRegId *'), which requires 8 byte alignment
>>>>>> 0x00001c1ed9ac: note: pointer points here
>>>>>>   00 00 00 00 00 00 00 00  50 d9 1e 1c 00 00 00 00  70 8d 20 1c 00 00
>>>>>> fb 1c  00 00 00 00 80 10 fb 1c
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:307:13 in
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:322:13: runtime error: store to
>>>>>> misaligned address 0x00001c1ed9b4 for type 'gem5::PhysRegIdPtr' (aka
>>>>>> 'gem5::PhysRegId *'), which requires 8 byte alignment
>>>>>> 0x00001c1ed9b4: note: pointer points here
>>>>>>   00 00 00 00 00 00 00 00  70 8d 20 1c 00 00 fb 1c  00 00 00 00 80 10
>>>>>> fb 1c  00 00 00 00 50 0d fb 1c
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:322:13 in
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:300:20: runtime error: load of
>>>>>> misaligned address 0x00001c1ed9ac for type 'gem5::PhysRegIdPtr' (aka
>>>>>> 'gem5::PhysRegId *'), which requires 8 byte alignment
>>>>>> 0x00001c1ed9ac: note: pointer points here
>>>>>>   00 00 00 00 f0 8f 01 18  00 00 00 00 c0 8c 01 18  00 00 00 00 00 00
>>>>>> fb 1c  00 00 00 00 80 10 fb 1c
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:300:20 in
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:329:20: runtime error: load of
>>>>>> misaligned address 0x00001d223754 for type 'gem5::PhysRegIdPtr' (aka
>>>>>> 'gem5::PhysRegId *'), which requires 8 byte alignment
>>>>>> 0x00001d223754: note: pointer points here
>>>>>>   00 00 00 00 f0 8f 01 18  00 00 00 00 18 60 01 1d  00 00 00 00 78 60
>>>>>> 01 1d  00 00 00 00 78 60 01 1d
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:329:20 in
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:315:20: runtime error: load of
>>>>>> misaligned address 0x00001c1ecba4 for type 'gem5::PhysRegIdPtr' (aka
>>>>>> 'gem5::PhysRegId *'), which requires 8 byte alignment
>>>>>> 0x00001c1ecba4: note: pointer points here
>>>>>>   00 00 00 00 f8 90 01 18  00 00 00 00 f8 90 01 18  00 00 00 00 c0 60
>>>>>> 01 1d  00 00 00 00 78 60 01 1d
>>>>>>               ^
>>>>>> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
>>>>>> build/ARM_clang/cpu/o3/dyn_inst.hh:315:20 in
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>> Jason
>>>>>>
>>>>>> On Thu, Nov 4, 2021 at 2:51 PM Gabe Black <gabe.bl...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Did you find anything with ASAN?
>>>>>>>
>>>>>>> Gabe
>>>>>>>
>>>>>>> On Thu, Nov 4, 2021, 12:59 PM Gabe Black <gabe.bl...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I don't know if they do, and frankly even the unique_ptr change
>>>>>>>> could since that could fix heap corruption, even though it's unlikely 
>>>>>>>> since
>>>>>>>> I don't think this regression uses any of that code (except maybe 
>>>>>>>> VIO). We
>>>>>>>> don't actually *know* that that change is at fault, even though I agree
>>>>>>>> that it seems like a reasonable guess. This could be one of those bugs
>>>>>>>> where something totally unrelated is wrong, and another change just 
>>>>>>>> shifts
>>>>>>>> things around until some address lines up with something bad.
>>>>>>>>
>>>>>>>> As valgrind grinds on, I think there's a good chance of identifying
>>>>>>>> exactly what the problem is. I think that should happen in the next 
>>>>>>>> day or
>>>>>>>> two, hopefully.
>>>>>>>>
>>>>>>>> Gabe
>>>>>>>>
>>>>>>>> On Thu, Nov 4, 2021 at 9:55 AM Jason Lowe-Power <
>>>>>>>> ja...@lowepower.com> wrote:
>>>>>>>>
>>>>>>>>> Hey Gabe,
>>>>>>>>>
>>>>>>>>> Do these fix the nightly regression? If not, we may need to back
>>>>>>>>> out "4fe56ff72 - (3 months ago) arch-arm,cpu: Replace rename modes 
>>>>>>>>> with
>>>>>>>>> split reg/elem register files." until we have a fix.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Jason
>>>>>>>>>
>>>>>>>>> On Thu, Nov 4, 2021 at 12:13 AM Gabe Black <gabe.bl...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Valgrind hasn't finished, but what it found so far is attached. I
>>>>>>>>>> went through it and have the following changes which should address 
>>>>>>>>>> these
>>>>>>>>>> uninitialized accesses, and an inefficiency in the cache it found by
>>>>>>>>>> accident.
>>>>>>>>>>
>>>>>>>>>> https://gem5-review.googlesource.com/c/public/gem5/+/52403
>>>>>>>>>> https://gem5-review.googlesource.com/c/public/gem5/+/52404
>>>>>>>>>> https://gem5-review.googlesource.com/c/public/gem5/+/52405
>>>>>>>>>> https://gem5-review.googlesource.com/c/public/gem5/+/52406
>>>>>>>>>>
>>>>>>>>>> Gabe
>>>>>>>>>>
>>>>>>>>>> On Wed, Nov 3, 2021 at 12:45 PM Jason Lowe-Power <
>>>>>>>>>> ja...@lowepower.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Here's my data:
>>>>>>>>>>>
>>>>>>>>>>> BAD * 4fe56ff72 - (3 months ago) arch-arm,cpu: Replace rename
>>>>>>>>>>> modes with split reg/elem register files. - Gabe Black
>>>>>>>>>>> GOOD * 25138cbb7 - (4 weeks ago) arch: Simplify and tidy up
>>>>>>>>>>> PCState classes. - Gabe Black
>>>>>>>>>>> * 930986332 - (7 days ago) mem: Fix whitespace in
>>>>>>>>>>> mem/ruby/system/Sequencer.py. - Gabe Black
>>>>>>>>>>> GOOD * 69e6ea485 - (3 months ago) arch-arm: Add walkBits method
>>>>>>>>>>> to PageTableOps - Giacomo Travaglini
>>>>>>>>>>> * 1268c6ec3 - (2 weeks ago) arch-arm: Expose LookupLevel enum to
>>>>>>>>>>> the python world - Giacomo Travaglini
>>>>>>>>>>>
>>>>>>>>>>> I've tested this a number of times and tested commits before and
>>>>>>>>>>> after these commits. I have increasing confidence (though no 
>>>>>>>>>>> certainty)
>>>>>>>>>>> that 4fe56ff72 is the culprit.
>>>>>>>>>>>
>>>>>>>>>>> I'm running a UBSAN now to see if that will help at all.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Jason
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 2, 2021 at 5:28 PM Gabe Black <gabe.bl...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I'm going to kill it now, and restart it with
>>>>>>>>>>>> --track-origins=yes and in a separate tree so I can keep working 
>>>>>>>>>>>> on other
>>>>>>>>>>>> things while it runs.
>>>>>>>>>>>>
>>>>>>>>>>>> Gabe
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 2, 2021 at 5:11 PM Gabe Black <gabe.bl...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> It's still running, but here's what it's found so far.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Gabe
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 2, 2021 at 7:48 AM Jason Lowe-Power <
>>>>>>>>>>>>> ja...@lowepower.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks! I tried a bisect but, tbh, it wasn't helpful since
>>>>>>>>>>>>>> the error doesn't seem to be deterministic.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As more evidence that it's a memory issue, the backtrace that
>>>>>>>>>>>>>> I saw with GDB was something a bit different.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 2, 2021 at 5:07 AM Gabe Black <
>>>>>>>>>>>>>> gabe.bl...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm running it under valgrind to see if that tells me
>>>>>>>>>>>>>>> anything, which is going to take a while. I'll let you know 
>>>>>>>>>>>>>>> if/when it
>>>>>>>>>>>>>>> finishes.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Gabe
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 2, 2021 at 4:36 AM Gabe Black <
>>>>>>>>>>>>>>> gabe.bl...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Attached is a log of a failing run, and backtrace of the
>>>>>>>>>>>>>>>> segfault.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Gabe
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 2, 2021 at 4:17 AM Gabe Black <
>>>>>>>>>>>>>>>> gabe.bl...@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Ok, I reproduced the segfault once, but then running again
>>>>>>>>>>>>>>>>> in gdb it exited normally. I'm pretty confident it's 
>>>>>>>>>>>>>>>>> something to do with
>>>>>>>>>>>>>>>>> things getting cleaned up and/or destructed at the end of the 
>>>>>>>>>>>>>>>>> simulation,
>>>>>>>>>>>>>>>>> but until I catch something in the act of exploding I won't 
>>>>>>>>>>>>>>>>> be able to nail
>>>>>>>>>>>>>>>>> down specifically what's doing it.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Gabe
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 2, 2021 at 3:46 AM Gabe Black <
>>>>>>>>>>>>>>>>> gabe.bl...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> A clean build seems to have fixed the IdeDisk problem.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 2, 2021 at 3:35 AM Gabe Black <
>>>>>>>>>>>>>>>>>> gabe.bl...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Can you get a backtrace from it? Or run it in valgrind?
>>>>>>>>>>>>>>>>>>> I'm trying to use the command line you provided locally, 
>>>>>>>>>>>>>>>>>>> but it's
>>>>>>>>>>>>>>>>>>> complaining about not being able to find IdeDisk which is 
>>>>>>>>>>>>>>>>>>> very strange... I
>>>>>>>>>>>>>>>>>>> don't think I have an account on the machine where this 
>>>>>>>>>>>>>>>>>>> ran, but ideally
>>>>>>>>>>>>>>>>>>> I'll be able to reproduce it locally where it will be 
>>>>>>>>>>>>>>>>>>> easier to work with.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Gabe
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Nov 1, 2021 at 3:03 PM Jason Lowe-Power <
>>>>>>>>>>>>>>>>>>> ja...@lowepower.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> After spending some time on this, there is definitely a
>>>>>>>>>>>>>>>>>>>> segfault at the end of execution. It's odd that the 
>>>>>>>>>>>>>>>>>>>> testing scripts
>>>>>>>>>>>>>>>>>>>> sometimes reports that it works.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> If you run the following, you should see a segfault at
>>>>>>>>>>>>>>>>>>>> the end and no stats are generated:
>>>>>>>>>>>>>>>>>>>> ../gem5/> build/ARM/gem5.opt
>>>>>>>>>>>>>>>>>>>> tests/gem5/fs/linux/arm/run.py 
>>>>>>>>>>>>>>>>>>>> tests/gem5/configs/realview-o3.py
>>>>>>>>>>>>>>>>>>>> tests/gem5/resources/arm .
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I also notice that when it doesn't fail the following
>>>>>>>>>>>>>>>>>>>> is printed:
>>>>>>>>>>>>>>>>>>>> "build/ARM/arch/arm/isa.hh:650: warn: User mode does
>>>>>>>>>>>>>>>>>>>> not have SPSR
>>>>>>>>>>>>>>>>>>>> build/ARM/arch/arm/isa.hh:650: warn: User mode does not
>>>>>>>>>>>>>>>>>>>> have SPSR"
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> But it's not printed when it fails.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Mon, Nov 1, 2021 at 8:29 AM Jason Lowe-Power <
>>>>>>>>>>>>>>>>>>>> ja...@lowepower.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I don't think so. The binaries haven't been updated
>>>>>>>>>>>>>>>>>>>>> since April ('aarch-system-20210904.tar.bz2'). Well, the 
>>>>>>>>>>>>>>>>>>>>> blame says April
>>>>>>>>>>>>>>>>>>>>> even if the filename is confusing (YYYYDDMM?).
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Here's the failure:
>>>>>>>>>>>>>>>>>>>>> https://jenkins.gem5.org/job/nightly/ws/tests/testing-results/SuiteUID%3Arealview-o3-ARM-x86_64-opt/TestUID%3Arealview-o3-ARM-x86_64-opt/simerr
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> build/ARM/arch/arm/insts/pseudo.cc:173: warn:
>>>>>>>>>>>>>>>>>>>>> instruction 'csdb' unimplemented
>>>>>>>>>>>>>>>>>>>>> build/ARM/arch/arm/generated/decoder-ns.cc.inc:100643:
>>>>>>>>>>>>>>>>>>>>> warn: instruction 'mcr bpiall' unimplemented
>>>>>>>>>>>>>>>>>>>>> gem5 has encountered a segmentation fault!
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Oct 30, 2021 at 4:11 AM Gabe Black via
>>>>>>>>>>>>>>>>>>>>> gem5-dev <gem5-dev@gem5.org> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Maybe you need to re-download the resources?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Gabe
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sat, Oct 30, 2021 at 3:50 AM jenkins-no-reply---
>>>>>>>>>>>>>>>>>>>>>> via gem5-dev <gem5-dev@gem5.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> See <
>>>>>>>>>>>>>>>>>>>>>>> https://jenkins.gem5.org/job/nightly/27/display/redirect
>>>>>>>>>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Changes:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> ------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>> [...truncated 809.58 KB...]
>>>>>>>>>>>>>>>>>>>>>>> [----------] 4 tests from CheckpointInFixture
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] CheckpointInFixture.FindSections
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] CheckpointInFixture.FindSections (1 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] CheckpointInFixture.FindEntries
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] CheckpointInFixture.FindEntries (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] CheckpointInFixture.ExtractEntries
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] CheckpointInFixture.ExtractEntries (0
>>>>>>>>>>>>>>>>>>>>>>> ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] CheckpointInFixture.SCSCptInPathScoped
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] CheckpointInFixture.SCSCptInPathScoped
>>>>>>>>>>>>>>>>>>>>>>> (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [----------] 4 tests from CheckpointInFixture (1 ms
>>>>>>>>>>>>>>>>>>>>>>> total)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [----------] 6 tests from SerializableFixture
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SCSChangeCptOutSingle
>>>>>>>>>>>>>>>>>>>>>>> [       OK ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SCSChangeCptOutSingle (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SCSChangeCptOutMultiple
>>>>>>>>>>>>>>>>>>>>>>> [       OK ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SCSChangeCptOutMultiple (1 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] SerializableFixture.SCSChangeCptOutLarge
>>>>>>>>>>>>>>>>>>>>>>> [       OK ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SCSChangeCptOutLarge (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SectionSerializationSimple
>>>>>>>>>>>>>>>>>>>>>>> [       OK ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.SectionSerializationSimple (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] SerializableFixture.ParamOutIn
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] SerializableFixture.ParamOutIn (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.ParamOutInMultipleSections
>>>>>>>>>>>>>>>>>>>>>>> [       OK ]
>>>>>>>>>>>>>>>>>>>>>>> SerializableFixture.ParamOutInMultipleSections (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [----------] 6 tests from SerializableFixture (2 ms
>>>>>>>>>>>>>>>>>>>>>>> total)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [----------] Global test environment tear-down
>>>>>>>>>>>>>>>>>>>>>>> [==========] 33 tests from 8 test suites ran. (171
>>>>>>>>>>>>>>>>>>>>>>> ms total)
>>>>>>>>>>>>>>>>>>>>>>> [  PASSED  ] 33 tests.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>   YOU HAVE 1 DISABLED TEST
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingDeathTest.PanicLoggerExitHelper
>>>>>>>>>>>>>>>>>>>>>>> (149 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingDeathTest.ExitMessage
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingDeathTest.ExitMessage (152 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingDeathTest.Panic
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingDeathTest.Panic (151 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingDeathTest.Fatal
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingDeathTest.Fatal (2 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingDeathTest.PanicIf
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingDeathTest.PanicIf (150 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingDeathTest.FatalIf
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingDeathTest.FatalIf (3 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingDeathTest.gem5Assert
>>>>>>>>>>>>>>>>>>>>>>> [  SKIPPED ] LoggingDeathTest.gem5Assert (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [----------] 13 tests from LoggingDeathTest (1216 ms
>>>>>>>>>>>>>>>>>>>>>>> total)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [----------] 21 tests from LoggingFixture
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.BasicPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.BasicPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.VariadicCharPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.VariadicCharPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.VariadicStringPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.VariadicStringPrint (0
>>>>>>>>>>>>>>>>>>>>>>> ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.VariadicCharMissingPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.VariadicCharMissingPrint
>>>>>>>>>>>>>>>>>>>>>>> (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ]
>>>>>>>>>>>>>>>>>>>>>>> LoggingFixture.VariadicStringMissingPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ]
>>>>>>>>>>>>>>>>>>>>>>> LoggingFixture.VariadicStringMissingPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.DisabledPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.DisabledPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.WarnLoggerPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.WarnLoggerPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.InfoLoggerPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.InfoLoggerPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.HackLoggerPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.HackLoggerPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.FatalLoggerPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.FatalLoggerPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.PanicLoggerPrint
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.PanicLoggerPrint (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.BaseMessage
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.BaseMessage (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.BaseMessageOnce
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.BaseMessageOnce (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.Warn
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.Warn (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.Inform
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.Inform (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.Hack
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.Hack (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.WarnOnce
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.WarnOnce (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.InformOnce
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.InformOnce (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.HackOnce
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.HackOnce (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.WarnIf
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.WarnIf (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [ RUN      ] LoggingFixture.WarnIfOnce
>>>>>>>>>>>>>>>>>>>>>>> [       OK ] LoggingFixture.WarnIfOnce (0 ms)
>>>>>>>>>>>>>>>>>>>>>>> [----------] 21 tests from LoggingFixture (0 ms
>>>>>>>>>>>>>>>>>>>>>>> total)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [----------] Global test environment tear-down
>>>>>>>>>>>>>>>>>>>>>>> [==========] 34 tests from 2 test suites ran. (1216
>>>>>>>>>>>>>>>>>>>>>>> ms total)
>>>>>>>>>>>>>>>>>>>>>>> [  PASSED  ] 32 tests.
>>>>>>>>>>>>>>>>>>>>>>> [  SKIPPED ] 2 tests, listed below:
>>>>>>>>>>>>>>>>>>>>>>> [  SKIPPED ] LoggingDeathTest.EmptyPrefix
>>>>>>>>>>>>>>>>>>>>>>> [  SKIPPED ] LoggingDeathTest.gem5Assert
>>>>>>>>>>>>>>>>>>>>>>> scons: done building targets.
>>>>>>>>>>>>>>>>>>>>>>> *** Summary of Warnings ***
>>>>>>>>>>>>>>>>>>>>>>> Warning: Deprecated namespaces are not supported by
>>>>>>>>>>>>>>>>>>>>>>> this compiler.
>>>>>>>>>>>>>>>>>>>>>>>          Please make sure to check the mailing list
>>>>>>>>>>>>>>>>>>>>>>> for deprecation
>>>>>>>>>>>>>>>>>>>>>>>          announcements.
>>>>>>>>>>>>>>>>>>>>>>> + docker run -u 118: --volume
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/..:/nobackup/jenkins/workspace/nightly/tests/..
>>>>>>>>>>>>>>>>>>>>>>> -w /nobackup/jenkins/workspace/nightly/tests/../tests 
>>>>>>>>>>>>>>>>>>>>>>> --rm
>>>>>>>>>>>>>>>>>>>>>>> gcr.io/gem5-test/ubuntu-20.04_all-dependencies
>>>>>>>>>>>>>>>>>>>>>>> ./main.py run --length long -j16 -t16
>>>>>>>>>>>>>>>>>>>>>>> Running the new gem5 testing script.
>>>>>>>>>>>>>>>>>>>>>>> For more information see TESTING.md.
>>>>>>>>>>>>>>>>>>>>>>> To see details as the testing scripts are running,
>>>>>>>>>>>>>>>>>>>>>>> use the option -v, -vv, or -vvv
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> ================================================================================
>>>>>>>>>>>>>>>>>>>>>>> Loading Tests
>>>>>>>>>>>>>>>>>>>>>>> Discovered 2856 tests and 2856 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/asmtest/tests.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 264 tests and 132 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/cpu_tests/test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 24 tests and 12 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/dram-lowp/test_dram_lowp.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 192 tests and 162 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/fs/linux/arm/test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 12 tests and 6 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/gem5_library_example_tests/test_gem5_library_examples.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 258 tests and 129 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/hello_se/test_hello_se.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 24 tests and 12 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/insttest_se/test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 0 tests and 0 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/kvm-fork-tests/test_kvm_fork_run.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 0 tests and 0 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/kvm-switch-tests/test_kvm_cpu_switch.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 36 tests and 36 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/learning_gem5/part1_test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 48 tests and 24 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/learning_gem5/part2_test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 18 tests and 9 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/learning_gem5/part3_test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 12 tests and 6 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/m5_util/test_exit.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 0 tests and 0 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/m5threads_test_atomic/test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 72 tests and 72 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/memory/test.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 0 tests and 0 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/parsec-benchmarks/test_parsec.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 72 tests and 36 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/riscv-boot-tests/test_linux_boot.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 24 tests and 6 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/stats/test_hdf5.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 21 tests and 21 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/test_build/test_build.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 120 tests and 120 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/test_memory_traffic_gen.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 150 tests and 126 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/gem5/x86-boot-tests/test_linux_boot.py
>>>>>>>>>>>>>>>>>>>>>>> Discovered 6 tests and 6 suites in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/pyunit/test_run.py
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> ================================================================================
>>>>>>>>>>>>>>>>>>>>>>> Running Tests from 48 suites
>>>>>>>>>>>>>>>>>>>>>>> Results will be stored in
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/tests/testing-results
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> ================================================================================
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/ARM/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/MIPS/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/SPARC/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/GCN3_X86_MSI/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/GCN3_X86/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/X86_MESI_Two_Level/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/X86/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Building the following targets. This may take a
>>>>>>>>>>>>>>>>>>>>>>> while.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> /nobackup/jenkins/workspace/nightly/build/POWER/gem5.opt
>>>>>>>>>>>>>>>>>>>>>>> You may want to run with only a single ISA(--isa=),
>>>>>>>>>>>>>>>>>>>>>>> use --skip-build, or use 'rerun'.
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-switcheroo-atomic-ARM-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> realview-switcheroo-noncaching-timing-ARM-x86_64-opt 
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-switcheroo-timing-ARM-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-simple-atomic-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> realview-simple-atomic-checkpoint-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-mips-hello-timing-MIPS-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-mips-hello-timing-MIPS-x86_64-opt-MatchRegex Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-mips-hello-atomic-MIPS-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-mips-hello-atomic-MIPS-x86_64-opt-MatchRegex Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-mips-hello-o3-MIPS-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-mips-hello-o3-MIPS-x86_64-opt-MatchRegex
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-sparc-hello-timing-SPARC-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-sparc-hello-timing-SPARC-x86_64-opt-MatchRegex 
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-sparc-hello-atomic-SPARC-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-sparc-hello-atomic-SPARC-x86_64-opt-MatchRegex 
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-sparc-insttest-atomic-SPARC-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-sparc-insttest-atomic-SPARC-x86_64-opt-MatchStdoutNoPerf
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: test-sparc-insttest-timing-SPARC-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-sparc-insttest-timing-SPARC-x86_64-opt-MatchStdoutNoPerf
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: simple_ruby_test-GCN3_X86-x86_64-opt-MSI Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> simple_ruby_test-GCN3_X86-x86_64-opt-MSI-MatchStdoutNoPerf
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: ruby_test_test-GCN3_X86-x86_64-opt-MSI Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> ruby_test_test-GCN3_X86-x86_64-opt-MSI-MatchStdout 
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: build-X86-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: build-SPARC-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: build-MIPS-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: build-POWER-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-LinearGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelDDR3_1600-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-LinearGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelDDR3_2133-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-LinearGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelDDR4_2400-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-LinearGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelLPDDR3_1600-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-LinearGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelHBM-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-minor-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-RandomGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelDDR3_1600-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-RandomGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelDDR3_2133-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-RandomGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelDDR4_2400-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-RandomGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelLPDDR3_1600-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> test-memory-RandomGenerator.MESITwoLevel.gem5.components.memory.single_channel.SingleChannelHBM-NULL-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-switcheroo-full-ARM-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-minor-dual-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> realview64-minor-dual-ARM-x86_64-opt-MatchFileRegex 
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-simple-timing-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-switcheroo-o3-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-switcheroo-full-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-o3-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-o3-dual-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> realview64-o3-dual-ARM-x86_64-opt-MatchFileRegex Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-minor-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-switcheroo-o3-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-o3-checker-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> atomic-cpu_1-cores_classic_init_x86-boot-test-GCN3_X86-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-o3-ARM-x86_64-opt Failed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview64-simple-timing-ruby-ARM-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> realview64-simple-timing-dual-ruby-ARM-x86_64-opt Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> realview64-simple-timing-dual-ruby-ARM-x86_64-opt-MatchFileRegex
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test: realview-simple-timing-ruby-ARM-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> timing-cpu_1-cores_mi_example_init_x86-boot-test-X86-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> timing-cpu_1-cores_mesi_two_level_init_x86-boot-test-X86-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> atomic-cpu_4-cores_classic_systemd_x86-boot-test-GCN3_X86-x86_64-opt
>>>>>>>>>>>>>>>>>>>>>>>  Passed
>>>>>>>>>>>>>>>>>>>>>>> Test:
>>>>>>>>>>>>>>>>>>>>>>> o3-cpu_2-cores_mesi_two_level_init_x86-boot-test-X86-x86_64-opt-MESI_Two_Level
>>>>>>>>>>>>>>>>>>>>>>> Passed
>>>>>>>>>>>>>>>>>>>>>>> ============== Results: 59 Passed, 1 Failed in
>>>>>>>>>>>>>>>>>>>>>>> 1.1e+04 seconds  ================
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/ARM/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/SPARC/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/SPARC/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/SPARC/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> build/SPARC/base/statistics.hh:277: warn: One of the
>>>>>>>>>>>>>>>>>>>>>>> stats is a legacy stat. Legacy stat is a stat that does 
>>>>>>>>>>>>>>>>>>>>>>> not belong to any
>>>>>>>>>>>>>>>>>>>>>>> statistics::Group. Legacy stat is deprecated.
>>>>>>>>>>>>>>>>>>>>>>> Build step 'Execute shell' marked build as failure
>>>>>>>>>>>>>>>>>>>>>>> Archiving artifacts
>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>> gem5-dev mailing list -- gem5-dev@gem5.org
>>>>>>>>>>>>>>>>>>>>>>> To unsubscribe send an email to
>>>>>>>>>>>>>>>>>>>>>>> gem5-dev-le...@gem5.org
>>>>>>>>>>>>>>>>>>>>>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>> gem5-dev mailing list -- gem5-dev@gem5.org
>>>>>>>>>>>>>>>>>>>>>> To unsubscribe send an email to
>>>>>>>>>>>>>>>>>>>>>> gem5-dev-le...@gem5.org
>>>>>>>>>>>>>>>>>>>>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
_______________________________________________
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to