Switch BundleExtractToSpecificPath and BundleAndRun to using built test assets#92024
Conversation
The `TestWith*Paths` tests were just running a self-contained application by invoking it using relative/absolute paths on the command line. There was no difference in what it was doing for single-file.
|
Tagging subscribers to this area: @agocke, @vitek-karas, @VSadov Issue Details
Fixes #91039
|
vitek-karas
left a comment
There was a problem hiding this comment.
Looks good. Just curious: Do we understand how it fixes the "No space left on the device" failure?
|
I believe it was simply because we were copying so much around - a full self-contained application copied for every test case and then each test case would generate a bundle. While we were cleaning up, it was only after all the test cases were run (explicitly cleaning up the copies after each test case would probably also have fixed it). This change (and the others switching to use the pre-built assets / |
BundleExtractToSpecificPathandBundleAndRuntests use built test asset project (HelloWorld)BundleExtractToSpecificPathtests explicitly includemockcoreclrso that it will have native binaries to bundleBundleAndRun.TestWith*Paths*testsBundlerConsistencyTests- trying to separate tests targeting theBundlerAPI from tests targeting single-file activationFixes #91039