#19891: Travis CI support
--------------------------------------+------------------------------------
     Reporter:  marko@…               |                    Owner:  gcc
         Type:  Cleanup/optimization  |                   Status:  assigned
    Component:  Testing framework     |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:  Travis, CI, testing   |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by gcc):

 * easy:  1 => 0


Comment:

 Hi @apollo13,

 Status update:

 * I finally managed to persuade the Travis guys to [https://github.com
 /travis-ci/travis-ci/issues/1125#issuecomment-19539914 increase the size
 of the ramdisk] used for the databases. The tests now [https://travis-
 ci.org/aptivate/django/jobs/8274059 pass] without reconfiguring
 PostgreSQL.

 * I also moved the Travis configuration scripts and files to a Git repo so
 that I don't have to host them somewhere (except in Github) to run tests
 in Travis. I hope that's an acceptable alternative to HTTP hosting.

 * I can't do anything about the [https://github.com/travis-ci/travis-
 ci/issues/280 email notification issue], it's a limitation of Travis that
 [https://github.com/travis-ci/travis-ci/issues/1094 will hopefully be
 fixed one day]. If this is a blocker to merging then Travis support will
 not be merged any time soon, and there's nothing I can do about it.

 * I added support for UNLOGGED tables that should speed up running tests
 in Postgres for all users. That could be considered a separate
 branch/ticket if necessary.

 * Selenium tests are still broken. I want to see if I can overcome the
 other issues first before investing time in fixing them.

 You can see the latest work
 [https://github.com/aptivate/django/commits/ticket_19891 here]. Please let
 me know if these things are acceptable. If so then I'll keep working on
 fixing selenium tests.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19891#comment:28>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.18d779ddc0f47ffd9ed2ebbed7483bc5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to