unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Leo Famulari <leo@famulari.name>, Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH] gnu: Add dlib.
Date: Tue, 16 Aug 2016 10:15:31 +1000	[thread overview]
Message-ID: <4752bc68-5466-6c26-a7b4-e53aec400ff5@uq.edu.au> (raw)
In-Reply-To: <20160815222840.GA10735@jasmine>

On 16/08/16 08:28, Leo Famulari wrote:
> On Mon, Aug 15, 2016 at 09:29:11PM +0100, Marius Bakke wrote:
>> Leo Famulari <leo@famulari.name> writes:
>>> Running test_empirical_kernel_map / phase `check' failed after 2043.7 seconds
>> Strange, I've built this dozens of times now with no test failures
>> (GuixSD on amd64). Are you memory constrained by any chance? Any OOM or
>> segfaults? I don't think the tests have taken more than ~15 minutes to
>> run either, once they are built.
> I don't think I'm particularly resource constrained. I have ~7 GiB RAM
> available to build with, plenty of disk space, and the processor is this
> thing:
>
> http://ark.intel.com/products/64896/Intel-Core-i5-3320M-Processor-3M-Cache-up-to-3_30-GHz
>
> It appears to exit cleanly (no segfault or OOM).
>
> It fails the same test on this machine as well as a slower x86_64
> (Thinkpad x200s). One machine is Guix / Debian, the other is GuixSD.
I built this patch on a x86_64 server with 40 cores and 256G of memory 
twice, here's what I got:

Running test_one_vs_all_trainer \

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!! TEST FAILED: test_one_vs_all_trainer 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Failure message from test:

Error occurred at line 141.
Error occurred in file 
/tmp/nix-build-dlib-19.1.drv-0/dlib-19.1/dlib/test/one_vs_all_trainer.cpp.
Failing expression was ans == res.
res:
60  0  0
  0 69  1
  0  0 80




Testing Finished
Total number of individual testing statements executed: 471078543
Number of failed tests: 1
Number of passed tests: 133

phase `check' failed after 2206.2 seconds
builder for `/gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv' 
failed with exit code 1
@ build-failed /gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv 
- 1 builder for 
`/gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv' failed with 
exit code 1
guix build: error: build failed: build of 
`/gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv' failed


and in the second run.....


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!! TEST FAILED: test_one_vs_all_trainer 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Failure message from test:

Error occurred at line 141.
Error occurred in file 
/tmp/nix-build-dlib-19.1.drv-0/dlib-19.1/dlib/test/one_vs_all_trainer.cpp.
Failing expression was ans == res.
res:
30  0 30
  0 35 35
  0  0 80




Testing Finished
Total number of individual testing statements executed: 470341624
Number of failed tests: 1
Number of passed tests: 133

phase `check' failed after 2183.7 seconds
builder for `/gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv' 
failed with exit code 1
@ build-failed /gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv 
- 1 builder for 
`/gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv' failed with 
exit code 1
guix build: error: build failed: build of 
`/gnu/store/gqbzlp1g5h038rxswaz2b6y78d57q8sx-dlib-19.1.drv' failed

real    37m12.419s
user    0m5.344s
sys    0m0.412s

  reply	other threads:[~2016-08-16  0:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13 17:15 [PATCH] gnu: Add dlib Marius Bakke
2016-08-14 17:25 ` Leo Famulari
2016-08-14 19:52   ` Marius Bakke
2016-08-15  7:43     ` Alex Kost
2016-08-15 11:51       ` Marius Bakke
2016-08-15 20:15         ` Leo Famulari
2016-08-15 20:29           ` Marius Bakke
2016-08-15 22:28             ` Leo Famulari
2016-08-16  0:15               ` Ben Woodcroft [this message]
2016-08-16 10:45                 ` Marius Bakke
2016-08-16 20:47                   ` Leo Famulari
2016-08-16 23:31                     ` Ben Woodcroft
2016-08-16 23:45                       ` Leo Famulari
2016-08-17  3:24                         ` Ben Woodcroft
2016-08-17  5:01                           ` Ben Woodcroft
2016-08-17 14:48                           ` Marius Bakke
2016-08-18 20:23                             ` Leo Famulari
2016-08-19 10:52                               ` Marius Bakke
2016-08-21 20:17                                 ` Leo Famulari
2016-08-22  2:30                                   ` Ben Woodcroft
2016-08-22 12:01                                     ` Marius Bakke
2016-08-23 18:33                                       ` Marius Bakke
2016-08-24 10:26                                         ` Marius Bakke
2016-08-24 17:26                                           ` Leo Famulari
2016-08-24 19:08                                             ` Marius Bakke
2016-08-24 22:51                                               ` Ben Woodcroft
2016-08-30 14:43                                               ` Marius Bakke
2016-08-31 19:09                                                 ` Leo Famulari
2016-09-09 12:15                                                   ` Marius Bakke
2016-09-10 12:32                                                     ` Marius Bakke
2016-09-10 18:16                                                       ` Leo Famulari
2016-09-13  5:14                                                         ` Leo Famulari
2016-09-13  5:14                                                       ` Leo Famulari
2016-08-18 20:18                           ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4752bc68-5466-6c26-a7b4-e53aec400ff5@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).