[bug 618] marked fixed,	but dstress bug_optimize_294 showing some failures still
    Thomas Kuehne 
    thomas at kuehne.cn
       
    Sun Jan 21 15:38:54 PST 2007
    
    
  
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brad Roberts schrieb am 2007-01-20:
[...]
> What I'm actually thinking about here is how to check dstress vs 
> bugzilla to make sure that bugs that are marked fixed are _actually_ 
> fixed.
1) svn checkout svn://svn.berlios.de/dstress/trunk/ dstress
2) cd dstress
3) dmd tools/db.d -ofdb
4) bunzip2 < raw_results/linux-amd64_dmd-1.00.log.bz2 | db > sql_data
All test cases for bugs filed via Bugzilla have a @url@ line containing
http://.*puremagic[.]com
> And then make sure that all the failing tests have a 
> corresponding bug filed (many just point to a news group posting, which 
> is easily and for most probably lost in the distant past).
If the test case has no puremagic- at url@, then there is a good chance
that no Buzilla entry was filed.
Thomas
-----BEGIN PGP SIGNATURE-----
iD8DBQFFs//sLK5blCcjpWoRAkbFAJsEY+5qz/z3ykNTtIMirfdg0VE/WgCfVXQx
pRLKOfy7yyKQJWRkY9bkjGo=
=LVD1
-----END PGP SIGNATURE-----
    
    
More information about the Digitalmars-d-bugs
mailing list