Re: [SPDK] test system OS & tool versions

Re: [SPDK] test system OS & tool versions

[Rodriguez, Edwin]

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

Another useful enhancement would be a notice that all tests suceeded.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: "Luse, Paul E" <paul.e.luse(a)intel.com>
Date: 3/19/18 3:45 PM (GMT-05:00)
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] test system OS & tool versions

Cool, thanks Daniel & Ed.  Yeah, I just saw the cc_version in a log.  I’ll submit a patch shortly to add some more info and see about making it a little easier to spot in the log

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Rodriguez, Edwin
Sent: Monday, March 19, 2018 9:58 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] test system OS & tool versions

How about adding ‘lsb_release -a’ ?

Ed R

From: SPDK <spdk-bounces(a)lists.01.org> on behalf of "Verkamp, Daniel" <daniel.verkamp(a)intel.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, March 19, 2018 at 12:47 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] test system OS & tool versions

Hi Paul,

We already have the C compiler version in build.log for each machine – search for ‘make cc_version’.  It could be useful to add uname -a as well to round out the system information.

Thanks,
-- Daniel

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Sunday, March 18, 2018 9:33 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] test system OS & tool versions

A few folks have asked for a convenient way to get this info.  What is we just added

uanme –a
gcc –version

to the end of autotest.sh that that you could look at any patch and on a per machine basis see what was used?  Are there a few other versions we’d want to add and is tacking this onto the log convenient enough?

Other ideas?

Thanks
Paul


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5841 bytes --]

Re: [SPDK] test system OS & tool versions

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]

Cool, thanks Daniel & Ed.  Yeah, I just saw the cc_version in a log.  I’ll submit a patch shortly to add some more info and see about making it a little easier to spot in the log

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Rodriguez, Edwin
Sent: Monday, March 19, 2018 9:58 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] test system OS & tool versions

How about adding ‘lsb_release -a’ ?

Ed R

From: SPDK <spdk-bounces(a)lists.01.org> on behalf of "Verkamp, Daniel" <daniel.verkamp(a)intel.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, March 19, 2018 at 12:47 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] test system OS & tool versions

Hi Paul,

We already have the C compiler version in build.log for each machine – search for ‘make cc_version’.  It could be useful to add uname -a as well to round out the system information.

Thanks,
-- Daniel

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Sunday, March 18, 2018 9:33 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] test system OS & tool versions

A few folks have asked for a convenient way to get this info.  What is we just added

uanme –a
gcc –version

to the end of autotest.sh that that you could look at any patch and on a per machine basis see what was used?  Are there a few other versions we’d want to add and is tacking this onto the log convenient enough?

Other ideas?

Thanks
Paul


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 6564 bytes --]

Re: [SPDK] test system OS & tool versions

[Rodriguez, Edwin]

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

How about adding ‘lsb_release -a’ ?

Ed R

From: SPDK <spdk-bounces(a)lists.01.org> on behalf of "Verkamp, Daniel" <daniel.verkamp(a)intel.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, March 19, 2018 at 12:47 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] test system OS & tool versions

Hi Paul,

We already have the C compiler version in build.log for each machine – search for ‘make cc_version’.  It could be useful to add uname -a as well to round out the system information.

Thanks,
-- Daniel

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Sunday, March 18, 2018 9:33 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] test system OS & tool versions

A few folks have asked for a convenient way to get this info.  What is we just added

uanme –a
gcc –version

to the end of autotest.sh that that you could look at any patch and on a per machine basis see what was used?  Are there a few other versions we’d want to add and is tacking this onto the log convenient enough?

Other ideas?

Thanks
Paul


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 6168 bytes --]

Re: [SPDK] test system OS & tool versions

[Verkamp, Daniel]

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hi Paul,

We already have the C compiler version in build.log for each machine - search for 'make cc_version'.  It could be useful to add uname -a as well to round out the system information.

Thanks,
-- Daniel

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Sunday, March 18, 2018 9:33 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] test system OS & tool versions

A few folks have asked for a convenient way to get this info.  What is we just added

uanme -a
gcc -version

to the end of autotest.sh that that you could look at any patch and on a per machine basis see what was used?  Are there a few other versions we'd want to add and is tacking this onto the log convenient enough?

Other ideas?

Thanks
Paul


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4049 bytes --]

[SPDK] test system OS & tool versions

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

A few folks have asked for a convenient way to get this info.  What is we just added

uanme -a
gcc -version

to the end of autotest.sh that that you could look at any patch and on a per machine basis see what was used?  Are there a few other versions we'd want to add and is tacking this onto the log convenient enough?

Other ideas?

Thanks
Paul

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 2396 bytes --]