You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long storry short: for testing the ability to do pub get and pub build we copy in the packages and test them if they have a pubspec yaml file.
If you copy a symlink, like the one added in r38788, without -L to cp you will just get the relative symlink copied in, which will, of course, not work.
I generally think it is a bad idea to add symlinks to the repo, we have had enough issues with the ones for packages/pub
I will, for now, mark the test as skip in pkgbuild, but I think we should instead just add bin/runtime/vmservice to the location where we look for packages. I will make a cl for that
The text was updated successfully, but these errors were encountered:
For background, the symlink was added in r38788 to enable tests in dart/tests/standalone/vmservice/* (for now, only allocations_test) to import the "observatory" package, whose source we maintain in dart/runtime/bin/vmservice/client.
If we had support for multiple pkg-root paths, an alternative would have been to add dart/runtime/bin/vmservice/client for these specific tests only (so far, there's only one, but we'll want to use this for most of them eventually).
Long storry short: for testing the ability to do pub get and pub build we copy in the packages and test them if they have a pubspec yaml file.
If you copy a symlink, like the one added in r38788, without -L to cp you will just get the relative symlink copied in, which will, of course, not work.
I generally think it is a bad idea to add symlinks to the repo, we have had enough issues with the ones for packages/pub
I will, for now, mark the test as skip in pkgbuild, but I think we should instead just add bin/runtime/vmservice to the location where we look for packages. I will make a cl for that
The text was updated successfully, but these errors were encountered: