Bug 1562192 - test run-pass/i128.rs fails in s390x
Summary: test run-pass/i128.rs fails in s390x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: DevTools
Classification: Red Hat
Component: rust
Version: rust-toolset-7
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 2018.4
Assignee: Josh Stone
QA Contact: Edjunior Barbosa Machado
Vladimír Slávik
URL:
Whiteboard:
Depends On: 1610053
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-29 18:20 UTC by Edjunior Barbosa Machado
Modified: 2018-11-13 15:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-11-13 15:24:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rust-lang rust issues 49828 0 None None None 2018-04-10 01:06:41 UTC
Red Hat Product Errata RHEA-2018:3584 0 None None None 2018-11-13 15:24:46 UTC

Description Edjunior Barbosa Machado 2018-03-29 18:20:30 UTC
Description of problem:
test run-pass/i128.rs from rust internal testsuite fails on both rhel-7.5 and rhel-alt-7.5 in s390x.
The testcase runs successfully in other archs.

Version-Release number of selected component (if applicable):
rust-toolset-7-rust-1.24.0-1.el7

How reproducible:
100%

Steps to Reproduce:
1. rpmbuild --rebuild rust-toolset-7-rust-1.24.0-1.el7.src.rpm

Actual results:
(...)
test [run-pass] run-pass/i128.rs ... FAILED
(...)
---- [run-pass] run-pass/i128.rs stdout ----
        
error: test run failed!
status: exit code: 101
command: "/root/rpmbuild/BUILD/rustc-1.24.0-src/build/s390x-unknown-linux-gnu/test/run-pass/i128.stage2-s390x-unknown-linux-gnu"
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `-207698809054923482737659375`,
 right: `-11259375`', /root/rpmbuild/BUILD/rustc-1.24.0-src/src/test/run-pass/i128.rs:83:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:68
             at libstd/sys_common/backtrace.rs:57
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:381
   3: std::panicking::default_hook
             at libstd/panicking.rs:397
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:577
   5: std::panicking::begin_panic
             at libstd/panicking.rs:538
   6: std::panicking::begin_panic_fmt
             at libstd/panicking.rs:522
   7: i128::main
   8: std::rt::lang_start::{{closure}}
   9: std::panicking::try::do_call
             at libstd/rt.rs:59
             at libstd/panicking.rs:480
  10: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:101
  11: std::rt::lang_start_internal
             at libstd/panicking.rs:459
             at libstd/panic.rs:365
             at libstd/rt.rs:58
  12: main
  13: __libc_start_main
  14: <unknown>

------------------------------------------

thread '[run-pass] run-pass/i128.rs' panicked at 'explicit panic', tools/compiletest/src/runtest.rs:2788:9
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:68
             at libstd/sys_common/backtrace.rs:57
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:381
   3: std::panicking::default_hook
             at libstd/panicking.rs:391
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:577
   5: std::panicking::begin_panic
   6: compiletest::runtest::ProcRes::fatal
   7: compiletest::runtest::TestCx::fatal_proc_rec
   8: compiletest::runtest::TestCx::run_rpass_test
   9: compiletest::runtest::run
  10: <F as alloc::boxed::FnBox<A>>::call_box
  11: <F as alloc::boxed::FnBox<A>>::call_box
             at libtest/lib.rs:1443
             at ./src/liballoc/boxed.rs:815
  12: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:101

Comment 2 Josh Stone 2018-04-10 01:12:20 UTC
Note, the `i128` type is still unstable in the compiler, but it is on track to be declared stable in the upcoming 1.26 release.

Comment 9 errata-xmlrpc 2018-11-13 15:24:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:3584


Note You need to log in before you can comment on or make changes to this bug.