-
Notifications
You must be signed in to change notification settings - Fork 6
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
add support for run-bug-run runbugrun #39 WIP #166
base: master
Are you sure you want to change the base?
Conversation
Hi @cadddr ! There is currently a failure in the RunBugRun tests. Seems to be an error in loading the dataframe. |
Since this isn’t file not found, could be a version/deprecation issue with
pandas? What version is being installed, so I can reproduce? Thanks
…On Mon, Dec 2, 2024 at 10:28 PM André Silva ***@***.***> wrote:
Hi @cadddr <https://github.com/cadddr> !
There is currently a failure in the RunBugRun tests.
See
https://github.com/ASSERT-KTH/repairbench-framework/actions/runs/12126690735/job/33810455158?pr=166#step:13:337
Seems to be an error in loading the dataframe.
—
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWMCVO4CSBZWZCTHME2NUT2DVTUBAVCNFSM6AAAAABQ3CF6BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJTHA2TCNZQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
When you run Right now that is |
I also have pandas==2.2.3 In the log there is a deprecation warning for using path string as argument to read_json. Wrapped into file stream. Hopefully this passes, otherwise, not sure how to debug this. |
Now the problem seems to be related with a FileNotFound. |
My path: Double checked commands in setup.sh download and unpack the file correctly:
Why is the working dir in the log |
Trying to fix path, and rebased to latest master. Let's see if we can fix this. |
Fixed the file not found problem by changing the benchmark directory to a submodule. We not get another error, during the execution of a RunBugRun bug. |
Thanks for fixing the paths. Bug-related errors do not consistently reproduce since we're taking 3 bugs from an unordered dict. After fixing the order (and running 20 bugs instead of 3), I'm getting the first failure fail on print (result) print (test_output) |
Thanks for noticing the randomness bug! I fixed the issue for all benchmarks and rebased this PR with the latest commits from master. For the problem of comparing outputs, the straigh-forward solution would be to eval the strings and compare the values. |
#39 WIP