All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yash Shinde" <Yash.Shinde@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0
Date: Wed, 03 Jul 2024 22:49:09 -0700	[thread overview]
Message-ID: <31491.1720072149300569224@lists.openembedded.org> (raw)
In-Reply-To: <e196c7761406a0fd8a7fcd38fa198cc60dca271e.camel@linuxfoundation.org>

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

I thought we skipped mips and ppc targets for rust oe - selftests , didn ' t we ?

I tested for the targets mentioned in, https://lists.openembedded.org/g/openembedded-core/message/201295 ( https://lists.openembedded.org/g/openembedded-core/message/201295 )

Please let me know which targets are tested for rust oe-selftests in AB?

Regards,

Yash

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

WARNING: multiple messages have this Message-ID (diff)
From: "Yash Shinde" <Yash.Shinde@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0
Date: Wed, 03 Jul 2024 22:58:45 -0700	[thread overview]
Message-ID: <31491.1720072149300569224@lists.openembedded.org> (raw)
Message-ID: <20240704055845.gNkZoa3Pyeah6iUO_f7oS5s4ekIj_8s3pDcH-euS1EU@z> (raw)
In-Reply-To: <e196c7761406a0fd8a7fcd38fa198cc60dca271e.camel@linuxfoundation.org>

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

https://valkyrie.yoctoproject.org/#/builders/49/builds/55/steps/12/logs/stdio ( https://valkyrie.yoctoproject.org/#/builders/49/builds/55/steps/12/logs/stdio )

The above failure for rust v1.77.2 is on ppc target.

I thought we skipped mips and ppc targets for rust oe - selftests , didn ' t we ?

I tested for the targets mentioned in, https://lists.openembedded.org/g/openembedded-core/message/201295 ( https://lists.openembedded.org/g/openembedded-core/message/201295 )

Please let me know which targets are tested for rust oe-selftests in AB?

Regards,

Yash

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

WARNING: multiple messages have this Message-ID (diff)
From: "Yash Shinde" <Yash.Shinde@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0
Date: Wed, 03 Jul 2024 22:58:56 -0700	[thread overview]
Message-ID: <31491.1720072149300569224@lists.openembedded.org> (raw)
Message-ID: <20240704055856.MO7Eo6KSYN7EU7wyfsjR9wySq1YCXGkqy9P6yyhphHY@z> (raw)
In-Reply-To: <e196c7761406a0fd8a7fcd38fa198cc60dca271e.camel@linuxfoundation.org>

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

https://valkyrie.yoctoproject.org/#/builders/49/builds/55/steps/12/logs/stdio ( https://valkyrie.yoctoproject.org/#/builders/49/builds/55/steps/12/logs/stdio )

The above failure is for rust v1.77.2 is on ppc target.

I thought we skipped mips and ppc targets for rust oe - selftests , didn ' t we ?

I tested for the targets mentioned in, https://lists.openembedded.org/g/openembedded-core/message/201295 ( https://lists.openembedded.org/g/openembedded-core/message/201295 )

Please let me know which targets are tested for rust oe-selftests in AB?

Regards,

Yash

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

  parent reply	other threads:[~2024-07-04  5:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  9:26 [PATCH 1/9] rust: Oe-selftest fixes for rust v1.76 Yash.Shinde
2024-07-01  9:26 ` [PATCH 2/9] rust: Upgrade 1.75.0->1.76.0 Yash.Shinde
2024-07-01  9:50   ` Alexander Kanavin
2024-07-01  9:56     ` Sundeep KOKKONDA
2024-07-01 11:36       ` [OE-core] " Richard Purdie
2024-07-01  9:26 ` [PATCH 3/9] rust: reproducibility issue fix with v1.76 Yash.Shinde
2024-07-01  9:26 ` [PATCH 4/9] rust: Oe-selftest changes for rust v1.77 Yash.Shinde
2024-07-01  9:26 ` [PATCH 5/9] rust: Upgrade 1.76.0->1.77.0 Yash.Shinde
2024-07-01  9:26 ` [PATCH 6/9] rust: Upgrade 1.77.0->1.77.1 Yash.Shinde
2024-07-01  9:26 ` [PATCH 7/9] rust: Upgrade 1.77.1->1.77.2 Yash.Shinde
2024-07-01  9:26 ` [PATCH 8/9] rust: Oe-selftest changes for rust v1.78 Yash.Shinde
2024-07-01  9:26 ` [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0 Yash.Shinde
2024-07-01  9:30   ` Yash Shinde
2024-07-01 16:47   ` [OE-core] " Richard Purdie
2024-07-02 12:36     ` Sundeep KOKKONDA
     [not found]   ` <17DE24B76261B84E.14163@lists.openembedded.org>
2024-07-02  8:59     ` [OE-core] " Richard Purdie
2024-07-02 12:37       ` Sundeep KOKKONDA
2024-07-02 14:12         ` [OE-core] " Richard Purdie
2024-07-02 15:08           ` Ross Burton
2024-07-02 17:37             ` Sundeep KOKKONDA
2024-07-03  8:14               ` [OE-core] " Richard Purdie
2024-07-03  8:19                 ` Sundeep KOKKONDA
2024-07-04  5:49                 ` Yash Shinde [this message]
2024-07-04  5:58                   ` Yash Shinde
2024-07-04  5:58                   ` Yash Shinde
     [not found]                   ` <Groupsio.2.31491.1720072149300569224@lists.openembedded.org>
2024-07-04 10:36                     ` [OE-core] " Alexander Kanavin
     [not found]                     ` <17DEFC31DA378080.5810@lists.openembedded.org>
2024-07-04 11:22                       ` Alexander Kanavin
2024-07-04 11:44                         ` Yash Shinde
2024-07-04 11:53                           ` Ross Burton
2024-07-01  9:48 ` [OE-core] [PATCH 1/9] rust: Oe-selftest fixes for rust v1.76 Alex Kiernan

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=31491.1720072149300569224@lists.openembedded.org \
    --to=yash.shinde@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.