-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
performance bug (introduced at some time after Jan 19, 2016) #1543
Comments
The main reason I'm having trouble bisecting is that my attempts to remake older versions almost always result in executables that can report their version number correctly, but otherwise trip an assertion, e.g.:
In case there's something obviously wrong with the procedure I'm following, here it is in brief:
@nicowilliams, @wtlangford - Any suggestions would be appreciated. Thanks. |
I wouldn't expect any issues with your method. I usually run |
@wtlangford - You're right: jq-1.5rc2-238-g10d6605-dirty (May 20, 2017) |
@pkoppstein The way to bisect in the face of that is to write a script like this:
|
@pkoppstein and, of course, you'll want to force a timeout on your test. |
I used this bisect script:
to find a likely commit that introduced this:
So it looks like e24af3c, which is just this (ignoring docs and test changes):
I'm guess there's a an implied Oy. We may have to revisit that one patch entirely. It was intended to allow |
@wtlangford We should back this out before releasing 1.6. |
Revert in-progress. |
@pkoppstein Thanks for the report! This is fixed in master now. |
@pkoppstein You might want to check that |
@nicowilliams - I added the following lines to my private copy of jq.test and ran jqtest successfully. Please feel free to add to
|
The following program performs very nicely with jq 1.5 and jq-1.5rc2-150-g1740fd0 of Jan 19, 2016, but fails to terminate in a reasonable time using the current master (jq-1.5rc2-251-g476b367):
E.g. using jq 1.5:
(My attempts to further bisect have run into some other difficulties....)
The text was updated successfully, but these errors were encountered: