[gem5-dev] Test

This is a test for the mailing lists. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net ___ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org

[gem5-dev] Mailing List problems experienced this afternoon. Now resolved

Dear all, This afternoon we found out our mailing list was not sending emails to everyone who had subscribed to them. It seems this primarily affected those with Microsoft-based email addresses (outlook et al.). I've been told some filters were activated due to the high volume of email from our

[gem5-dev] Re: Mailing List problems experienced this afternoon. Now resolved

Dear all, We’ve had reports of spam on this mailing list. I thought I’d fixed this issue, but it seems like they were still getting through. To solve this for good, the mailing lists have been updated so only members of the list can post. As always, anyone can sign up to be a member of the

[gem5-dev] [NOTICE] Mailing lists successfully migrated!

Dear all, Thank you for your patience. If you have received this email it means our mailing lists have been successfully migrated. You should experience no change in service; please continue use the mailing lists as you have done so before. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235,

[gem5-dev] Re: RELEASE-NOTES file in gem5

Dear all, There is now a RELEASE_NOTES.md file in the root directory of gem5 (on develop branch for now). If anyone has any items they want included in this RELEASE_NOTES.md file, which are not noted already, then please get in touch with me and I'll add them. This list is the best way for us to

[gem5-dev] gem5 Staging Branch created

Dear all, As of 10AM PST the gem5 Staging Branch (release-staging-v20.0.0.0) has been created from the gem5 develop branch. Over the next two weeks we shall be running rigorous tests on this branch to ensure the upcoming release is as stable and bug-free as possible. We will then merge the

[gem5-dev] Re: GCB status

Hey Giacomo, Yes, it's intended. We're still planning to replace Kokoro with the GCB system (I'd actually like to call it Kokoro v2, as I'm rather fond of the name :) ). We treated the time GCB was on Gerrit as an experiment to see if it did what we wanted. By and large, it does. The

[gem5-dev] Pending gem5 20.1 "must haves"

Dear all, We're in the final push of getting stuff into the develop branch to be included in gem5 20.1. We've identified some outstanding items which have yet to be incorporated, but consider them "must haves" which need included before creating the staging branch. Outlined below are these work

[gem5-dev] Re: ARM build failures

Hey Gabe, Iru Cai made a fix for this a week or so ago: https://gem5-review.googlesource.com/c/public/gem5/+/33154. Not sure if this addresses all concerns, but their change is mostly basic reduction due to `imm` and `ecount` being unsigned. I also find if you take on board these observations,

[gem5-dev] Re: Build failed in Jenkins: gem5_develop #163

Hey Mike, Is there any reason these gem5_develop tests are still running? Is it safe to turn them off? From my understanding they are simply running the "main.py' script on the quick tests, which Kokoro does already (special thanks to Gabe who upgraded Kokoro for us :) ). When there is a failure,

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #20

Dear all, The compilation issues are fixed in the following commits: https://gem5-review.googlesource.com/c/public/gem5/+/33777 https://gem5-review.googlesource.com/c/public/gem5/+/33835 https://gem5-review.googlesource.com/c/public/gem5/+/33816

[gem5-dev] gem5 v20.1.0.0 Staging Branch created

Dear all, As of 10:45PM PST the gem5 Staging Branch for gem5 v20.1.0.0 has been created from the gem5 develop branch. Over the next two weeks we shall be running rigorous tests on this branch to ensure the upcoming release is as stable and bug-free as possible. We will then merge the release

[gem5-dev] Re: Build failed in Jenkins: Nightly #63

This failure is fixed by https://gem5-review.googlesource.com/c/public/gem5/+/34255 -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Sep 9, 2020 at 12:58 PM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #22

We're running into a lot of errors today :). I've fixed all the compilation errors. These are currently under review here: https://gem5-review.googlesource.com/c/public/gem5/+/34256 https://gem5-review.googlesource.com/c/public/gem5/+/34255 -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis

[gem5-dev] Re: Build failed in Jenkins: Nightly #91

Hey all, The source of this issue is that our Jenkin's server was using Python2, and a commit was merged which utilized some Python3 exclusive features: https://gem5-review.googlesource.com/c/public/gem5/+/33900 We are going to drop support for Python2 in the next release, so I've upgraded our

[gem5-dev] Re: Build failed in Jenkins: Nightly #91

gt; > > > > > What is/was the fix for this issue? I also cannot build even though I have > python 3.6 installed (via apt-get on Ubuntu 20.04). I am manually passing > python3-config to scons but I’m getting a syntax error when it sees the > metaclass keyword. > > > &

[gem5-dev] Re: Build failed in Jenkins: Nightly #92

This just failed because I messed up the docker command for the test. I've fixed this. I think they should pass tonight. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Fri, Oct 9, 2020 at 5:47 AM jenkins-no-reply--- via gem5-dev <

[gem5-dev] gem5 20.1 to be released in September 2020; 2 weeks to get in your changes!

Dear all, In one month's time gem5 v20.1.0.0 will be released. In accordance with our release procedures (https://gem5.googlesource.com/public/gem5 /+/refs/heads/master/CONTRIBUTING.md#releases), on September 1st we will create our release-staging branch from the develop branch. Therefore,

[gem5-dev] For gem5 20.1: Remove "master" and replace with new "stable" default branch (?)

Dear all, Back when we moved from the master branch being under constant development to a dual "master-as-stable" and "develop" branch setup, there was talk of renaming the master branch. Though, at this time, it seemed unconventional so avoided doing so. In the past few months there has been

[gem5-dev] Re: Build failed in Jenkins: gem5_develop #155

Hey Mike, Sorry for the delay in getting back to you. I'm pretty sure this is due to the following changes where we remove "ext/libelf" in favour of using the system's libelf: https://gem5-review.googlesource.com/c/public/gem5/+/33317 https://gem5-review.googlesource.com/c/public/gem5/+/33318

[gem5-dev] Re: gem5 documentation repo

Thanks Andreas! Documentation is still an ongoing process (and probably always will be :)), but we're happy things are in a better place these days. In regards to your idea of moving the website repo (or the documentation within the repo) into the gem5 repo. I have four counter-arguments to this

[gem5-dev] Re: Change in gem5/gem5[develop]: mem-cache: Create Compressor namespace

Just an FYI on this: The nightly builds don't clean the gem5 directory before pulling and recompiling. This saves us some build time. Obviously for stuff like this, we need a work around. I've therefore tweaked the building scripts with stuff like this: ``` scons build/ARM/gem5.opt -j4 || (rm

[gem5-dev] Re: problem running tests?

I agree the TestLib framework is broken when it comes to reporting output, which makes problems pretty difficult to figure things out. As far as I know, it's been this way for some time. My workflow when i get a failing test is to use `./main.py run --uid ` on the failing test suite which, when

[gem5-dev] Re: problem running tests?

Just checked v19 and it seems that, in this release, failing tests would output stderr and stdout to .testing-results, but if memory serves this was flakey. I _think_ the output wasn't recorded if gem5 crashed, which is a very common cause for test-case failure. In v20 nothing is recorded. If I

[gem5-dev] Re: Build failed in Jenkins: Nightly #75

Or it broke because I forgot the `s` in `scons build/NULL/unittests.perf` :). Fixed! -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Sep 22, 2020 at 7:52 AM Jason Lowe-Power wrote: > I think the problem is that google perftools

[gem5-dev] gem5 v20.1 released!

Dear all, gem5 v20.1.0.0 has officially been released! Using `git clone https://gem5.googlesource.com/public/gem5` will get you the latest version. Please note that HEAD now points towards our new `stable` branch, where gem5 v20.2 exists. The old master branch will be fully removed soon. There

[gem5-dev] Re: Segmentation fault in gem5

Hey, I haven't tried to replicate this segfault myself, but it may be related to this segfault we've encountered before: https://gem5.atlassian.net/browse/GEM5-782. We haven't really found the root cause of this problem yet. If this is the same issue, it can be overcome by compiling gem5 to it's

[gem5-dev] Re: A few quick thoughts

1) Seems fine to me. 2) I remember looking into this and I agree with Jason, it involves template magic which I'm not a huge fan of. I feel like in order to add these compile time asserts we'd be sacrificing some readability/ease-of-usability of bitfields.hh. This may just be a "me thing", but

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #23

It seems like the compiler tests started running on develop just before I merged all the fixes from the staging branch. I'm going to kick start the compiler tests again to ensure these tests pass. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web:

[gem5-dev] Re: New ARM patches on staging branch

Hey Giacomo, First of all, we'll keep the staging branch there for as long as you need. Though once merged into the master, the staging and the master should be identical (so I'm not really sure what the point is?). I actually released gem5 20 last night and was going to send out an email this

[gem5-dev] Hotfix: `python: Fix m5's tick rounding mechanism`

Dear all, Tiago has identified an issue which affects gem5 20: https://gem5.atlassian.net/browse/GEM5-616. This introduces a bug where the wrong clock frequencies may be reported due to a rounding error. This was introduced on the staging branch. We consider this quite severe and needs fixed

[gem5-dev] gem5 v20 released!

Dear all, gem5 v20.0.0.0 has officially been released! In keeping with our master-as-stable policy, the latest version of gem5 can be obtained by pulling the code from the master branch: https://gem5.googlesource.com/public/gem5. There have been a lot of changes since gem5 19, which we have

[gem5-dev] gem5 Users' Workshop Presentations!

Dear all, As some of you may be aware, we're running a special virtual gem5 Users' Workshop next Wednesday (June 3rd). As part of this virtual workshop,presenters have been asked to upload their presentations for attendees to view in advance. The session next Wednesday shall consist mainly of an

[gem5-dev] Re: Hotfix: `python: Fix m5's tick rounding mechanism`

Dear all, This hotfix has been applied to the master branch. We're now at gem5 version 20.0.0.1. The hotfix has also been merged into the develop branch. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net gem5 Virtual

[gem5-dev] gem5 Users' Workshop Presentations! [Part 2]

Dear all, In our second and final round of gem5 Workshop advertisements, we wish to make the gem5 community aware of the following presentations: "*gem5art: Zen and the Art of gem5 Experiments*", by Ayaz Akram, Mahyar Samani, Hoa Nguyen, Krithiga Murugavel, Trivikram Reddy, Marjan Fariborz,

[gem5-dev] Re: A call for maintainers

We also have our gem5-resources and gem5-website repositories, which we tag with "resources" and "website". Though separate repos, it may be worth adding maintainers for these things as they come up on Gerrit either way. I'm happy to volunteer as a maintainer for both. -- Dr. Bobby R. Bruce Room

[gem5-dev] Re: ubuntu boot test failure

Hey Mike, Sorry for taking so long to look into this. In short, I can't recreate this issue on my end. I've tried on three different systems (including our Jenkins server), and each time the gzipped file is downloaded and decompressed correctly. You are correct that some of the test resources

[gem5-dev] Re: Minimum scons version?

I've got no problem with this. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Aug 5, 2020 at 12:33 AM Gabe Black via gem5-dev wrote: > Hi folks. Our scons scripts currently require (through a > programmatic check) that you're

[gem5-dev] Re: [Suggestion] Replace gem5-users mailing-list with Discourse

iscourse :). >> >> >> >> Just to give a bit more context: I'm also trying to find a good forum >> for >> >> community engagement during my online Learning gem5 class this summer. >> I >> >> would like to find a platform

[gem5-dev] gem5 v20.0.0.3 Hotfix Release

Dear all, On July 1st we were made aware of a bug within gem5-20.0, reported by Hsuan Hsu here: https://gem5.atlassian.net/browse/GEM5-658. The bug resulted in gem5 crashing when calling m5ops, using the ARM ISA. Thankfully the source of this bug was found and fixed (here:

[gem5-dev] [Suggestion] Replace gem5-users mailing-list with Discourse

Dear all, In an effort to better support the gem5 community, there has been a suggestion that we drop the gem5-users mailing list and replace it with Discourse, https://www.discourse.org/about, a web-based discussion platform. I'm writing this email to propose this to the community and ask for

[gem5-dev] Re: Ruby Prefetcher Segfaulting

A hotfix to rectify this issue has been released (gem5 version 20.0.0.2 on the master branch). It has also been merged into the develop branch. Apologies to anyone who's encountered this issue. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web:

[gem5-dev] Re: gem5 Town Hall Meeting Youtube LiveFeed

Woops, accidentally sent that a bit prematurely :) Continuing... To join our YouTube LiveFeed, please use the following link: https://youtu.be/fvCXmMBblZY We will be monitoring the chat in this LiveFeed for questions and comments. We will try our best to ensure everyone is heard. Those with

[gem5-dev] gem5 Town Hall Meeting Youtube LiveFeed

Dear all, As with our meeting today, you can join tomorrow's town hall meeting (June 4th 1400 UTC) via Youtube Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net gem5 Virtual Workshop open for registration!! [Free to

[gem5-dev] Re: The Nightly Build system is now Live (Compiler tests too!)

gle Cloud or something else? > -- > *From:* Bobby Bruce via gem5-dev > *Sent:* Monday, July 27, 2020 7:54 PM > *To:* gem5 Developer List > *Cc:* Bobby Bruce > *Subject:* [gem5-dev] The Nightly Build system is now Live (Compiler > tests too!) > > Dear a

[gem5-dev] The Nightly Build system is now Live (Compiler tests too!)

Dear all, After some tinkering, we now have a nightly build system deployed, run from our Jenkins: https://jenkins.gem5.org. If I've set up the permissions correctly, everyone should be able to see the status of all our builds from there. Please note, at the time of writing, we're still

[gem5-dev] Re: testlib question

For those interested in the outcome of this. Hoa opened a Jira ticket, https://gem5.atlassian.net/browse/GEM5-709, and found a fix for this issue, currently under review here: https://gem5-review.googlesource.com/c/public/gem5/+/31994 -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis,

[gem5-dev] Invitation to complete the gem5 Survey 2020!

Dear all, To all those willing, I wish to extend an invitation to participate in this year's gem5 survey. The purpose of this survey is to provide valuable feedback to the gem5 community as to which areas of the project we should focus on over the next year and beyond. This survey may be

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #33

(Resending so message doesn't bounce on mailing list) > > Hi Bobby, > > Can you point us to what you would want in testlibs? > > Matt > > On Mon, Nov 30, 2020 at 2:38 PM Bobby Bruce via gem5-dev < > gem5-dev@gem5.org> wrote: > >> @Kyle: GCN3 is only bui

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #33

bly deleting the whole if block in > src/gpu-compute/X86GPUTLB.py could fix the error. Seems like a duplicate > definition to me. There is also no full system support for GPU yet anyway. > > > > > > -Matt > > > > > > *From:* Bobby Bruce via gem5-dev > *Sent:

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #33

Hey Matt and Kyle, It seems like the GCN3_X86 isn't building. The following error is being returned: http://jenkins.gem5.org/job/Compiler-Checks/33/artifact/compile-test-out/clang-version-9/GCN3_X86.opt.stderr.txt Could someone look into fixing this? Kind regards, Bobby -- Dr. Bobby R. Bruce

[gem5-dev] Re: Invitation to complete the gem5 Survey 2020!

This is a friendly reminder that you still have time to complete the 2020 gem5 survey if you have not already done so. This is a great chance to give the gem5 project feedback which we will use to decide where to allocate resources over the course of the next year. It only takes 10 minutes and is

[gem5-dev] Re: Build failed in Jenkins: Nightly #162

I think the Jenkins might have an older Docker image. I'll fix this. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net Please consider making a submission to GI@ICSE '21: http://geneticimprovementofsoftware.com/gi2021icse.html On Fri, Dec

[gem5-dev] Re: Build failed in Jenkins: Nightly #165

I messed up the wget on the new GCN3 tests. Should be fixed now :). -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net Please consider making a submission to GI@ICSE '21: http://geneticimprovementofsoftware.com/gi2021icse.html On Sun, Dec

[gem5-dev] gem5 v20.1.0.2 Hotfix Release

Dear all, We've fixed two bugs as part of a hotfix release for gem5 v20.1. A "ValueError: invalid literal for int() with base..." error was being thrown in certain circumstances due to a non-integer being passed to "MemorySize" via a division. This has been fixed. An assertion in Stats was

[gem5-dev] gem5 v20.1.0.1 Hotfix Release [Garnet Network Model]

Dear all, In the gem5 v20.1.0.0 release there was a bug in the Garnet Network Stats, which adversely affected the overall behavior of the Garnet Network Model. The bug, and related fix, are discussed here: https://gem5-review.googlesource.com/c/public/gem5/+/36416. On November 6th, we applied

[gem5-dev] Re: Status of Compiler-Checks tests

Hey Ciro, Due to us officially dropping support for Python2 in the next release, the develop branch was failing on the compilation tests due to the fact the Docker Image's we were running them on weren't configured correctly (some were purely Python2). So I paused the compiler tests while I fixed

[gem5-dev] Candidate Hot-fix v20.1.0.1: Fix Garnet Network Stats

Hey everyone, This is pretty inoffensive, but in line with procedures, I'd like to sign off (just some code-reviews +2) on this hot-fix I wish to apply to the stable branch: https://gem5-review.googlesource.com/c/public/gem5/+/37116. It fixes a bug in the Garnet Network Stats, which I've been

[gem5-dev] Potential v20.1 hot-fix --- Fixing Linux boot for Arm ISA

Dear all, A bug has been identified, here: https://gem5.atlassian.net/browse/GEM5-901, where Linux v5.4 failed to boot in v20.1 on the Arm ISA. A fix has been produced: https://gem5-review.googlesource.com/c/public/gem5/+/39695 It has been suggested that this should be added to gem5 as a hotfix

[gem5-dev] Re: Nightly stuck

Thanks Giacomo, I've jumped in and added timeouts to the Nightly builds and the compiler checks. The Nightly builds will now fail (instead of just "abort", which apparently is a silent failure) after 23 hours. Most of the time the nightly builds complete within 12ish hours (though this does vary

[gem5-dev] Re: Testing fail on GCN3_X86 on Arm machine

I'm guessing you're correct and this is because you're testing on an ARM machine. GCN3_X86 should compile fine, though we don't test on ARM hosts (we'd like to change this soon). I've added a Jira ticket covering this bug: https://gem5.atlassian.net/browse/GEM5-881. -- Dr. Bobby R. Bruce Room

[gem5-dev] Re: Some evidence build times have substantially increased on Jenkins

> > If you compare #patches with execution time you see a strong correlation > > between these two > > > > Same applies with the compiler check. Now situation is to get a bit > better, but > > IMHO in the last few days the combination of a) + b) has been lethal. &g

[gem5-dev] gem5 v20.1.0.3 Hotfix Release

Dear all, Last month a bug was identified where booting Linux stalled under certain circumstances when using the ARM ISA: https://gem5.atlassian.net/browse/GEM5-901. A fix was found and has been applied as a new hotfix release to v20.1. We would advise users to pull the latest gem5 release to

[gem5-dev] gem5 21.0 to be released March 2021; 2 weeks to get in your changes!

Dear all, We plan to release gem5 v21.0.0.0 next month. As such, we will be creating our release-staging branch from the develop branch on February 16th. Anything fully submitted on the develop branch by this date will be included in the gem5 21.0 release. Submitting patches to the

[gem5-dev] Some evidence build times have substantially increased on Jenkins

Dear all, As you may have noticed from the mailing list, our nightly builds are failing due to timeouts, as are the compiler checkers. Though this is just a preliminary look at the problem, I've noticed that the gem5 build times on our Jenkins have increased substantially. Looking at our last

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #43

Patches to fix these compilation errors can be found here: https://gem5-review.googlesource.com/c/public/gem5/+/40397 -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Feb 2, 2021 at 2:51 AM jenkins-no-reply--- via gem5-dev <

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #86

Just an FYI: The compiler tests are occasionally failing due to this bug: https://gem5.atlassian.net/browse/GEM5-1006 (in short, gem5 targeting X86 can't be compiled in GCC 5). So we don't compile every variation of gem5 against every version of GCC, for GCC 5 we randomly select a single gem5

[gem5-dev] gem5 21.1 to be released in July 2021; 2 weeks to get in your changes!

Dear all, On July 6th we will create the gem5 v21.1 release-staging branch from develop, with the intent of releasing gem5 v21.1 later that month. This means you have until July 6th to have patches you wish to be part of gem5 v21.1 fully merged into the develop branch. Submitting patches to the

[gem5-dev] gem5 Minor release: v21.0.1

Dear all. We're happy to announce our first minor release: version 21.0.1! This release consists entirely of bug fixes for v21.0 users. More information on exactly what has been fixed can be found here:

[gem5-dev] Re: RFC: run python Black on gem5 python code

re worth. I'm not opposed to having at least some > > stated > > > standard for python though, and the "official" one seems like a > > pretty > > > reasonable choice. I guess it's fine with me, up until it causes me > > some sort of > > &

[gem5-dev] Re: Build failed in Jenkins: nightly #307

Cool, thanks for the help. I believe this patch should fix the nightlys: https://gem5-review.googlesource.com/c/public/gem5/+/45480 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, May 11, 2021 at 7:27 PM Gabe Black wrote: > Yes,

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #72

These two patchset should fix most of this: https://gem5-review.googlesource.coThism/c/public/gem5/+/45479 , https://gem5-review.googlesource.com/c/public/gem5/+/45481 Unfortunately, we currently can't compile with GCC 5 as deprecation

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #72

nto > position to use c++17 with 7, and I think if we move to 8 it's pretty safe. > > Version 5.2 was released on July 16, 2015 > Version 7.3 was released on January 25, 2018 > Version 8.1 was released on May 2, 2018 > Version 11.1 was released very recently on April 27,

[gem5-dev] Re: Build failed in Jenkins: Compiler-Checks #65

This can be ignored. Just a hiccup during the Jenkins migration process :). -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Thu, May 6, 2021 at 3:57 PM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See < >

[gem5-dev] Jenkins Server migrated to UC Davis. Web Portal temporarily unavailable.

Dear all, In order to save the project some money, the Jenkins server has been moved from the cloud to a server at UC Davis. This is a temporary solution until we can find our Jenkins instance a more permanent home. The only important thing to note is that, in order to keep the UC Davis machine

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #72

were willing to bump clang support all the way up to version 9 (a >>> big leap, released 19 September 2019) we would get support for >>> __builtin_LINE and __builtin_FILE, which are there to support >>> std::source_location which is a c++20 feature but which can be used wi

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #72

up. I don't >>>>>>>> really know what benchmark we use to decide when that's ok to do. If >>>>>>>> we do >>>>>>>> move up, it would be nice to move to a version which would let us use >>>>>>>> c++17

[gem5-dev] Re: Build failed in Jenkins: nightly #307

Hey Daniel and Gabe, I'm looking into this test failure (reproducible with `scons build/NULL/unittests.fast`). I'm a little confused about how these tests ever passed. This patchet introduces the error (or at least, if this patch is reverted, the tests pass):

[gem5-dev] Re: test breakage for GCN3 on ToT?

Hey Gabe, When you say the 'hello' binary is dynamically linked, we're talking about the 'hello64-dynamic' binary? I agree these tests should probably be removed. (Does anyone have any objection to this?) This only appears to be half your problem though, as you've got "MatchStdoutNoPerf" tests

[gem5-dev] Re: problem with docker image?

It is annoying when this happens, and doubly so that it's clearly flakey and hard to reproduce. However, I've only ever seen this on Kokoro so I think the blame is somewhere there. Keep in mind, we run nightly tests using the same image and never seem to run into this issue, I'm quite confident

[gem5-dev] gem5 Minor release: Candidate patches

Dear all, I'm getting ready to go for our first gem5 minor release, consisting of bug fixes but no functionality/API changes. I've cherry-picked some candidates that have already been reviewed and merged on the develop branch. These can be found in this relation-chain:

[gem5-dev] Re: problem with docker image?

Correction: The command is "sleep", not "wait" :). -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, May 25, 2021 at 9:46 AM Bobby Bruce wrote: > It is annoying when this happens, and doubly so that it's clearly flakey > and hard

[gem5-dev] Re: Build failed in Jenkins: nightly #321

Just an FYI: I'm looking into this. It appears the realview-o3-ARM-x86_64-opt test is hanging until our timeout is reached. I'm currently trying to find the offending commit and will report back on possible fixes. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web:

[gem5-dev] Bug in O3 CPU on the develop branch.

Hey all, As you may have noticed, the nightly tests are failing. I've done some digging and found that the O3 realview tests (the ARM ISA) are hanging and reaching a timeout. You can reproduce this with: ``` python3 ./main.py run --uid

[gem5-dev] Re: Bug in O3 CPU on the develop branch.

We believe we've found a fix for this bug here: https://gem5-review.googlesource.com/c/public/gem5/+/46039. We'll need to re-run the nightlys to make sure. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, May 26, 2021 at 1:51 PM

[gem5-dev] Re: problem with docker image?

Yeah, I'm with you on your interpretation of that error. I forgot a negation in my original reply to this email thread. I meant to say I'm _not_ very confident in the wait solution, and the more I think it through, I'm even less so, as the error occurs after the docker image is pulled, so I'd

[gem5-dev] gem5 21.1 release: 1 week left to get your work into develop!

Dear all, Due to holidays and other commitments we've decided to give the gem5 developers a few more days to get their changes reviewed. We'll now create the v21.1 staging branch on end-of-day (California time) on July 9th. Let's make this a productive week and get in what we can :). Kind

[gem5-dev] Re: Deep dive into SCons

Hey Gabe, Thanks for this, I think this change will be welcome. In line with your proposal, I think anything that makes Scons more explicit would be really helpful. A lot of the current setup does things implicitly, which has tripped me up several times. One thing I feel is worth noting is that

[gem5-dev] Re: RFC: run python Black on gem5 python code

ne statements? >> >> Finally, I'd also rather have consistency; if this number changes, it'd >> be better to do so for all file extensions, not only Python files. >> >> That said, I'm against this change as is due to the discrepancy between >> advantages and disadvantages. &

[gem5-dev] Re: gem5 21.1 release: 1 week left to get your work into develop!

Dear all, The v21.1 staging branch has been created: https://gem5.googlesource.com/public/gem5/+/refs/heads/release-staging-v21-1. We'll start rigorously testing this branch in the coming weeks. As usual, we'll accept bug fixes to this branch and non-functional improvements such as improvements

[gem5-dev] Re: test library error

Hey Gabe, This is weird, though I cannot replicate it. I'd also guess it's weird timeout. Have you seen it elsewhere? Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Mon, Feb 8, 2021 at 9:31 PM Gabe Black via

[gem5-dev] gem5 v21.0 released!

Dear all, gem5 v21.0.0.0 has officially been released. Using `git clone https://gem5.googlesource.com/public/gem5` will get you the latest version. There have been a lot of changes since v20.1, which we have highlighted in our release-notes:

[gem5-dev] Re: Diagnosing failing tests in kokoro?

Hey Gabe, Right now when there are failures during download, a test fails quietly. I'm not aware of any way to quickly know when this happens. This is definitely far from ideal. I've added a Jira item to change this: https://gem5.atlassian.net/browse/GEM5-948. This isn't the first time this has

[gem5-dev] Re: More unreproducible kokoro failures... testlib bug?

I'm 95% sure I've just fixed this. The problem was due to me failing to include the aarch-system-20200611.tar.bz tarball on our Google Cloud when releasing v21.0. Kokoro downloads this to run certain arm tests. If it can't download this tarball the tests fail (I need to get round to improving this

[gem5-dev] Re: Diagnosing failing tests in kokoro?

Hey Gabe, As you can see in my other email, I just fixed this. It was a mess-up on my part, I forgot to include the aarch-system tarball in our Google Cloud Bucket. TestLib downloads this to run some Arm tests. The reason your tests passed locally is you probably had a local, cached version (in

[gem5-dev] gem5 v20.1.0.5 Hotfix Release

Dear all, The gem5 v20.1.0.5 hotfix release is now available on the stable branch: https://gem5.googlesource.com/public/gem5/. This fixes a number of bugs identified over recent weeks. As always, we advise gem5 users pull the latest version from the stable branch to keep up-to-date with the

[gem5-dev] Re: Some gem5 infrastructure down

Hey all, Thanks for your patience. Our Google Cloud infrastructure is now back online. I'll go through Gerrit momentarily to re-start the tests that failed due to this unexpected downtime. A couple of hours down over the course of a year... not too bad, all things considered :) Kind regards,

[gem5-dev] Re: gem5 v20.1.0.5 Hotfix Release

Slight amendment to this --- a third bug fix has been included: https://gem5-review.googlesource.com/c/public/gem5/+/43146. -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Mar 16, 2021 at 3:40 PM Bobby Bruce wrote: > Dear all, >

[gem5-dev] gem5 v20.1.0.5 Hotfix Release

Dear all, Two bugs were identified in the v20.1 release of gem5 and I've been persuaded their fixes should be added to the v20.1 release of gem5 as hotfixes. One concerns atomics permission checks in TLB, and the other is an incorrect cast to float values, instead of integer values, in

[gem5-dev] Re: RFC: run python Black on gem5 python code

Sounds like a good idea to me. --- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Mar 3, 2021 at 10:11 AM Daniel Carvalho via gem5-dev < gem5-dev@gem5.org> wrote: > +1 > > Em quarta-feira, 3 de março de 2021 14:35:57 BRT, Jason

  1   2   3   >