Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-19
Date: Mon, 20 Jan 2014 21:35:41 +1300	[thread overview]
Message-ID: <52DCDFDD.3000303@gmail.com> (raw)
In-Reply-To: <20140120073009.9260E101682@stock.ovh.net>

On 20/01/14 20:30, Thomas Petazzoni wrote:
>        sh4 |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/c5791912f3d05c9c93e54e85989b25002aa9085f/
>    powerpc |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/4387ea6ddcda0ec72a3c1b1345a74f604ca9cc9c/
>        arm |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/abaa014eb74a140afb1ef48922f27d2aacd47885/
>    powerpc |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/918834dc396e5898ed902cd194546cd15801882b/
>        sh4 |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/624a11f8c5916336c3ee2a5d618344b80e61d3f8/
>       mips |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/103e7a17f815f77a51172c20f0862d32521b246b/
>    powerpc |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/e78cb0c352a954c10af90a5d55a59957508a9a85/
>       mips |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/059018fccfc5d05fee575143eeb488fead672fcb/
>       i686 |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/ca87135e3aa0b192b313b6782f379c0b622e39ef/
>       i686 |                tcpreplay-4.0.0 | NOK | http://autobuild.buildroot.net/results/c59b8f9d93d77c8b75c02172ff6e6072e8f62228/

I'm feeling kind of bad about the tcpreplay failures that just seem to
be piling up. So far I've not been able to reproduce the issue. I think
the problem is that under some condition the __VA_ARGS__ macro is
unavailable.

Tcpreplay 4.0.2 was released a day or two ago. I know there are a number
of warnings fixes but I'm a little hesitant to update tcpreplay again
without understanding where these failures are coming from.

  parent reply	other threads:[~2014-01-20  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-19 Thomas Petazzoni
2014-01-20  8:17 ` Baruch Siach
2014-01-20  8:35 ` Chris Packham [this message]
2014-01-20 19:25   ` Bernd Kuhls
2014-01-20 21:03     ` Chris Packham
2014-01-20 23:35       ` Chris Packham
2014-01-21 10:35         ` Martin Bark
2014-01-22  2:59           ` Chris Packham

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=52DCDFDD.3000303@gmail.com \
    --to=judge.packham@gmail.com \
    --cc=buildroot@busybox.net \
    /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