All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: imammedo@redhat.com
Cc: yingwen.chen@intel.com, devel@edk2.groups.io,
	phillip.goerl@oracle.com, qemu-devel@nongnu.org,
	alex.williamson@redhat.com, jiewen.yao@intel.com,
	jun.nakajima@intel.com, michael.d.kinney@intel.com,
	pbonzini@redhat.com, boris.ostrovsky@oracle.com,
	rfc@edk2.groups.io, lersek@redhat.com, joao.m.martins@oracle.com
Subject: Re: [Qemu-devel] [edk2-devel] [PATCH 0/2] q35: mch: allow to lock down 128K RAM at default SMBASE address
Date: Tue, 17 Sep 2019 08:24:35 -0700 (PDT)	[thread overview]
Message-ID: <156873387351.17151.5157996315956457380@5dec9699b7de> (raw)
In-Reply-To: <20190917130708.10281-1-imammedo@redhat.com>

Patchew URL: https://patchew.org/QEMU/20190917130708.10281-1-imammedo@redhat.com/



Hi,

This series failed the docker-mingw@fedora build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.

=== TEST SCRIPT BEGIN ===
#! /bin/bash
make docker-image-fedora V=1 NETWORK=1
time make docker-test-mingw@fedora J=14 NETWORK=1
=== TEST SCRIPT END ===

./tests/docker/docker.py --engine auto build qemu:fedora tests/docker/dockerfiles/fedora.docker   --add-current-user  
Image is up to date.
  LD      docker-test-mingw@fedora.mo
cc: fatal error: no input files
compilation terminated.
make: *** [docker-test-mingw@fedora.mo] Error 4



The full log is available at
http://patchew.org/logs/20190917130708.10281-1-imammedo@redhat.com/testing.docker-mingw@fedora/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

      parent reply	other threads:[~2019-09-17 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 13:07 [Qemu-devel] [PATCH 0/2] q35: mch: allow to lock down 128K RAM at default SMBASE address Igor Mammedov
2019-09-17 13:07 ` [Qemu-devel] [PATCH 1/2] q35: implement 128K SMRAM " Igor Mammedov
2019-09-19 17:02   ` Laszlo Ersek
2019-09-20  8:28     ` [edk2-devel] " Igor Mammedov
2019-09-20  9:28       ` Laszlo Ersek
2019-09-23 18:35         ` Laszlo Ersek
2019-09-24 11:19           ` Igor Mammedov
2019-09-30 11:51             ` Laszlo Ersek
2019-09-30 12:36               ` Igor Mammedov
2019-09-30 14:22                 ` Yao, Jiewen
2019-10-01 18:03                   ` Laszlo Ersek
2019-10-04 11:31                     ` Igor Mammedov
2019-10-07  9:44                       ` Laszlo Ersek
2019-09-24 11:47         ` Paolo Bonzini
2019-09-17 13:07 ` [Qemu-devel] [PATCH 2/2] tests: q35: MCH: add default SMBASE SMRAM lock test Igor Mammedov
2019-09-17 15:23 ` [Qemu-devel] [edk2-devel] [PATCH 0/2] q35: mch: allow to lock down 128K RAM at default SMBASE address no-reply
2019-09-17 15:24 ` no-reply [this message]

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=156873387351.17151.5157996315956457380@5dec9699b7de \
    --to=no-reply@patchew.org \
    --cc=alex.williamson@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=devel@edk2.groups.io \
    --cc=imammedo@redhat.com \
    --cc=jiewen.yao@intel.com \
    --cc=joao.m.martins@oracle.com \
    --cc=jun.nakajima@intel.com \
    --cc=lersek@redhat.com \
    --cc=michael.d.kinney@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=phillip.goerl@oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rfc@edk2.groups.io \
    --cc=yingwen.chen@intel.com \
    /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.