similar to: qemu-kvm-ev ppc64le release builds

I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma package on ppc64le (which is actually newer than qemu-kvm-ev currently). Does anyone know what the difference is between these two packages? We currently use qemu-kvm-ev and we've run into this bug [1] which got me wondering if we should be switching to that package on ppc64le. Thanks! [1]

2018-05-10 21:57 GMT+02:00 Lance Albertson <lance at osuosl.org>: > I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma > package on ppc64le (which is actually newer than qemu-kvm-ev currently). > Does anyone know what the difference is between these two packages? We > currently use qemu-kvm-ev and we've run into this bug [1] which got me > wondering

Seems there were a couple of correlated failures that appear to be flakes on this buildbot recently: green: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/13974 red: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/13975 (target-override.c during stage 1, seems to be missing the directory/symlink it just created) red:

Hello, today I updated a CentOS 7.6 ppc64le machine to CentOS 7.7. After reboot to the new kernel (4.18.0-80.7.2.el7.ppc64le) dkms could not build the nvidia-module. Error-message from dkms: Compiler version check failed: The major and minor number of the compiler used to compile the kernel: gcc version 8.3.1 20190311 (Red Hat 8.3.1-3) (GCC) does not match the compiler used here: cc (GCC)

I have created a JamesOConnor centos wiki userid and I would like to create and be able edit a pair of AltArch wiki pages. https://wiki.centos.org/SpecialInterestGroup/AltArch/ppc64le # POWER8 Little Endian https://wiki.centos.org/SpecialInterestGroup/AltArch/ppc64 # POWER7 Big Endian These would be linked to from https://wiki.centos.org/SpecialInterestGroup/AltArch similar to the Arm32,

Well, I am at my wit's end. I have copied over the script and directories for this test case and run it a few million times. First I was running one at a time, then I switched to kicking off 1000 at a time. All the while, the bots continued to run on the same machine. The script never failed even once. I am not sure if this has something to do with Python as part of llvm-lit or what is going

Sure. I didn't use lit or ninja. I simply copied the script produced by lit (/home/buildbots/ppc64le-clang-multistage-test/clang-ppc64le-multistage/stage1/tools/clang/test/Driver/Output/target-override.c.script) into a temporary directory (along with a deep copy of the build directory). I modified the paths in the script to point to the temporary directory. Then I ran the script in a loop. For

This is likely due to a race condition (%T is a shared parent directory). I'll put up a patch to fix it. On Thu, Sep 3, 2020 at 10:00 AM David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Is the machine running any jobs in parallel? Would it be worth trying running lit in the loop, rather than the script? (perhaps lit's doing something interesting) or maybe the

Thanks everyone for this discussion. Turns out that in my effort to make it possible to run multiple instances of this script in parallel, I inadvertently hid the issue. I made each instance use a directory that has $1 appended to the name and the wrapper script provided a unique value with $LINENO. :( MaskRay, thanks for fixing the problem. All the PPC bots are back to green now. On Thu, Sep 3,

Patch extracts MSB/LSB info from /bin/file output and passes it as separate parameret from elf_arch. Then it is sent to impl_file_architecture and checked/ Modified magic_for_file to handle regex changes. Now with tests for file_architecture. Fixes: RHBZ#1211996 Maros Zatko (2): inspector: recognize ppc64 and ppc64le archs (RHBZ#1211996) tests: ppc64 and ppc64le for file_architecture

Hi, My New Year's resolution is to complain (constructively) whenever I get a spurious build failure email from a buildbot. For new or infrequent contributors especially, they can be extremely confusing and unnecessarily alarming. This one below is the first build ever attempted by the builder, so how on earth can it have come up with a meaningful blame list? And in any case, surely we

I think that was maybe the discussion on https://reviews.llvm.org/D78245 On Thu, Sep 3, 2020 at 6:22 PM Robinson, Paul <paul.robinson at sony.com> wrote: > I have a vague memory that libcxx wanted it for something, and claimed it > would be hard to work around not having it. > > Anyone else remember that? I can’t dredge up the details, sorry… > > In any event, a separate

qemu-kvm-ev-2.3.0-31.el7_2.21.1 has been tagged for testing for CentOS Virt SIG and is already in testing repositories. It's now available for x86_64, ppc64le and aarch64. Please help testing and providing feedback, thanks. We plan to move to stable repo around Wednesday next week. ChangeLog since previous release: * Fri Aug 19 2016 Sandro Bonazzola <sbonazzo at redhat.com> -

https://llvm.org/docs/CommandGuide/lit.html already lists %T as "parent directory of %t (not unique, deprecated, do not use)". See also https://reviews.llvm.org/D35396 On Thu, Sep 3, 2020 at 3:37 PM David Blaikie <dblaikie at gmail.com> wrote: > Yeah, I think I'd be up for considering deprecation of %T due to the risk > of race conditions/conflicts between tests. %t

Should be fixed by https://reviews.llvm.org/D87103 Shall we consider deprecating(emitting a warning)/removing %T from lit? lldb, lld/COFF and clang-tools-extra are the three major users of %T. There are a few other %T in other places but there are not too many. We will also investigate whether other projects using lit are using %T. On Thu, Sep 3, 2020 at 11:25 AM David Blaikie <dblaikie at

Patch extracts MSB/LSB info from /bin/file output and passes it as separate parameret from elf_arch. Then it is sent to impl_file_architecture and checked/ Modified magic_for_file to handle regex changes. Now with tests for file_architecture, and error reporting for unknown endianness. Fixes: RHBZ#1211996 Maros Zatko (1): inspector: recognize ppc64 and ppc64le archs (RHBZ#1211996)

Hi, I'm building compiler-rt in a ppc64le machine and it is generating the sanitizers fine but it is not generating the builtin library. I tried to compile it in a x86_64 machine and I got the builtin library generated (libclang_rt.builtins-x86_64.a). Taking a look in a cmake config file from compiler-rt, I saw that ppc64 is not in the supported architecture list to generate the builtin

Hi Bill, The PPC LNT buildbot is randomly failing on LNT because of timeouts. http://lab.llvm.org:8011/builders/clang-ppc64le-linux-lnt I've checked all recent LNT failures and they were spotted on some processes (lua, sqlite3, tramp3d, expandfft, etc), so I doubt this is in any was a real time out due to code-gen issues. I imagine they're all at the edge already and the standard

On Mon, Aug 03, 2020 at 01:45:45PM +0000, Kim-Norman Sahm wrote: > hi, > > i’m running Debian 10 on POWER9 and would like to spawn x86_64 emulated VMs. > The virtual machine is configured to run with 8 vpus but it’s very slow. > On the host you can see that the qemu-system-x86_64 process is using just one core! > > Ppc64le guests are using multi cores, so its looks like an

Hi U can visit the http://iaxclient.sf.net for some opensource underdevelopment softphones. Take Care Obaid Amin Syed >From: Chris Albertson <chrisalbertson90278@yahoo.com> >Reply-To: asterisk-users@lists.digium.com >To: asterisk-users@lists.digium.com >Subject: [Asterisk-Users] Good W2K softphone >Date: Fri, 3 Oct 2003 23:00:13 -0700 (PDT) > > >I haven't