Jul 15 2018
Dec 5 2017
Jul 10 2017
Jun 1 2017
Apr 19 2017
We have still few issues in Appveyor and should revalidate all open subtasks here (as they propably should be closed), but that looks like real milestone for this project. We should treat right now any Travis failure as blocker (at least till we move to Wikimedia CI) and try to make all tests properly mocked.
Mar 29 2017
Mar 21 2017
Isn't it a dup for T158943 ?
Mar 8 2017
Feb 24 2017
Basically it looks, that for pywikibot/i18n git submodule update --init is failing.
Yep, but it was reintroduced in the very next commit, so we should figure out why, because I don't believe that another removal will resolve this issue permanently.
OK, I can confirm, that
Warning: Unable to read "/home/tmagulski/Dokumenty/magul/i18n/core_stable/qqq.json" file (Error code: ENOENT). Use --force to continue.
I've digged one revert from last December (rPWINcd138ef95047e2b4e304d934f640f90e1abf68a3) that looks like something connected.
Feb 21 2017
@Phantom42 Yes, I agree. Actually if You would read my comments above, I done the same research few days ago.
Feb 19 2017
I've checked on Py2,6 and Py2.7 and str(StopIteration()) results with '' so this assertion should be meet in either way. I also checked, that we use unittest2 as unittest for Python versions lower then 2.7.3. I believe problem could be somwhere there.
This particular line that is failing has been introduced in our code in rPWBC2c33f951
Feb 4 2017
Jan 13 2017
Ok @Xqt I upload patch that abandon 2.6 and introduce 3.6 on our Travis CI and Appveyor CI. Feel free to review.
Is there any reason to inform user in any other fashion then ImportError and is there any particular reason that it should be implemented for six package and not some else?
Jan 12 2017
It looks like Your patch requires rebase and it should also remove Python 2.6 from Travis CI and Appveyor CI.
@Dereckson You have my full support on that. Actually we right now have little (or no) unittests in pywikibot and I would like to change it.
I was going create this patch, but You're welcome to do it also, I will just review it (remember about sorting list).
Jan 11 2017
So can we close this issue? What do You think? @jhsoby ?
Yep, You're most probably right. I will create patch for this test in Pywikibot
Jan 10 2017
Jan 9 2017
Closing it as invalid, because there were no activity for over a month from @Shizhao and I was not able to reproduce it.
@Dalba found a reason why we have problems and remove 2 tests. I'm closing it as resolved.
Jan 7 2017
@Huji I'm aware that we are running 4 jobs to verify any gerrit patch, but haven't found time to check how they are defined. There is also plan to move the whole testing procedure to Wikimedia CI infrastructure (see task T132138), so if You have time to update our jobs there that will be really big step in right direction.
Jan 6 2017
Jan 1 2017
Dec 29 2016
Dec 23 2016
Dec 21 2016
Great, thank You!
Shit, I haven't test it, just assumed, that it will work. I will looks further into it. :/
Primary repository is available here: ssh://gerrit.wikimedia.org:29418/pywikibot/core
@maiden_taiwan I see that You're testing today a lot with 2.0rc5 release. Could You test it also on tip of master branch?
Dec 19 2016
Dec 18 2016
Dec 17 2016
I've tested 707 sites (all production sites: commons, wikidata, wikipedia, wikivoyage, wiktionary, wikibooks, wikinews, wikiquote, wikisource, wikiversity). The whole test takes around 25 minuts.
Dec 16 2016
Hi @Mayank.jindal5, nice to see You here. Have fun trying to solve this issue, and if You would have any specific question, don't hesitate to ask.
Issue about TestFactoryGenerator::test_random_generator_ns_multi was resolved in T150892.
In last 7 months there were more then 200 occurrences of The build has been terminated (around 5 months ago, build #3545 practically every build has stalled). I have examined almost 100 of them.