/tmp/REIX file for testing.
** Attachment added: File for testing. Produced on PPC64LE by Avro test code
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+attachment/4229394/+files/REIX.PPC64LE
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Breno,
I have changed the source code of the Avro Python tests in order to save
the temporary file used by the test. I saved it in a file I named
/tmp/REIX . This file contains non-asci data. I gonna attach it to this
bug. Also, I think this file depends on the machine architecture.
About the
Hi Matthias,
We have checked, and there is no 14.10 version yet for PPC64LE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137
Title:
OptionParser on PPC64LE does not split args correctly
To
I've tried to use PDb on Ubuntu/PPC64LE for debugging the issue.
However, with Pdb, the issue disappears...
We have in opts variable the correct value for fields: 'fields': 'first,
last'
$ pdb ../../lang/py/build/scripts/avro cat /tmp/REIX --fields 'first, last'
build/scripts/avro: line
Looking at ./Lib/optparse.py of Python 2.7.6 :
def parse_args(self, args=None, values=None):
stop = self._process_args(largs, rargs, values)
_process_args()
_process_args()
_process_long_opt()
Probably the issue is in :
def _process_long_opt(self, rargs,
Hi Breno
OK. There is a place where to get an install image for Ubuntu 14.10 for PPC64
LE.
Since the PPC64/LE machines I use are managed by another team, it may be
complicated/long to get them agree to install a machine with something
unstable. Anyway, I'll ask if it is possible.
Now, why do
No issue with Python. My mistake.
** Changed in: python2.7 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137
Title:
OptionParser on PPC64LE does not split
I've found the issue. I had changed the python shell in order to add some trace
options and that generated the issue. Removing the change did fix the issue.
And, looking in depth at Avro results, I found that the final result is mixed
with the traces, and that the result is OK.
So, that is my
Public bug reported:
The issue appears on PPC64 LE.
It is OK on (Ubuntu) x86_64.
Version of Python is 2.7.6 on both systems.
The issue is demonstrated while running AVRO Python tests (in lang/py : ant
test).
- On Ubuntu / PPC64 LE :
$ pwd
/lang/py
$ export PYTHONPATH=./build/src
$
In Avro, the issue appears as:
[py-test] ERROR: test_fields (test_script.TestCat)
[py-test]
--
[py-test] Traceback (most recent call last):
[py-test] File
Hi.
I opened this defect in the wrong world. So, I made it invalid and opened
1312623.
Sorry for the confusion.
Tony
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598
Title:
fatal error:
** Attachment added: hs_err_pid26910.log
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096211/+files/hs_err_pid26910.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
$ uname -a
Linux tony1 3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:13 UTC 2014
ppc64le ppc64le ppc64le GNU/Linux
$ apt-cache policy openjdk-7-jre-lib
openjdk-7-jre-lib:
Installed:
Here are4 hs*.log files produced when JVM7 crashed.
** Attachment added: hs_err_pid7832.log
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096210/+files/hs_err_pid7832.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: hs_err_pid8407.log
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096213/+files/hs_err_pid8407.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: hs_err_pid32470.log
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096212/+files/hs_err_pid32470.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: openjdk-7 (Ubuntu)
Assignee: (unassigned) = Tony Reix (tony-reix)
** Changed in: openjdk-7 (Ubuntu)
Status: New = Invalid
** Description changed:
- $ lsb_release -rd
- Description: Ubuntu 14.04 LTS
- Release: 14.04
-
- $ uname -a
- Linux tony1 3.13.0-19-generic
Public bug reported:
Within glibc (2.19 on Ubuntu, but also on 2.17), some long double
routines for PPC64 are wrong: both .c and .S files exist, and .S files
are taken first though they are old and wrong. The bugs appear for some
cases (for ceill(), second double is wrong). The fix is easy:
** Package changed: pcre3 (Ubuntu) = eglibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294588
Title:
glibc: some long double math routines for PPC64 are wrong: patches
To manage
Hu OK. I'll dig that later, and open a defect in Boost world.
Thanks !
Tony
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282140
Title:
core on 64bit arch in spirit ... lex_lexertl2-p3 test
Public bug reported:
Hello
I'm preparing a patch for Boost v1.55 for context coroutine libraries for
Linux on Power PPC64 LITTLE Endian.
The code is the same (using #if) for Boost v1.55 for context coroutine
libraries for Linux on Power PPC64 BIG Endian.
Files :
This is described in comment #12 :
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/comments/12
(However, I've just found that core (error 139) on PPC64/LE also appears on
AMD64: my mistake).
Boost 1.55 on PPC64 shows more and different issues on LE than on BE. However,
same
Revision 86799 of :
./libs/context/src/asm/jump_ppc64_sysv_elf_gas.S
./libs/context/src/asm/make_ppc64_sysv_elf_gas.S
is exactly identical to the version delivered with Boost v1.55 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here are the results of testing Boost 1.55 on Fedora 19 on PPC/BE.
4380 tests
libs/heap/test/pairing_heap_tests.test/gcc-4.8.2/debug/threading-multi/pairing_heap_tests.output
libs/heap/test/mutable_heap_test.test/gcc-4.8.2/debug/threading-multi/mutable_heap_test.output
There are errors specific to Fedora PPC64/BE vs Ubuntu PPC64/LE, and
vice-versa.
Errors specific to Fedora PPC64/BE (none of these errors appears in Ubuntu
AMD64):
* 1 libs/locale/test/test_boundary.test/gcc-4.8.2/debug/test_boundary.output
* 1
There are few PPC assembler files in Boost (v1.55) :
./libs/context/src/asm/jump_ppc64_sysv_elf_gas.S
./libs/context/src/asm/jump_ppc32_sysv_elf_gas.S
./libs/context/src/asm/make_ppc64_sysv_elf_gas.S
./libs/context/src/asm/make_ppc32_sysv_elf_gas.S
And I've not found any PPC assembler code
Public bug reported:
Test :
./boost1.55-1.55.0/bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8/debug/phoenix_v3-on/lex_lexertl2-p3
SegFaults on 64 bits machines (AMD64 and PPC64).
The issue is that :
CharT curr_char_ = (std::numeric_limitsCharT::min)();
returns
Here is the list of v1.55 errors that appear on PPC64LE and not on
Intel64:
- Memory Access Violation:
libs/math/test/test_jacobi.test/gcc-4.8/debug/link-static/test_jacobi.output
- Cores:
libs/log/test/core.test/gcc-4.8/debug/build-no/threading-multi/core
I forgot to talk again about the tests running an infinite loop on
PPC64, that never appear on AMD64:
Here are infinite loops on PPC64-BE (I provide the last trace appearing
on the screen. The blocking test is: test_tr1* that I killed) :
gcc.link
Results for Boost 1.55 on Ubuntu 14.04 on amd64 with gcc 4.8.2 (Ubuntu
4.8.2-15ubuntu3) :
(Linux version 3.13.0-8-generic (buildd@lamiak) (gcc version 4.8.2
(Ubuntu/Linaro 4.8.2-14ubuntu4) ) #27-Ubuntu SMP Fri Feb 7 02:01:37 UTC
2014)
4401 tests
Number of Memory Access Violation: 7
Here is the same report about Boost 1.55 on Ubuntu 14.04 PPC/LE .
4214 tests
libs/math/test/test_jacobi.test/gcc-4.8/debug/link-static/test_jacobi.output
libs/heap/test/d_ary_heap_test.test/gcc-4.8/debug/threading-multi/d_ary_heap_test.output
I now have a Ubuntu-amd64 (x86_64) environment, where I am
building/testing Boost 1.55 and then 1.54.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262
Title:
Many tests of Boost v1.54 fail
To
On my PC, running oneiric, version 11.10, on Xeon, with gcc 4.6.1, I also see
errors when testing Boost v1.55.
EXIT STATUS are:
1 : 11 (False results)
134 :1 (Exception, aborted)
139 :2 (Seg Fault)
200 : 10 (memory access violation)
201 : 8 (error detected)
I have to
After debugging some more, it looks like the issue is in:
BOOST : libs/filesystem/src/path.cpp
std::locale path::imbue(const std::locale loc)
{
std::locale temp(path_locale); line 918
path_locale = loc;
codecvt_facet_ptr =
std::use_facetstd::codecvtwchar_t,
Here are the traces for one of the cores:
boost1.54-1.54.0/bin.v2/libs/filesystem/test/operations_test_static.test/gcc-4.8/debug/link-static/operations_test_static
Program received signal SIGSEGV, Segmentation fault.
__atomic_add_dispatch (__val=1, __mem=0x0) at
Here is the trace when building PCRE 8.31 from Ubuntu sources:
sudo dpkg-buildpackage
...
CC_FOR_BUILD=cc CPPFLAGS=-D_FORTIFY_SOURCE=2 CFLAGS=-Wall -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security
LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro \
Public bug reported:
I'm now testing Boost v1.54 from Ubuntu sources.
I've done:
sudo apt-get update
sudo apt-get install libboost-dev
sudo apt-get install libboost-all-dev
sudo apt-get install dpkg-dev
sudo apt-get build-dep boost1.54
apt-get source boost1.54
sudo apt-get build-dep
I forgot to say that this is on PPC/LE with alpha2 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262
Title:
Many tests of Boost v1.54 fail
To manage notifications about this bug go to:
Public bug reported:
Version 8.31 of libpcre3 (pcre3 sources) is not ready for --enable-jit
option on Linux/PPC64 LE. It even does not compile.
Version 8.34 of libpcre3 does include code for Linux on PPC64-LE. However, this
code still fails for JIT. It is being fixed now.
Staty tune with:
39 matches
Mail list logo
