Marked tests known to not work on various platforms #1670

2020-09-17T13:19:32+02:00

g1itch commented

2020-09-17 13:19:32 +02:00

(Migrated from github.com)

Hello!

These changes should fix PyBitmessage-travis-migrate.

TestProcessConfig and TestLogger work as expected only on Ubuntu Xenial. I marked them for skipping on other platforms.

Hello! These changes should fix PyBitmessage-travis-migrate. `TestProcessConfig` and `TestLogger` work as expected only on Ubuntu Xenial. I marked them for skipping on other platforms.

PeterSurda commented

2020-09-17 15:41:04 +02:00

(Migrated from github.com)

Thanks, still some minor issues. If you want I can provide a xenial image. I'm also working on supporting the .travis.yml file directly.

PeterSurda commented

2020-09-17 22:15:25 +02:00

(Migrated from github.com)

buildbot/PyBitmessage-travis-migrate is not meant to be permanent, it was just a hack to see if it kind of works. It doesn't have a proper environment. I now wrote a shell script that decodes .travis.yml directly and runs what's needed. It's not perfect but for the time being it's adequate. That one now finally passed v0.6 head. So the test for xenial probably isn't necessary.

buildbot/PyBitmessage-travis-migrate is not meant to be permanent, it was just a hack to see if it kind of works. It doesn't have a proper environment. I now wrote a shell script that decodes `.travis.yml` directly and runs what's needed. It's not perfect but for the time being it's adequate. That one now finally passed v0.6 head. So the test for xenial probably isn't necessary.

g1itch commented

2020-10-08 20:38:55 +02:00

(Migrated from github.com)

BTW: same mess with log and config test cases on Fedora 31: https://travis-ci.org/github/g1itch/PyBitmessage/jobs/734029435

How your travis_bash is doing?

BTW: same mess with log and config test cases on Fedora 31: https://travis-ci.org/github/g1itch/PyBitmessage/jobs/734029435 How your travis_bash is doing?

PeterSurda commented

2020-10-09 18:47:48 +02:00

(Migrated from github.com)

How your travis_bash is doing?

I think it works, at least on systems that have use apt. I'll try to setup a xenial image tomorrow and we'll see what the results will be.

> How your travis_bash is doing? I think it works, at least on systems that have use `apt`. I'll try to setup a xenial image tomorrow and we'll see what the results will be.

PeterSurda commented

2020-10-12 09:12:24 +02:00

(Migrated from github.com)

Looks like same problems on xenial as on bionic: https://buildbot.bitmessage.org/#/builders/15/builds/9/steps/4/logs/stdio

PS: if you register pybitmessage buildbot on github with your repo, it should automatically run the tests on any of your branch whenever you push: https://github.com/apps/pybitmessage-buildbot

PPS: I'm trying to give people the ability to stop/rerun jobs on their own branches, but it's not working yet.

Looks like same problems on xenial as on bionic: https://buildbot.bitmessage.org/#/builders/15/builds/9/steps/4/logs/stdio PS: if you register pybitmessage buildbot on github with your repo, it should automatically run the tests on any of your branch whenever you push: https://github.com/apps/pybitmessage-buildbot PPS: I'm trying to give people the ability to stop/rerun jobs on their own branches, but it's not working yet.

PeterSurda commented

2020-10-13 21:39:00 +02:00

(Migrated from github.com)

The script doesn't support TRAVIS_DIST, so it's skipping it everytime.

The script doesn't support `TRAVIS_DIST`, so it's skipping it everytime.

g1itch commented

2020-10-13 21:47:16 +02:00

(Migrated from github.com)

The script doesn't support TRAVIS_DIST, so it's skipping it everytime.

I did it intentionally. Despite the fact that these defected tests are succeed also on my Gentoo desktop environment, it looks like they also break test suite on your xenial buildbot environment as well as my simple fedora31 container.

This is a temporary solution. Proper fix would probably be rewriting bmconfigparser and extending tests.

> The script doesn't support `TRAVIS_DIST`, so it's skipping it everytime. I did it intentionally. Despite the fact that these defected tests are succeed also on my Gentoo desktop environment, it looks like they also break test suite on your xenial buildbot environment as well as my simple fedora31 container. This is a temporary solution. Proper fix would probably be rewriting bmconfigparser and extending tests.

PeterSurda commented

2020-10-14 19:46:43 +02:00

(Migrated from github.com)

For the "xenial_" and "bionic_" workers I now use the official ubuntu cloud images, and just install buildbot and some python and dev packages through cloud-init.

g1itch commented

2020-10-15 15:06:59 +02:00

(Migrated from github.com)

For the "xenial_" and "bionic_" workers I now use the official ubuntu cloud images, and just install buildbot and some python and dev packages through cloud-init.

It turns out that travis uses it's own python setup: https://github.com/travis-ci/travis-ci/issues/2231

> For the "xenial_" and "bionic_" workers I now use the official ubuntu cloud images, and just install buildbot and some python and dev packages through cloud-init. It turns out that travis uses it's own python setup: https://github.com/travis-ci/travis-ci/issues/2231

PeterSurda commented

2020-10-23 13:31:42 +02:00

(Migrated from github.com)

You can close this, it's superseded by #1683.

This repo is archived. You cannot comment on pull requests.

No reviewers