- "/tmp/rustc-test/rustc-1.25.0-src/build/x86_64-unknown-linux-gnu/stage0-tools-bin/rustdoc-themes" "/tmp/rustc-test/rustc-1.25.0-src/build/x86_64-unknown-linux-gnu/stage2/bin/rustdoc"
"/tmp/rustc-test/rustc-1.25.0-src/src/librustdoc/html/static/themes"
File "./x.py", line 20, in <module>
bootstrap.main()
File "/tmp/rustc-test/rustc-1.25.0-src/src/bootstrap/bootstrap.py", line
763, in main
bootstrap()
File "/tmp/rustc-test/rustc-1.25.0-src/src/bootstrap/bootstrap.py", line
754, in bootstrap
run(args, env=env, verbose=build.verbose)
File "/tmp/rustc-test/rustc-1.25.0-src/src/bootstrap/bootstrap.py", line
148, in run
raise RuntimeError(err)
/tmp/rustc-test/rustc-1.25.0-src/build/bootstrap/debug/bootstrap test
--verbose --no-fail-fast
NotPresent', /checkout/src/libcore/result.rs:916:5
I could not find anything with checkout, but ./src/libcore/result.rs line
/// `Ok(None)` will be mapped to `None`.
/// `Ok(Some(_))` and `Err(_)` will be mapped to `Some(Ok(_))` and
`Some(Err(_))`.
So it may have just been summarizing results when it failed.
Yeah, it seems to be just plain weird in how it goes about things.
I'm currently adding the following to the [rust] part of
config.toml:
# get reasonably clean output from the test harness
quiet-tests = true
but I don't, for the moment, have a view on whether or not that is a
useful addition.
I earlier tried, in the same part of config.toml
thinlto = false
which is said to make the *compiler* faster. But on my 4-core ryzen
the build time for rust went from low-50s of minutes (some
variation from one run to the next) to over 70 minutes, so I didn't
think any potential savings from using it to compile librsvg and
firefox would be likely to make up that time.
=============
$ grep 'running .* tests' ../rustc-testlog | awk '{ sum += $2 } END { print
sum }'
15736
$ grep '^test result:' ../rustc-testlog | awk '{ sum += $6 } END { print
sum }'
5
$ grep FAIL ../rustc-testlog
test [compile-fail] compile-fail/issue-37131.rs ... FAILED
That one needs llvm built for a thumb (ARM) variant.
test result: FAILED. 2301 passed; 1 failed; 15 ignored; 0 measured; 0
filtered out
test [debuginfo-gdb] debuginfo/gdb-pretty-struct-and-enums-pre-gdb-7-7.rs
... FAILED
test [debuginfo-gdb] debuginfo/pretty-huge-vec.rs ... FAILED
test [debuginfo-gdb] debuginfo/pretty-uninitialized-vec.rs ... FAILED
test result: FAILED. 82 passed; 3 failed; 24 ignored; 0 measured; 0 filtered
out
test [run-make] run-make/sysroot-crates-are-unstable ... FAILED
test result: FAILED. 174 passed; 1 failed; 0 ignored; 0 measured; 0 filtered
out
For my latest attempt (without gdb), one of the debuginfo-gdb tests
passed, 84 failed (they need gdb) and soem others were ignored.
Looking at the reported panics, I got one weird one which might be
related to the invalid opcodes (those seem to be related to building
a debug version of rustlib for use in the tests):
run-make/sysroot-crates-are-unstable
Traceback (most recent call last):
File "test.py", line 64, in <module>
libs = get_all_libs(join(sysroot, 'lib/rustlib/{}/lib'.format(os.environ['TARGET'])))
File "test.py", line 59, in get_all_libs
for f in listdir(dir_path)
OSError: [Errno 2] No such file or directory: 'lib/rustlib/x86_64-unknown-linux-gnu/lib'
make: *** [Makefile:2: all] Error 1
I think I forgot to mention that I'm building with
PYTHON=/usr/bin/python3 but that doesn't seem to be related to the
crash, that happens with both versions of python.
Back to trying to fly too close to the sun, there are a couple of
weeks before we need 1.25 ...
ĸen
--
In my seventh decade astride this planet, and as my own cells degrade,
there are some things I cannot do now: skydiving, marathon running,
calculus. I couldn't do them in my 20s either, so no big loss.
-- Derek Smalls, formerly of Spinal Tap
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html