-
Notifications
You must be signed in to change notification settings - Fork 349
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
Create toShortSignature() in Method.java #454
Create toShortSignature() in Method.java #454
Conversation
Hi, |
Actually this is leading error after repeat() method in String
…On Fri, 24 May, 2024, 7:44 pm cyrille-artho, ***@***.***> wrote:
Hi,
This PR does not fix any additional failing test. We had 14 failing tests
before and now. Can you please check again?
—
Reply to this email directly, view it on GitHub
<#454 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVOVF5DWYY4HH7JSFI6DE3ZD5DNRAVCNFSM6AAAAABIHSUGRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGYZTQMBVGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Fixing this might solve the 4-5 failing test cases.
…On Fri, 24 May, 2024, 7:59 pm Ekla, ***@***.***> wrote:
Actually this is leading error after repeat() method in String
On Fri, 24 May, 2024, 7:44 pm cyrille-artho, ***@***.***>
wrote:
> Hi,
> This PR does not fix any additional failing test. We had 14 failing tests
> before and now. Can you please check again?
>
> —
> Reply to this email directly, view it on GitHub
> <#454 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVOVF5DWYY4HH7JSFI6DE3ZD5DNRAVCNFSM6AAAAABIHSUGRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGYZTQMBVGY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
How many failing tests do you have locally? The patch for |
Currently there is 14 failing test cases. The method repeat() solved two failing test case reducing total failed test cases to 14. No, there is not any test cases that failed before and now work. Here is the link to see the changes https://github.com/eklaDFF/jpf-core ///////////////////////////////////////////// |
In that case, is this patch a first step for a later fix of something? If that's the case, we can wait with a PR until the next change fixes something. |
Yeh, I think we should move forward with this.
Please review the changes in GitHub repo attached above and let me know
what you think.
…On Fri, 24 May, 2024, 11:35 pm cyrille-artho, ***@***.***> wrote:
In that case, is this patch a first step for a later fix of something? If
that's the case, we can wait with a PR until the next change fixes
something.
—
Reply to this email directly, view it on GitHub
<#454 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASVOVF7PIAZXUKYGYNBWCPTZD56QJAVCNFSM6AAAAABIHSUGRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZQGEYDGNRQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
A. Error report without implementing
B. Error report after implementing
In A, our error is reported while it is at static block and in B our error is reported way ahead. |
Thank you for your explanation. I'll merge this as a partial fix for that test case (and I don't see a need to create a smaller test case where only the first function is needed). |
Created
toShortSignature()
inMethod.java