public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Sadineni, Harish" <Harish.Sadineni@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] gcc: Oe-selftest failure analysis - allowing multiple ssh sessions
Date: Thu, 18 Apr 2024 04:00:30 -0700	[thread overview]
Message-ID: <9804.1713438030710020860@lists.openembedded.org> (raw)
In-Reply-To: <20240418105051.2559536-2-Harish.Sadineni@windriver.com>

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

Time taken to run gcc testsuite w/o multiple ssh sessions -> 16-18 hrs
Time taken to run gcc testsuite w/ multiple ssh sessions -> 11-12 hrs
There is an improvement of ~30% in execution time.

Thanks,

Harish

[-- Attachment #2: Type: text/html, Size: 1634 bytes --]

  reply	other threads:[~2024-04-18 11:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 10:50 [PATCH 1/2] gcc: Oe-selftest failure analysis - fix for host key verfication & kex exchange identification failures Harish.Sadineni
2024-04-18 10:50 ` [PATCH 2/2] gcc: Oe-selftest failure analysis - allowing multiple ssh sessions Harish.Sadineni
2024-04-18 11:00   ` Sadineni, Harish [this message]
2024-04-18 10:57 ` [PATCH 1/2] gcc: Oe-selftest failure analysis - fix for host key verfication & kex exchange identification failures Sadineni, Harish
2024-04-18 11:07 ` Patchtest results for " patchtest
2024-04-25 12:07 ` [OE-core] " Richard Purdie
2024-04-25 12:35 ` Richard Purdie
2024-07-16 18:20   ` Sadineni, Harish
  -- strict thread matches above, loose matches on Subject: below --
2024-04-18 11:34 [PATCH 1/2] gcc: " Harish.Sadineni
2024-04-18 11:34 ` [PATCH 2/2] gcc: Oe-selftest failure analysis - allowing multiple ssh sessions Harish.Sadineni
2024-04-18 11:40   ` Sadineni, Harish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9804.1713438030710020860@lists.openembedded.org \
    --to=harish.sadineni@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox