Error while Building Sync2 module

Development
61

can i have a screenshot of your two local instances ?? take a full screen shot with the url bar

62

sync-serv1
sync-serv11874×966 90.8 KB
sync-serv2
sync-serv21818×965 91.7 KB

1 Like
63

oh ya thats true @reagan. let me try out more options of how to have two servers running.

64

@dkayiwa on child and parent instance this is what I get

push
push995×533 66.6 KB

1 Like
65

@jwnasambu youve been able to reproduce the bug on the remote servers

1 Like
66

How far ? I am stack at failing to sync trying other options but…

67

@jwnasambu as a dev , thats where you now have to chip in , and start working on the bugs .:slightly_smiling_face:

1 Like
68

True. I have just liked the whole experience. Am beginning to think of JSON on a serious note.

2 Likes
69

I guess you can now start working on some tickets @jwnasambu now since you can reproduce some of the bugs.

1 Like
70

@jwnasambu can I have a screen shot look at your json files configuration for the general part of both instances…

71

@reagan Were you able to solve those failing test whilst building the sync module? And for the JSON configurations hope you are as well following the Sync2.0 User manual

72

Hi @dkayiwa why would the build for the sync module have test failures even after a fresh clone without any code changes done to it. Some kind of org.junit.ComparisonFailure on some of the tests. You can have a look at thisPastebin log, @reagan and @lgilbert shared the same results

1 Like
73

Surprisingly, I also see the same error on on atomfeed if you try to build it. It passes the same error with one test failing on the same basis org.junit.ComparisonFailure Here is a Pastebin log for it too. Failed to get the reason for these two occurrences. Does anyone else have a failure on the atomfeed?

74

Could this be because you are compiling on windows? Is any one on the team using a different operating system?

1 Like
75

@odorajonathan i have just made a commit to the atom feed module. Can you update and compile again to see what happens?

76

@mozzy and the rest, i have also made a commit to the sync module. Can you update and compile again to see what happens?

1 Like
77

@dkayiwa That didn’t go well as it gave this error log. The previous error still remians

78

@odorajonathan what message do you get when you run this command? git reset --hard

79

I get this

Admin@THe-ODoRa MINGW64 ~/atomfeed (master)

$ git reset --hard

HEAD is now at 4226a97 Adding the encoding when converting stream to string
80

@odorajonathan i have just made another commit. Update and compile again.