[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2049: Decide where "packaging tests" should live.

Tahoe-LAFS trac at tahoe-lafs.org
Thu Sep 25 19:51:06 UTC 2014


#2049: Decide where "packaging tests" should live.
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  nejucomo
  nejucomo               |     Status:  new
         Type:  task     |  Milestone:  soon (release n/a)
     Priority:  normal   |    Version:  1.10.0
    Component:  dev-     |   Keywords:  packaging dev-infrastructure
  infrastructure         |  buildbot pypi openitp-packaging
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by nejucomo):

 Zancas and I are reading over [https://github.com/tahoe-lafs/buildbot-
 config-tahoe/blob/master/tahoe/git/master.cfg buildbot-config-
 tahoe/tahoe/git/master.cfg] in order to learn what should appear in
 [https://github.com/tahoe-lafs/packaging-tests packaging-tests].

 In my opinion, the {{{master.cfg}}} should be minimal, and I'd like to
 move some of the operations here into {{{packaging-tests}}}, and here are
 some examples of why:

 * In [https://github.com/tahoe-lafs/buildbot-config-
 tahoe/blob/master/tahoe/git/master.cfg#L92 master.cfg line 92] there's a
 conditional on a per-buildslave option {{{do_test_already_have_dep}}}
 which determines whether or not to run a test. I would rather have two
 explicitly named tests such as
 {{{test_tahoe_build_with_preexisting_pycryptopp}}} versus
 {{test_tahoe_build_without_preexisting_pyrcryptopp}}} and then configure
 buildslaves by specifying which tests they run.  (In fact, a single
 buildslave may be able to run both tests which would be handy especially
 when we have few buildslaves for a given architecture.)

 ... (I will edit this comment to write more detail, but I want to submit
 now because I'm paranoid of losing my progress...)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2049#comment:24>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list