develooper Front page | perl.perl5.porters | Postings from October 2013

Smoke failures

Thread Next
From:
Johan Vromans
Date:
October 31, 2013 09:28
Subject:
Smoke failures
Message ID:
21106.8873.357869.116398@phoenix.squirrel.nl
I run a daily smoke for blead on x86_64 and armv6l. The reports are
mailed to smokers-reports@perl.org and submitted to the smoke database.

I've noticed that many of my smoke reports do not end up in the
database. Sometimes it looks like russian roulette, e.g (shown is the
final line of the log file wich shows the result from the database
submission):

  loga820780c62918236069b3b55502640c99a9e812a.log:{"id":5701}
  logf09d8c379a9d59fc38b2fc1517c6659ed99f544e.log:{"db_error":...}
  log23aa77bc9fa488ace3ef1089104e999c23821171.log:{"db_error":...}
  log5bf072acecd43c8898653edd2462bf41bc618a98.log:{"db_error":...}
  log3cfe9c806f5c45049445a0194a340960268c902f.log:{"id":5841}
  logb5556731e072795d671ca231c2f61614b84b4f05.log:{"id":5872}
  logb60fc215755c2aabdaebeac3d21e48f45d59f304.log:{"id":5907}
  logde19dead5ea4c0494ce36818d909a44f25573257.log:{"id":5941}
  log407f86e143fb0e33ece8e41bfd0ec5ad641133c8.log:{"db_error":...}

Sometimes reports are missing over periods of weeks. I cannot verify
that submission success implies that the results end up in the
database. The mail messages are sent correctly, since I get copies. In
fact, that is what I keep a daily eye on...

(And yes, sometimes it is my fault when a stray lockfile prevents
smokes from running.)

I think the smoke testing procedures can use a bit of fixing and
polishing. If someone is willing to pay attention (Dave M?) please
contact me and I can send logfiles and other information.

Thanks.

-- Johan

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About