Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assorted fixes #143

Merged
merged 1 commit into from
Dec 24, 2019
Merged

Assorted fixes #143

merged 1 commit into from
Dec 24, 2019

Conversation

dagwieers
Copy link
Collaborator

@dagwieers dagwieers commented Dec 23, 2019

This PR includes:

  • Various small fixes to tests
  • The use of the Addon Signals master branch for testing

This fixes tests as seen at: https://travis-ci.org/dagwieers/service.upnext/branches

@dagwieers
Copy link
Collaborator Author

@im85288 Can you please look into why Travis is no longer working? Tests were failing and we did not know because there's no checks being made automatically.

@dagwieers dagwieers force-pushed the assorted-fixes2 branch 2 times, most recently from 9f33824 to 027623a Compare December 24, 2019 01:08
This PR includes:
- Various small fixes to tests
- The use of the Addon Signals master branch for testing
@im85288
Copy link
Owner

im85288 commented Dec 24, 2019

@dagwieers The build started to fail from the merge of issue #93

It looks like the problem is only there for python 3.5 where I see the following exception:

Traceback (most recent call last): File "/home/travis/build/im85288/service.upnext/test/test_encoding.py", line 71, in test_to_addon_signals decoded_data = AddonSignals._decodeData('["%s"]' % encoded_data) # pylint: disable=protected-access File "/home/travis/virtualenv/python3.5.6/lib/python3.5/site-packages/AddonSignals.py", line 21, in _decodeData return json.loads(base64.b64decode(data[0])) File "/opt/python/3.5.6/lib/python3.5/json/__init__.py", line 312, in loads s.__class__.__name__)) TypeError: the JSON object must be str, not 'bytes'

@dagwieers
Copy link
Collaborator Author

This is related to a bug we fixed in AddonSignals. The master branch should have this fixed. The real build issues happened later.

@dagwieers
Copy link
Collaborator Author

@im85288 I would like to see the Travis integration fixed in GitHub. I don't know when this stopped working...

@im85288
Copy link
Owner

im85288 commented Dec 24, 2019

@im85288 im85288 merged commit b1278d4 into im85288:master Dec 24, 2019
@im85288
Copy link
Owner

im85288 commented Dec 24, 2019

@dagwieers travis build passing now thanks, I have added you as a Collaborator so you should be able to see everything I can

@dagwieers
Copy link
Collaborator Author

@im85288 Thanks, but I can't seem to look into why Travis is not integrated in GitHub for this project. It worked for some time though, see the check-marks on this page:
https://github.com/im85288/service.upnext/pulls?page=2&q=is:pr+is:closed

@im85288
Copy link
Owner

im85288 commented Dec 24, 2019

@dagwieers I did get a notification email that the travis build succeeded when I merged this pull request and the home code page badge now shows it as passed. Is this what you mean?

@dagwieers
Copy link
Collaborator Author

dagwieers commented Dec 24, 2019

So the integration of GitHub and Travis I am looking for is:

This used to work fine up until November 7.

@dagwieers
Copy link
Collaborator Author

It seems to be working again, I rebuild some of the older PRs and they get marked !

@dagwieers dagwieers added the testing Related to automated testing label Dec 25, 2019
@dagwieers dagwieers added this to the v1.1.0 milestone Dec 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Related to automated testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants