View Issue Details

IDProjectCategoryView StatusLast Update
0004489TalerWeb site(s)public2016-05-06 20:28
ReporterChristian Grothoff Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityhighSeverityblockReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Version0.0 
Target Version0.0Fixed in Version0.0 
Summary0004489: lcov.taler.net again is outdated / fails to auto-update
DescriptionPlease look into it...
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2016-05-04 13:43

manager   ~0010629

Now I'm getting a 403...

Marcello Stanisci

2016-05-04 20:38

reporter   ~0010637

I've just restarted the coverage script (deployment/taler-build/coverage.sh from deployment git repo). It contains a 'make check' which does some performance tests and they take very long to complete and therefore make lcov generate the html. There is a detached 'screen' session running the script on tripwire; you can resume it with:

$ screen -r 17758.pts-7.tripwire

Christian Grothoff

2016-05-05 07:20

manager   ~0010641

We might want to (1) change the code to not make the benchmark not take quite that long, and (2) not run the benchmarks as part of lcov. Running the "perf_" logic is enabled by "--enable-expensivetests", so we should NOT pass that configure option for the lcov setup.

Marcello Stanisci

2016-05-06 19:25

reporter   ~0010657

Ok, but if you look at deployment/taler-build/coverage.sh, there is no "--enable-expensivetests" passed to configure. By the way, it's still running.

Christian Grothoff

2016-05-06 19:51

manager   ~0010658

It wasn't running, it was hung. Maybe an old (buggy) version. Anyway, I've killed it. The buildbot usually has an option to give a timeout to jobs. We should somehow limit this one to say 1h.

Christian Grothoff

2016-05-06 20:11

manager   ~0010660

Fixed two issues with the testcase (missing timeout, hang if aggregator process not found).

Issue History

Date ModifiedUsernameFieldChange
2016-05-04 04:59Christian GrothoffNew Issue
2016-05-04 04:59Christian GrothoffStatusnew => assigned
2016-05-04 04:59Christian GrothoffAssigned To => Marcello Stanisci
2016-05-04 13:43Christian GrothoffNote Added: 0010629
2016-05-04 20:38Marcello StanisciNote Added: 0010637
2016-05-05 07:20Christian GrothoffNote Added: 0010641
2016-05-06 19:25Marcello StanisciNote Added: 0010657
2016-05-06 19:51Christian GrothoffNote Added: 0010658
2016-05-06 20:11Christian GrothoffNote Added: 0010660
2016-05-06 20:27Christian GrothoffStatusassigned => informing
2016-05-06 20:27Christian GrothoffFixed in Version => 0.0
2016-05-06 20:27Christian GrothoffResolutionopen => fixed
2016-05-06 20:28Christian GrothoffStatusinforming => closed
2016-05-06 20:28Christian GrothoffTarget Version0.1 => 0.0