Mattia Rizzolo, on Wed 25 Nov 2015 13:35:01 +, wrote:
> On Mon, Nov 23, 2015 at 11:13:31AM +0100, Samuel Thibault wrote:
> > I built an interposing library myself, which produced the 0, but not the
> > bug.
> >
> > Could you also post the head of testlog0.txt?
>
> sure! (sorry it takes some t
On Mon, Nov 23, 2015 at 11:13:31AM +0100, Samuel Thibault wrote:
> I built an interposing library myself, which produced the 0, but not the
> bug.
>
> Could you also post the head of testlog0.txt?
sure! (sorry it takes some time to me to react...)
FWIW I genuinely don't know what those numbers me
Control: reopen -1
Control: found -1 0.1.7+dfsg-2
Samuel Thibault, on Mon 23 Nov 2015 11:00:21 +0100, wrote:
> Mattia Rizzolo, on Sun 22 Nov 2015 08:13:05 +, wrote:
> > mattia@profitbricks-build1-amd64 ../eztrace-1.1/build-mpich/test/automake %
> > tail testlog0.txt
> > 0 14019479517363
Mattia Rizzolo, on Sun 22 Nov 2015 08:13:05 +, wrote:
> mattia@profitbricks-build1-amd64 ../eztrace-1.1/build-mpich/test/automake %
> tail testlog0.txt
> 0 140194795173632 Reg 00
> 0 140194795173632 Reg 00
0?
Just thinking: AIUI reproducibi
On Fri, Nov 13, 2015 at 03:35:24PM +0100, Samuel Thibault wrote:
> Ok, so it's actually litl_print from litl-tools which went crazy, thus
> reassigning.
>
> To explain a bit: litl_print read a trace file
> (pbuilder1_eztrace_log_rank_1, 570 bytes long), and writes a dump of the
> trace (testlog.0.
Mattia Rizzolo, on Mon 16 Nov 2015 10:53:53 +, wrote:
> I'm sorry I haven't get back to yet before.
>
> On Fri, Nov 13, 2015 at 03:35:24PM +0100, Samuel Thibault wrote:
> > system (the testsuite is not supposed to run in parallel anyway), but
>
> if the testsuite is not supposed to run parall
I'm sorry I haven't get back to yet before.
On Fri, Nov 13, 2015 at 03:35:24PM +0100, Samuel Thibault wrote:
> system (the testsuite is not supposed to run in parallel anyway), but
if the testsuite is not supposed to run parallel, then you should avoid
that:
override_dh_auto_test:
- -dh_a
Now with the actual patch :)
Samuel
--- a/src/litl_read.c
+++ b/src/litl_read.c
@@ -347,6 +347,14 @@ static litl_read_event_t* __litl_read_ne
to_be_loaded = 1;
}
+ // fetch the next block of data from the trace
+ if (to_be_loaded) {
+__litl_read_next_buffer(trace, process, thread
Control: reassign -1 litl-tools
Hello,
Mattia Rizzolo, on Thu 12 Nov 2015 08:28:59 +, wrote:
> it (can?) generate very huge files that fills
> the entire file system (and we have a 200GB file system).
Urlgllg, to say the least...
> mattia@profitbricks-build5-amd64 /srv/workspace/pbuilder %
Source: eztrace
Version: 1.1-2
Severity: minor
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
User: reproducible-bui...@lists.alioth.debian.org
Usertag: ftbfs
Dear maintainer,
in the context of Reproducible Builds, we noticed that eztrace can't
reliably be built because it (can?) gener
10 matches
Mail list logo
