-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
make test target broken #926
Comments
Reproducible on macOS. |
Thx for reporting. Interesting... I'll do some research with older commits to find out. No clue yet where it exactly happened and why. |
On the develop branch, the built test binaries resident in |
To me it would actually make sense to place them in Can't really spot a reason for this in |
Test 3 already fails on v1.3.1, so nobody seems to have taken any notice thereof... No clue on that. This merge-commit 946b7f3 introduced the failure of tests 1 and 2 on
They should either be deleted again or related settings aligned to them in order to match. |
The above lines are commented-out in branch "build-settings" and thus the two first tests are functional again. Had a look at
Can't go back any further than v1.3.1 to determine exactly where it first appeared as build fails on v1.3.0 and v1.2.0 used autotools for building. However this shows that arguments are missing (maybe due to a change in the code where someone forgot to update the code for the files in Who can help fixing this? |
Maybe I have figured out the breakage. The first two breakages are caused by one commit between master and develop.
The possible reason is the removal of actual usage of Edit: commit that cause this breakage found:
The last two breakages are caused by the change of serial argument layout in memory. The latest serial buffer begins with no leading zeros which the test expects. |
Good job @chenguokai! I can verify that you are right with the first two failures and also tested the second issue successfully. So indeed this fixes that bug. I'll include the fix soon. Thank you. |
Hi,
Apparently, unitary tests are broken - i've no idea of the current level of brokenness, but, at least they do not run anymore due to some binary path change. I think this was a recent modification.
etc..
i'm running current develop branch on debian testing.
The text was updated successfully, but these errors were encountered: