You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
(25) |
2
(25) |
3
(5) |
4
(13) |
|
5
(4) |
6
(8) |
7
(6) |
8
|
9
(10) |
10
(15) |
11
(9) |
|
12
(14) |
13
(10) |
14
(24) |
15
(41) |
16
(13) |
17
(9) |
18
(3) |
|
19
(10) |
20
(11) |
21
(28) |
22
(36) |
23
(52) |
24
(36) |
25
(12) |
|
26
(31) |
27
(27) |
28
(20) |
29
(15) |
30
(22) |
31
(17) |
|
|
From: Bart V. A. <bar...@gm...> - 2009-07-07 18:12:41
|
On Tue, Jul 7, 2009 at 12:15 AM, Stefan Kost<en...@ho...> wrote: > GStreamer is heavily multithreaded too and uses both mutexes and glibs > atomic operations. The unit tests are already using valgrind's memcheck > in a 2nd run. I've tried drd and helgrind once, but got a lot of > warnings and had no idea where to start. One possible approach is to start with the first reported warning and to analyze the involved call stacks carefully in order to find out why the warning was reported. Subsequently you can either insert an annotation in the source code of the analyzed program or fix the reported issue if it is a bug. Next, recompile your program and rerun it under Valgrind, and again analyze the first reported warning. After a few steps all warnings will be suppressed. This approach has already been applied succesfully to other open source projects. Bart. |
|
From: Nicholas N. <n.n...@gm...> - 2009-07-07 12:07:20
|
On Tue, Jul 7, 2009 at 10:02 PM, Ashley Pittman<as...@pi...> wrote: > > Ok, I got that. How do the nightly test emails work, I assume they > parse the stdout of "perl tests/vg_regtest memcheck ..." so that needs > to be preserved as well. nightly/bin/nightly (in the standard case) invokes "make regtest" but the output is just copied to the report file, there's no parsing. Nick |
|
From: Ashley P. <as...@pi...> - 2009-07-07 12:02:44
|
On Tue, 2009-07-07 at 21:55 +1000, Nicholas Nethercote wrote: > On Tue, Jul 7, 2009 at 8:01 PM, Ashley Pittman<as...@pi...> wrote: > > > > I'm looking at spending a couple of days fixing up the regtests so they > > work with VPATH builds, this is probably going to end up being > > moderately intrusive however. > > > > Is there anything I need to know before I start hacking away at the > > code, are all the tests driven from "make regtest" for example or are > > there other ways of driving them that I need to preserve? > > The arguments to vg_regtest can be entire directories or individual > test files (with or without the .vgtest suffix). So all these kinds > of invocations must be preserved: > > perl tests/vg_regtest memcheck/ > perl tests/vg_regtest memcheck/addressable.vgtest > perl tests/vg_regtest memcheck/addressable Ok, I got that. How do the nightly test emails work, I assume they parse the stdout of "perl tests/vg_regtest memcheck ..." so that needs to be preserved as well. > > One thing that springs to mind is that platform_test could be removed > > and the logic rolled back into vg_regtest for example, is there any > > reason why I shouldn't do this? > > Not that I can see; vg_regtest seems to be the only user of platform_test. That should simplify things a bit. I notice a lot of the scripts call other scripts using ./ notation, I might find I need to put "$(top_srcdir)/$dir" on PATH and removing the ./ prefix from these scripts. Ashley, -- Ashley Pittman, Bath, UK. Padb - A parallel job inspection tool for cluster computing http://padb.pittman.org.uk |
|
From: Nicholas N. <n.n...@gm...> - 2009-07-07 11:56:02
|
On Tue, Jul 7, 2009 at 8:01 PM, Ashley Pittman<as...@pi...> wrote: > > I'm looking at spending a couple of days fixing up the regtests so they > work with VPATH builds, this is probably going to end up being > moderately intrusive however. > > Is there anything I need to know before I start hacking away at the > code, are all the tests driven from "make regtest" for example or are > there other ways of driving them that I need to preserve? The arguments to vg_regtest can be entire directories or individual test files (with or without the .vgtest suffix). So all these kinds of invocations must be preserved: perl tests/vg_regtest memcheck/ perl tests/vg_regtest memcheck/addressable.vgtest perl tests/vg_regtest memcheck/addressable > One thing that springs to mind is that platform_test could be removed > and the logic rolled back into vg_regtest for example, is there any > reason why I shouldn't do this? Not that I can see; vg_regtest seems to be the only user of platform_test. Nick |
|
From: Ashley P. <as...@pi...> - 2009-07-07 11:33:31
|
All, I'm looking at spending a couple of days fixing up the regtests so they work with VPATH builds, this is probably going to end up being moderately intrusive however. Is there anything I need to know before I start hacking away at the code, are all the tests driven from "make regtest" for example or are there other ways of driving them that I need to preserve? One thing that springs to mind is that platform_test could be removed and the logic rolled back into vg_regtest for example, is there any reason why I shouldn't do this? Ashley, -- Ashley Pittman, Bath, UK. Padb - A parallel job inspection tool for cluster computing http://padb.pittman.org.uk |
|
From: Konstantin S. <kon...@gm...> - 2009-07-07 07:18:58
|
> GStreamer is heavily multithreaded too and uses both mutexes and glibs > atomic operations. The unit tests are already using valgrind's memcheck > in a 2nd run. I've tried drd and helgrind once, but got a lot of > warnings and had no idea where to start. Dynamic annotations (supported by ThreadSanitizer and, afaik, by fresh DRD) can help you explain lock-less synchronization to the tool. --kcc |