Closed pdreiter closed 5 years ago
Looking at the source code, we appear to be considering context
for test-harness
.
https://github.com/squaresLab/BugZoo/blob/master/bugzoo/core/test.py#L117
https://github.com/squaresLab/BugZoo/blob/master/bugzoo/mgr/container.py#L395
And if we look into the log files for the fauxware
scenario, we can see that the correct execution context is being used:
DEBUG:bugzoo.mgr.container.24856cc1-cf88-41b5-b073-9175c207fddd:2019-05-17 10:42:23,287: executing command "./test.sh p3"
DEBUG:bugzoo.mgr.container.24856cc1-cf88-41b5-b073-9175c207fddd:2019-05-17 10:42:23,287: using execution context: /experiment/src
Hi Pemma,
I'm not sure if you still need these? It sounds like you figured out that cached coverage files were the issue.
In any case, I used bug build
and bug validate
to generate those logs.
Cheers, Chris
On Mon, 20 May 2019 at 14:13, pdreiter notifications@github.com wrote:
Can I get the command line[s] you used, so I can duplicate this?
On Fri, May 17, 2019 at 07:44 Chris Timperley notifications@github.com wrote:
Closed #331 https://github.com/squaresLab/BugZoo/issues/331.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/squaresLab/BugZoo/issues/331?email_source=notifications&email_token=AG3UEHC2DAUDRAWQYHZCIF3PV3AELA5CNFSM4HNQJ6YKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORQF4QXY#event-2349582431 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AG3UEHD7YKPNNOKU6BSNQIDPV3AELANCNFSM4HNQJ6YA
.
-- -pemma
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/squaresLab/BugZoo/issues/331?email_source=notifications&email_token=AAD72KA2OGLTVKQXKABGIIDPWLS3BA5CNFSM4HNQJ6YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVZURYI#issuecomment-494094561, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD72KCP3VS4NFHWZNJRUG3PWLS3BANCNFSM4HNQJ6YA .
From conversation here: https://gitq.com/squaresLab/Darjeeling/topics/3/incremental-debug-for-new-test-cases
context
intest-harness
is being ignored.