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

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

2020-10-13 Thread Giacomo Travaglini via gem5-dev

Yes you are right; of course when I use

alias scons=python `which scons`

I am assuming I already have a python3 installed somewhere in my machine as 
“python”
Your variation is probably better as doesn’t require you to use a virtualenv in 
a python2/python3 capable machine

Giacomo

From: Jason Lowe-Power 
Sent: 13 October 2020 16:46
To: gem5 Developer List 
Cc: Poremba, Matthew ; Giacomo Travaglini 

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

Hi all,

Yeah, this is 100% a scons problem. I'm not sure what we can do about it. To be 
more straightforward here are the possible solutions:

1. install python-is-python3
2. pip install scons
3. Edit /usr/bin/scons to use python3
4. Add `alias scons3="/usr/bin/env python3 $(which scons)"` to ~/.bashrc
5. probably others

For us, I think we should put a check at the very beginning of the scons 
execution to check to make sure it's running under python3. If it's not, we 
should print the above workarounds.

BTW, I don't think "alias scons=python `which scons`" will work in general. I 
think it should be "alias scons=python3 `which scons`" since python may be a 
symlink to python2.

Let me know if you have a better idea.

Cheers,
Jason

On Tue, Oct 13, 2020 at 8:41 AM Giacomo Travaglini via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
Forgot to mention: I am choosing the latter

Giacomo

From: Giacomo Travaglini
Sent: 13 October 2020 16:40
To: gem5 Developer List mailto:gem5-dev@gem5.org>>; Poremba, 
Matthew mailto:matthew.pore...@amd.com>>
Cc: Jieming Yin mailto:bjm...@gmail.com>>
Subject: RE: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

Hi all,

I had the same issue. The problem in my case was in scons, which was selecting 
python2 when building gem5 disregarding my python3 virtualenv

$less `which scons`
#! /usr/bin/python

And /usr/bin/python was linked to python2.7.

So the available solutions are:


  *   Installing a newer scons version with

#!/usr/bin/env python


  *   changing the symbolic link,
  *   modify the shebang of the preinstalled one,
  *   CL selection of the scons interpreter:
alias scons=python `which scons`

Kind Regards

Giacomo

From: Jieming Yin via gem5-dev mailto:gem5-dev@gem5.org>>
Sent: 09 October 2020 02:43
To: Poremba, Matthew mailto:matthew.pore...@amd.com>>
Cc: gem5 Developer List mailto:gem5-dev@gem5.org>>; Jieming 
Yin mailto:bjm...@gmail.com>>
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

Hi Matt,

My workaround is to do it in a python2 manner:

class SEWorkload(Workload):
type = 'SEWorkload'
__metaclass__ = SEWorkloadMeta

I have the same syntax error because I am running the gem5-gcn docker, and I 
have both python2 and python3 installed. But I don't really know how to fix it, 
it seems python2 is used sometimes.

Jieming

On Thu, Oct 8, 2020 at 7:43 PM Bobby Bruce via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
Hey Matt,

Before the nightly tests were run on Jenkins server which was an Ubuntu 18.04 
machine with Python2.

The nightly tests will now run using our Ubuntu 20.04 docker image: 
gcr.io/gem5-test/ubuntu-20.04_all-dependencies<http://gcr.io/gem5-test/ubuntu-20.04_all-dependencies>
 (Dockerfile source: 
https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile).

So, to compile gem5.opt for the ARM ISA, the nightly will use:

```
docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm 
gcr.io/gem5-test/ubuntu-20.04_all-dependencies<http://gcr.io/gem5-test/ubuntu-20.04_all-dependencies>
 scons build/ARM/gem5.opt
```

I'm going to guess you probably still have Python2 somewhere on your machine 
and it's using it during the compilation. I'll setup some tests on my end and 
see if I can recreate this problem. I _think_ right now we only test in 
environments that either have only Python2 or have only Python3, so we should 
probably have some tests to check what happens if someone has both.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Thu, Oct 8, 2020 at 4:10 PM Poremba, Matthew 
mailto:matthew.pore...@amd.com>> wrote:

[AMD Public Use]

Hi Bobby,


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.


-Matt

From: Bobby Bruce via gem5-dev mailto:gem5-dev@gem5.org>>
Sent: Thursday, October 8, 2020 3:19 PM
To: gem5 Developer List mailto:gem5-dev@gem5.org>>
Cc: Bobby Bruce mailto:bbr...@ucdavis.edu>>
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

[CAUTION: External Email]
Hey all,

The source of this issue is that our Jenkin's server was using Python2, and a 
commit was merged w

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

2020-10-13 Thread Jason Lowe-Power via gem5-dev

Hi all,

Yeah, this is 100% a scons problem. I'm not sure what we can do about it.
To be more straightforward here are the possible solutions:

1. install python-is-python3
2. pip install scons
3. Edit /usr/bin/scons to use python3
4. Add `alias scons3="/usr/bin/env python3 $(which scons)"` to ~/.bashrc
5. probably others

For us, I think we should put a check at the very beginning of the scons
execution to check to make sure it's running under python3. If it's not, we
should print the above workarounds.

BTW, I don't think "alias scons=python `which scons`" will work in general.
I think it should be "alias scons=python3 `which scons`" since python may
be a symlink to python2.

Let me know if you have a better idea.

Cheers,
Jason

On Tue, Oct 13, 2020 at 8:41 AM Giacomo Travaglini via gem5-dev <
gem5-dev@gem5.org> wrote:

> Forgot to mention: I am choosing the latter
>
>
>
> Giacomo
>
>
>
> *From:* Giacomo Travaglini
> *Sent:* 13 October 2020 16:40
> *To:* gem5 Developer List ; Poremba, Matthew <
> matthew.pore...@amd.com>
> *Cc:* Jieming Yin 
> *Subject:* RE: [gem5-dev] Re: Build failed in Jenkins: Nightly #91
>
>
>
> Hi all,
>
>
>
> I had the same issue. The problem in my case was in scons, which was
> selecting python2 when building gem5 disregarding my python3 virtualenv
>
>
>
> $less `which scons`
>
> #! /usr/bin/python
>
>
>
> And /usr/bin/python was linked to python2.7.
>
>
>
> So the available solutions are:
>
>
>
>- Installing a newer scons version with
>
>
>
> #!/usr/bin/env python
>
>
>
>- changing the symbolic link,
>- modify the shebang of the preinstalled one,
>- CL selection of the scons interpreter:
>
> alias scons=python `which scons`
>
>
>
> Kind Regards
>
>
>
> Giacomo
>
>
>
> *From:* Jieming Yin via gem5-dev 
> *Sent:* 09 October 2020 02:43
> *To:* Poremba, Matthew 
> *Cc:* gem5 Developer List ; Jieming Yin <
> bjm...@gmail.com>
> *Subject:* [gem5-dev] Re: Build failed in Jenkins: Nightly #91
>
>
>
> Hi Matt,
>
>
>
> My workaround is to do it in a python2 manner:
>
>
>
> class SEWorkload(Workload):
> type = 'SEWorkload'
> __metaclass__ = SEWorkloadMeta
>
>
>
> I have the same syntax error because I am running the gem5-gcn docker, and
> I have both python2 and python3 installed. But I don't really know how to
> fix it, it seems python2 is used sometimes.
>
>
>
> Jieming
>
>
>
> On Thu, Oct 8, 2020 at 7:43 PM Bobby Bruce via gem5-dev 
> wrote:
>
> Hey Matt,
>
>
>
> Before the nightly tests were run on Jenkins server which was an Ubuntu
> 18.04 machine with Python2.
>
>
>
> The nightly tests will now run using our Ubuntu 20.04 docker image:
> gcr.io/gem5-test/ubuntu-20.04_all-dependencies (Dockerfile source:
> https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile).
>
>
>
>
> So, to compile gem5.opt for the ARM ISA, the nightly will use:
>
>
>
> ```
>
> docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm
> gcr.io/gem5-test/ubuntu-20.04_all-dependencies scons build/ARM/gem5.opt
>
> ```
>
>
>
> I'm going to guess you probably still have Python2 somewhere on your
> machine and it's using it during the compilation. I'll setup some tests on
> my end and see if I can recreate this problem. I _think_ right now we only
> test in environments that either have only Python2 or have only Python3, so
> we should probably have some tests to check what happens if someone has
> both.
>
>
>
> Kind regards,
>
> Bobby
>
> --
>
> Dr. Bobby R. Bruce
> Room 2235,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
>
>
>
> web: https://www.bobbybruce.net
>
>
>
>
>
> On Thu, Oct 8, 2020 at 4:10 PM Poremba, Matthew 
> wrote:
>
> [AMD Public Use]
>
>
>
> Hi Bobby,
>
>
>
>
>
> 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.
>
>
>
>
>
> -Matt
>
>
>
> *From:* Bobby Bruce via gem5-dev 
> *Sent:* Thursday, October 8, 2020 3:19 PM
> *To:* gem5 Developer List 
> *Cc:* Bobby Bruce 
> *Subject:* [gem5-dev] Re: Build failed in Jenkins: Nightly #91
>
>
>
> [CAUTION: External Email]
>
> Hey all,
>
>
>
> The source of this issue is that our Jenkin's server was using Python2,
> and a commit was merged whi

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

2020-10-13 Thread Giacomo Travaglini via gem5-dev

Forgot to mention: I am choosing the latter

Giacomo

From: Giacomo Travaglini
Sent: 13 October 2020 16:40
To: gem5 Developer List ; Poremba, Matthew 

Cc: Jieming Yin 
Subject: RE: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

Hi all,

I had the same issue. The problem in my case was in scons, which was selecting 
python2 when building gem5 disregarding my python3 virtualenv

$less `which scons`
#! /usr/bin/python

And /usr/bin/python was linked to python2.7.

So the available solutions are:

  *   Installing a newer scons version with

#!/usr/bin/env python

  *   changing the symbolic link,
  *   modify the shebang of the preinstalled one,
  *   CL selection of the scons interpreter:
alias scons=python `which scons`

Kind Regards

Giacomo

From: Jieming Yin via gem5-dev mailto:gem5-dev@gem5.org>>
Sent: 09 October 2020 02:43
To: Poremba, Matthew mailto:matthew.pore...@amd.com>>
Cc: gem5 Developer List mailto:gem5-dev@gem5.org>>; Jieming 
Yin mailto:bjm...@gmail.com>>
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

Hi Matt,

My workaround is to do it in a python2 manner:

class SEWorkload(Workload):
type = 'SEWorkload'
__metaclass__ = SEWorkloadMeta

I have the same syntax error because I am running the gem5-gcn docker, and I 
have both python2 and python3 installed. But I don't really know how to fix it, 
it seems python2 is used sometimes.

Jieming

On Thu, Oct 8, 2020 at 7:43 PM Bobby Bruce via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
Hey Matt,

Before the nightly tests were run on Jenkins server which was an Ubuntu 18.04 
machine with Python2.

The nightly tests will now run using our Ubuntu 20.04 docker image: 
gcr.io/gem5-test/ubuntu-20.04_all-dependencies<http://gcr.io/gem5-test/ubuntu-20.04_all-dependencies>
 (Dockerfile source: 
https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile).

So, to compile gem5.opt for the ARM ISA, the nightly will use:

```
docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm 
gcr.io/gem5-test/ubuntu-20.04_all-dependencies<http://gcr.io/gem5-test/ubuntu-20.04_all-dependencies>
 scons build/ARM/gem5.opt
```

I'm going to guess you probably still have Python2 somewhere on your machine 
and it's using it during the compilation. I'll setup some tests on my end and 
see if I can recreate this problem. I _think_ right now we only test in 
environments that either have only Python2 or have only Python3, so we should 
probably have some tests to check what happens if someone has both.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net

On Thu, Oct 8, 2020 at 4:10 PM Poremba, Matthew 
mailto:matthew.pore...@amd.com>> wrote:

[AMD Public Use]

Hi Bobby,

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.

-Matt

From: Bobby Bruce via gem5-dev mailto:gem5-dev@gem5.org>>
Sent: Thursday, October 8, 2020 3:19 PM
To: gem5 Developer List mailto:gem5-dev@gem5.org>>
Cc: Bobby Bruce mailto:bbr...@ucdavis.edu>>
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

[CAUTION: External Email]
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<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgem5-review.googlesource.com%2Fc%2Fpublic%2Fgem5%2F%2B%2F33900=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081348428=Ux12iZ%2Bj0umYNRs7KDlkuZcHZEpE3tOvRlV6Tsyy%2B3Y%3D=0>

We are going to drop support for Python2 in the next release, so I've upgraded 
our nightly tests to use Python3. They should pass tonight.

I'm unsure if this has been officially announced in any capacity, but as we're 
dropping Python2 support in the next release, you may submit patches containing 
Python3 code without any requirement of providing some Python2 backwards 
compatibility.

The compilation tests also failed as we're using Python2 there as well. I'm 
currently working on a fix for these tests.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: 
https://www.bobbybruce.net<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bobbybruce.net%2F=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081358426=K7p4NxR5oOe5EwzEP4mkuGWTqZOGyDMn%2BzP8J5MPSzk%3D=0>

On Wed, Oct 7, 2020 at 11:49 PM jenkins-no-reply--- via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
See

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

2020-10-13 Thread Giacomo Travaglini via gem5-dev

Hi all,

I had the same issue. The problem in my case was in scons, which was selecting 
python2 when building gem5 disregarding my python3 virtualenv

$less `which scons`
#! /usr/bin/python

And /usr/bin/python was linked to python2.7.

So the available solutions are:


  *   Installing a newer scons version with

#!/usr/bin/env python


  *   changing the symbolic link,
  *   modify the shebang of the preinstalled one,
  *   CL selection of the scons interpreter:

alias scons=python `which scons`

Kind Regards

Giacomo

From: Jieming Yin via gem5-dev 
Sent: 09 October 2020 02:43
To: Poremba, Matthew 
Cc: gem5 Developer List ; Jieming Yin 
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

Hi Matt,

My workaround is to do it in a python2 manner:

class SEWorkload(Workload):
type = 'SEWorkload'
__metaclass__ = SEWorkloadMeta

I have the same syntax error because I am running the gem5-gcn docker, and I 
have both python2 and python3 installed. But I don't really know how to fix it, 
it seems python2 is used sometimes.

Jieming

On Thu, Oct 8, 2020 at 7:43 PM Bobby Bruce via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
Hey Matt,

Before the nightly tests were run on Jenkins server which was an Ubuntu 18.04 
machine with Python2.

The nightly tests will now run using our Ubuntu 20.04 docker image: 
gcr.io/gem5-test/ubuntu-20.04_all-dependencies<http://gcr.io/gem5-test/ubuntu-20.04_all-dependencies>
 (Dockerfile source: 
https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile).

So, to compile gem5.opt for the ARM ISA, the nightly will use:

```
docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm 
gcr.io/gem5-test/ubuntu-20.04_all-dependencies<http://gcr.io/gem5-test/ubuntu-20.04_all-dependencies>
 scons build/ARM/gem5.opt
```

I'm going to guess you probably still have Python2 somewhere on your machine 
and it's using it during the compilation. I'll setup some tests on my end and 
see if I can recreate this problem. I _think_ right now we only test in 
environments that either have only Python2 or have only Python3, so we should 
probably have some tests to check what happens if someone has both.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Thu, Oct 8, 2020 at 4:10 PM Poremba, Matthew 
mailto:matthew.pore...@amd.com>> wrote:

[AMD Public Use]

Hi Bobby,


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.


-Matt

From: Bobby Bruce via gem5-dev mailto:gem5-dev@gem5.org>>
Sent: Thursday, October 8, 2020 3:19 PM
To: gem5 Developer List mailto:gem5-dev@gem5.org>>
Cc: Bobby Bruce mailto:bbr...@ucdavis.edu>>
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

[CAUTION: External Email]
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<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgem5-review.googlesource.com%2Fc%2Fpublic%2Fgem5%2F%2B%2F33900=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081348428=Ux12iZ%2Bj0umYNRs7KDlkuZcHZEpE3tOvRlV6Tsyy%2B3Y%3D=0>

We are going to drop support for Python2 in the next release, so I've upgraded 
our nightly tests to use Python3. They should pass tonight.

I'm unsure if this has been officially announced in any capacity, but as we're 
dropping Python2 support in the next release, you may submit patches containing 
Python3 code without any requirement of providing some Python2 backwards 
compatibility.

The compilation tests also failed as we're using Python2 there as well. I'm 
currently working on a fix for these tests.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: 
https://www.bobbybruce.net<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bobbybruce.net%2F=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081358426=K7p4NxR5oOe5EwzEP4mkuGWTqZOGyDMn%2BzP8J5MPSzk%3D=0>


On Wed, Oct 7, 2020 at 11:49 PM jenkins-no-reply--- via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
See 
<https://jenkins.gem5.org/job/Nightly/91/display/redirect?page=changes<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins.gem5.org%2Fjob%2FNightly%2F91%2Fdisplay%2Fredirect%3Fpage%3Dchanges=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081368416=UA%2BkCy45Ggv1hLV

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

2020-10-08 Thread Jieming Yin via gem5-dev

Hi Matt,

My workaround is to do it in a python2 manner:

class SEWorkload(Workload):
type = 'SEWorkload'
__metaclass__ = SEWorkloadMeta

I have the same syntax error because I am running the gem5-gcn docker, and
I have both python2 and python3 installed. But I don't really know how to
fix it, it seems python2 is used sometimes.

Jieming

On Thu, Oct 8, 2020 at 7:43 PM Bobby Bruce via gem5-dev 
wrote:

> Hey Matt,
>
> Before the nightly tests were run on Jenkins server which was an Ubuntu
> 18.04 machine with Python2.
>
> The nightly tests will now run using our Ubuntu 20.04 docker image:
> gcr.io/gem5-test/ubuntu-20.04_all-dependencies (Dockerfile source:
> https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile).
>
>
> So, to compile gem5.opt for the ARM ISA, the nightly will use:
>
> ```
> docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm
> gcr.io/gem5-test/ubuntu-20.04_all-dependencies scons build/ARM/gem5.opt
> ```
>
> I'm going to guess you probably still have Python2 somewhere on your
> machine and it's using it during the compilation. I'll setup some tests on
> my end and see if I can recreate this problem. I _think_ right now we only
> test in environments that either have only Python2 or have only Python3, so
> we should probably have some tests to check what happens if someone has
> both.
>
> Kind regards,
> Bobby
> --
> Dr. Bobby R. Bruce
> Room 2235,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
>
> web: https://www.bobbybruce.net
>
>
> On Thu, Oct 8, 2020 at 4:10 PM Poremba, Matthew 
> wrote:
>
>> [AMD Public Use]
>>
>>
>>
>> Hi Bobby,
>>
>>
>>
>>
>>
>> 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.
>>
>>
>>
>>
>>
>> -Matt
>>
>>
>>
>> *From:* Bobby Bruce via gem5-dev 
>> *Sent:* Thursday, October 8, 2020 3:19 PM
>> *To:* gem5 Developer List 
>> *Cc:* Bobby Bruce 
>> *Subject:* [gem5-dev] Re: Build failed in Jenkins: Nightly #91
>>
>>
>>
>> [CAUTION: External Email]
>>
>> 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
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgem5-review.googlesource.com%2Fc%2Fpublic%2Fgem5%2F%2B%2F33900=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081348428=Ux12iZ%2Bj0umYNRs7KDlkuZcHZEpE3tOvRlV6Tsyy%2B3Y%3D=0>
>>
>>
>>
>> We are going to drop support for Python2 in the next release, so I've
>> upgraded our nightly tests to use Python3. They should pass tonight.
>>
>>
>>
>> I'm unsure if this has been officially announced in any capacity, but as
>> we're dropping Python2 support in the next release, you may submit patches
>> containing Python3 code without any requirement of providing some Python2
>> backwards compatibility.
>>
>>
>>
>> The compilation tests also failed as we're using Python2 there as well.
>> I'm currently working on a fix for these tests.
>>
>>
>>
>> Kind regards,
>>
>> Bobby
>>
>> --
>>
>> Dr. Bobby R. Bruce
>> Room 2235,
>> Kemper Hall, UC Davis
>> Davis,
>> CA, 95616
>>
>>
>>
>> web: https://www.bobbybruce.net
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bobbybruce.net%2F=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081358426=K7p4NxR5oOe5EwzEP4mkuGWTqZOGyDMn%2BzP8J5MPSzk%3D=0>
>>
>>
>>
>>
>>
>> On Wed, Oct 7, 2020 at 11:49 PM jenkins-no-reply--- via gem5-dev <
>> gem5-dev@gem5.org> wrote:
>>
>> See <
>> https://jenkins.gem5.org/job/Nightly/91/display/redirect?page=changes
>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins.gem5.org%2Fjob%2FNightly%2F91%2Fdisplay%2Fredirect%3Fpage%3Dchanges=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081368416=UA%2BkCy45Ggv1hLVQ2vgtKisVgQxnkVaLL8NPNSSaqfY%3D=0>
>> >
>>

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

2020-10-08 Thread Bobby Bruce via gem5-dev

Hey Matt,

Before the nightly tests were run on Jenkins server which was an Ubuntu
18.04 machine with Python2.

The nightly tests will now run using our Ubuntu 20.04 docker image:
gcr.io/gem5-test/ubuntu-20.04_all-dependencies (Dockerfile source:
https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile).


So, to compile gem5.opt for the ARM ISA, the nightly will use:

```
docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm
gcr.io/gem5-test/ubuntu-20.04_all-dependencies scons build/ARM/gem5.opt
```

I'm going to guess you probably still have Python2 somewhere on your
machine and it's using it during the compilation. I'll setup some tests on
my end and see if I can recreate this problem. I _think_ right now we only
test in environments that either have only Python2 or have only Python3, so
we should probably have some tests to check what happens if someone has
both.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Thu, Oct 8, 2020 at 4:10 PM Poremba, Matthew 
wrote:

> [AMD Public Use]
>
>
>
> Hi Bobby,
>
>
>
>
>
> 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.
>
>
>
>
>
> -Matt
>
>
>
> *From:* Bobby Bruce via gem5-dev 
> *Sent:* Thursday, October 8, 2020 3:19 PM
> *To:* gem5 Developer List 
> *Cc:* Bobby Bruce 
> *Subject:* [gem5-dev] Re: Build failed in Jenkins: Nightly #91
>
>
>
> [CAUTION: External Email]
>
> 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
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgem5-review.googlesource.com%2Fc%2Fpublic%2Fgem5%2F%2B%2F33900=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081348428=Ux12iZ%2Bj0umYNRs7KDlkuZcHZEpE3tOvRlV6Tsyy%2B3Y%3D=0>
>
>
>
> We are going to drop support for Python2 in the next release, so I've
> upgraded our nightly tests to use Python3. They should pass tonight.
>
>
>
> I'm unsure if this has been officially announced in any capacity, but as
> we're dropping Python2 support in the next release, you may submit patches
> containing Python3 code without any requirement of providing some Python2
> backwards compatibility.
>
>
>
> The compilation tests also failed as we're using Python2 there as well.
> I'm currently working on a fix for these tests.
>
>
>
> Kind regards,
>
> Bobby
>
> --
>
> Dr. Bobby R. Bruce
> Room 2235,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
>
>
>
> web: https://www.bobbybruce.net
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bobbybruce.net%2F=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081358426=K7p4NxR5oOe5EwzEP4mkuGWTqZOGyDMn%2BzP8J5MPSzk%3D=0>
>
>
>
>
>
> On Wed, Oct 7, 2020 at 11:49 PM jenkins-no-reply--- via gem5-dev <
> gem5-dev@gem5.org> wrote:
>
> See <https://jenkins.gem5.org/job/Nightly/91/display/redirect?page=changes
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins.gem5.org%2Fjob%2FNightly%2F91%2Fdisplay%2Fredirect%3Fpage%3Dchanges=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081368416=UA%2BkCy45Ggv1hLVQ2vgtKisVgQxnkVaLL8NPNSSaqfY%3D=0>
> >
>
> Changes:
>
> [giacomo.travaglini] arch: Add generic BaseMMU
>
> [giacomo.travaglini] fastmodel: Add IrisMMU model
>
> [gabeblack] sim: Add a mechanism for finding an compatible SE workload.
>
> [gabeblack] sparc: Clean up some code in base.isa.
>
> [gabeblack] sparc: Simplify the IntOp format slightly.
>
>
> --
> [...truncated 47.05 KB...]
>  [SO PyBind] QoSMemSinkInterface ->
> NULL/python/_m5/param_QoSMemSinkInterface.cc
>  [ CXX] NULL/python/_m5/param_QoSMemSinkInterface.cc -> .o
>  [SO PyBind] QoSPolicy -> NULL/python/_m5/param_QoSPolicy.cc
>  [ CXX] NULL/python/_m5/param_QoSPolicy.cc -> .o
>  [SO PyBind] QoSPropFairPolicy ->
> NULL/python/_m5/param_QoSPropFairPolicy.cc
>  [SO PARAM] QoSPropFairPolicy -> NULL/params/QoSPropFairPolicy.hh
>  [ CXX] NULL/python/_m5/param_QoSPropFairPolicy.cc -> .o
&g

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

2020-10-08 Thread Poremba, Matthew via gem5-dev

[AMD Public Use]

Hi Bobby,


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.


-Matt

From: Bobby Bruce via gem5-dev 
Sent: Thursday, October 8, 2020 3:19 PM
To: gem5 Developer List 
Cc: Bobby Bruce 
Subject: [gem5-dev] Re: Build failed in Jenkins: Nightly #91

[CAUTION: External Email]
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<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgem5-review.googlesource.com%2Fc%2Fpublic%2Fgem5%2F%2B%2F33900=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081348428=Ux12iZ%2Bj0umYNRs7KDlkuZcHZEpE3tOvRlV6Tsyy%2B3Y%3D=0>

We are going to drop support for Python2 in the next release, so I've upgraded 
our nightly tests to use Python3. They should pass tonight.

I'm unsure if this has been officially announced in any capacity, but as we're 
dropping Python2 support in the next release, you may submit patches containing 
Python3 code without any requirement of providing some Python2 backwards 
compatibility.

The compilation tests also failed as we're using Python2 there as well. I'm 
currently working on a fix for these tests.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: 
https://www.bobbybruce.net<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bobbybruce.net%2F=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081358426=K7p4NxR5oOe5EwzEP4mkuGWTqZOGyDMn%2BzP8J5MPSzk%3D=0>


On Wed, Oct 7, 2020 at 11:49 PM jenkins-no-reply--- via gem5-dev 
mailto:gem5-dev@gem5.org>> wrote:
See 
<https://jenkins.gem5.org/job/Nightly/91/display/redirect?page=changes<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins.gem5.org%2Fjob%2FNightly%2F91%2Fdisplay%2Fredirect%3Fpage%3Dchanges=02%7C01%7Cmatthew.poremba%40amd.com%7Cfbadcb5540864f21620c08d86bd84e41%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637377924081368416=UA%2BkCy45Ggv1hLVQ2vgtKisVgQxnkVaLL8NPNSSaqfY%3D=0>>

Changes:

[giacomo.travaglini] arch: Add generic BaseMMU

[giacomo.travaglini] fastmodel: Add IrisMMU model

[gabeblack] sim: Add a mechanism for finding an compatible SE workload.

[gabeblack] sparc: Clean up some code in base.isa.

[gabeblack] sparc: Simplify the IntOp format slightly.


--
[...truncated 47.05 KB...]
 [SO PyBind] QoSMemSinkInterface -> NULL/python/_m5/param_QoSMemSinkInterface.cc
 [ CXX] NULL/python/_m5/param_QoSMemSinkInterface.cc -> .o
 [SO PyBind] QoSPolicy -> NULL/python/_m5/param_QoSPolicy.cc
 [ CXX] NULL/python/_m5/param_QoSPolicy.cc -> .o
 [SO PyBind] QoSPropFairPolicy -> NULL/python/_m5/param_QoSPropFairPolicy.cc
 [SO PARAM] QoSPropFairPolicy -> NULL/params/QoSPropFairPolicy.hh
 [ CXX] NULL/python/_m5/param_QoSPropFairPolicy.cc -> .o
 [SO PyBind] QoSTurnaroundPolicy -> NULL/python/_m5/param_QoSTurnaroundPolicy.cc
 [ CXX] NULL/python/_m5/param_QoSTurnaroundPolicy.cc -> .o
 [SO PyBind] QoSTurnaroundPolicyIdeal -> 
NULL/python/_m5/param_QoSTurnaroundPolicyIdeal.cc
 [SO PARAM] QoSTurnaroundPolicyIdeal -> NULL/params/QoSTurnaroundPolicyIdeal.hh
 [ CXX] NULL/python/_m5/param_QoSTurnaroundPolicyIdeal.cc -> .o
 [SO PyBind] QueuedPrefetcher -> NULL/python/_m5/param_QueuedPrefetcher.cc
 [ CXX] NULL/python/_m5/param_QueuedPrefetcher.cc -> .o
 [SO PyBind] RandomRP -> NULL/python/_m5/param_RandomRP.cc
 [SO PARAM] RandomRP -> NULL/params/RandomRP.hh
 [ CXX] NULL/python/_m5/param_RandomRP.cc -> .o
 [SO PyBind] RangeAddrMapper -> NULL/python/_m5/param_RangeAddrMapper.cc
 [ CXX] NULL/python/_m5/param_RangeAddrMapper.cc -> .o
 [SO PyBind] RedirectPath -> NULL/python/_m5/param_RedirectPath.cc
 [ CXX] NULL/python/_m5/param_RedirectPath.cc -> .o
 [SO PyBind] RepeatedQwordsCompressor -> 
NULL/python/_m5/param_RepeatedQwordsCompressor.cc
 [SO PARAM] RepeatedQwordsCompressor -> NULL/params/RepeatedQwordsCompressor.hh
 [ CXX] NULL/python/_m5/param_RepeatedQwordsCompressor.cc -> .o
 [SO PyBind] Root -> NULL/python/_m5/param_Root.cc
 [SO PARAM] Root -> NULL/params/Root.hh
 [ CXX] NULL/python/_m5/param_Root.cc -> .o
 [SO PyBind] RubyCache -> NULL/python/_m5/param_RubyCache.cc
 [ CXX] NULL/python/_m5/param_RubyCache.cc -> .o
 [SO PyBind] RubyController -> NULL/python/_m5/param_RubyController.cc
 [ CXX] NULL/python/_m5/param_RubyController.cc -> .o
 [SO PyBind] RubyDirectedTester -> NULL/python/

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

2020-10-08 Thread Bobby Bruce via gem5-dev

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 nightly tests to use Python3. They should pass tonight.

I'm unsure if this has been officially announced in any capacity, but as
we're dropping Python2 support in the next release, you may submit patches
containing Python3 code without any requirement of providing some Python2
backwards compatibility.

The compilation tests also failed as we're using Python2 there as well. I'm
currently working on a fix for these tests.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Wed, Oct 7, 2020 at 11:49 PM jenkins-no-reply--- via gem5-dev <
gem5-dev@gem5.org> wrote:

> See  >
>
> Changes:
>
> [giacomo.travaglini] arch: Add generic BaseMMU
>
> [giacomo.travaglini] fastmodel: Add IrisMMU model
>
> [gabeblack] sim: Add a mechanism for finding an compatible SE workload.
>
> [gabeblack] sparc: Clean up some code in base.isa.
>
> [gabeblack] sparc: Simplify the IntOp format slightly.
>
>
> --
> [...truncated 47.05 KB...]
>  [SO PyBind] QoSMemSinkInterface ->
> NULL/python/_m5/param_QoSMemSinkInterface.cc
>  [ CXX] NULL/python/_m5/param_QoSMemSinkInterface.cc -> .o
>  [SO PyBind] QoSPolicy -> NULL/python/_m5/param_QoSPolicy.cc
>  [ CXX] NULL/python/_m5/param_QoSPolicy.cc -> .o
>  [SO PyBind] QoSPropFairPolicy ->
> NULL/python/_m5/param_QoSPropFairPolicy.cc
>  [SO PARAM] QoSPropFairPolicy -> NULL/params/QoSPropFairPolicy.hh
>  [ CXX] NULL/python/_m5/param_QoSPropFairPolicy.cc -> .o
>  [SO PyBind] QoSTurnaroundPolicy ->
> NULL/python/_m5/param_QoSTurnaroundPolicy.cc
>  [ CXX] NULL/python/_m5/param_QoSTurnaroundPolicy.cc -> .o
>  [SO PyBind] QoSTurnaroundPolicyIdeal ->
> NULL/python/_m5/param_QoSTurnaroundPolicyIdeal.cc
>  [SO PARAM] QoSTurnaroundPolicyIdeal ->
> NULL/params/QoSTurnaroundPolicyIdeal.hh
>  [ CXX] NULL/python/_m5/param_QoSTurnaroundPolicyIdeal.cc -> .o
>  [SO PyBind] QueuedPrefetcher -> NULL/python/_m5/param_QueuedPrefetcher.cc
>  [ CXX] NULL/python/_m5/param_QueuedPrefetcher.cc -> .o
>  [SO PyBind] RandomRP -> NULL/python/_m5/param_RandomRP.cc
>  [SO PARAM] RandomRP -> NULL/params/RandomRP.hh
>  [ CXX] NULL/python/_m5/param_RandomRP.cc -> .o
>  [SO PyBind] RangeAddrMapper -> NULL/python/_m5/param_RangeAddrMapper.cc
>  [ CXX] NULL/python/_m5/param_RangeAddrMapper.cc -> .o
>  [SO PyBind] RedirectPath -> NULL/python/_m5/param_RedirectPath.cc
>  [ CXX] NULL/python/_m5/param_RedirectPath.cc -> .o
>  [SO PyBind] RepeatedQwordsCompressor ->
> NULL/python/_m5/param_RepeatedQwordsCompressor.cc
>  [SO PARAM] RepeatedQwordsCompressor ->
> NULL/params/RepeatedQwordsCompressor.hh
>  [ CXX] NULL/python/_m5/param_RepeatedQwordsCompressor.cc -> .o
>  [SO PyBind] Root -> NULL/python/_m5/param_Root.cc
>  [SO PARAM] Root -> NULL/params/Root.hh
>  [ CXX] NULL/python/_m5/param_Root.cc -> .o
>  [SO PyBind] RubyCache -> NULL/python/_m5/param_RubyCache.cc
>  [ CXX] NULL/python/_m5/param_RubyCache.cc -> .o
>  [SO PyBind] RubyController -> NULL/python/_m5/param_RubyController.cc
>  [ CXX] NULL/python/_m5/param_RubyController.cc -> .o
>  [SO PyBind] RubyDirectedTester ->
> NULL/python/_m5/param_RubyDirectedTester.cc
>  [ CXX] NULL/python/_m5/param_RubyDirectedTester.cc -> .o
>  [SO PyBind] RubyDirectoryMemory ->
> NULL/python/_m5/param_RubyDirectoryMemory.cc
>  [ CXX] NULL/python/_m5/param_RubyDirectoryMemory.cc -> .o
>  [SO PyBind] RubyHTMSequencer -> NULL/python/_m5/param_RubyHTMSequencer.cc
>  [ CXX] NULL/python/_m5/param_RubyHTMSequencer.cc -> .o
>  [SO PyBind] RubyNetwork -> NULL/python/_m5/param_RubyNetwork.cc
>  [ CXX] NULL/python/_m5/param_RubyNetwork.cc -> .o
>  [SO PyBind] RubyPort -> NULL/python/_m5/param_RubyPort.cc
>  [ CXX] NULL/python/_m5/param_RubyPort.cc -> .o
>  [SO PyBind] RubyPortProxy -> NULL/python/_m5/param_RubyPortProxy.cc
>  [SO PARAM] RubyPortProxy -> NULL/params/RubyPortProxy.hh
>  [ CXX] NULL/python/_m5/param_RubyPortProxy.cc -> .o
>  [SO PyBind] RubyPrefetcher -> NULL/python/_m5/param_RubyPrefetcher.cc
>  [ CXX] NULL/python/_m5/param_RubyPrefetcher.cc -> .o
>  [SO PyBind] RubySequencer -> NULL/python/_m5/param_RubySequencer.cc
>  [ CXX] NULL/python/_m5/param_RubySequencer.cc -> .o
>  [SO PyBind] RubySystem -> NULL/python/_m5/param_RubySystem.cc
>  [ CXX] NULL/python/_m5/param_RubySystem.cc -> .o
>  [SO PyBind] RubyTester -> NULL/python/_m5/param_RubyTester.cc
>  [SO PARAM] RubyTester -> NULL/params/RubyTester.hh
>  [ CXX] NULL/python/_m5/param_RubyTester.cc -> .o
>  [SO PyBind] RubyWireBuffer -> NULL/python/_m5/param_RubyWireBuffer.cc

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

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

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

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

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

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

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

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

8 matches

Site Navigation

Mail list logo

Footer information