aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/test/shell
Commit message (Collapse)AuthorAge
* Increase size of //src/test/shell/bazel:maven_testGravatar Damien Martin-Guillerez2015-09-21
| | | | | | | It is timeout flaky. -- MOS_MIGRATED_REVID=103379536
* Remove support for the deprecated include() statement in order to be able to ↵Gravatar Lukacs Berki2015-09-21
| | | | | | | | | separate Skylark from the rest of the code so that Label parsing can be simplified. This is another go at []: now that the tests were fixed in [] and [] it can be submitted again. -- MOS_MIGRATED_REVID=103364881
* Rollback of commit 4e5037520e3067f9d8784e1c59f9545b96111cd4.Gravatar Lukacs Berki2015-09-17
| | | | | | | | | | | | | | | | | *** Reason for rollback *** Broke tests, I mistakenly assumed it was flakiness. *** Original change description *** Remove support for the deprecated include() statement. This is part of the crusade to eliminate as every dependency in Skylark on the rest of the code so that it can be moved deeper in the dependency graph. RELNOTES: The include() statement in BUILD files is not supported anymore. -- MOS_MIGRATED_REVID=103284257
* Remove support for the deprecated include() statement.Gravatar Lukacs Berki2015-09-17
| | | | | | | | | This is part of the crusade to eliminate as every dependency in Skylark on the rest of the code so that it can be moved deeper in the dependency graph. RELNOTES: The include() statement in BUILD files is not supported anymore. -- MOS_MIGRATED_REVID=103279943
* Deflake maven_testGravatar Kristina Chodorow2015-09-16
| | | | | | | | Change the test to only starts up the fileserver when needed, not before each test case, to prevent timeouts. -- MOS_MIGRATED_REVID=103216306
* Add a maven_server ruleGravatar Kristina Chodorow2015-09-16
| | | | | | | | This will also be used for authentication, but that has not been implemented yet. -- MOS_MIGRATED_REVID=103194964
* Parses the correct values of SDK, Platform and XCode version numbers when ↵Gravatar Anastasios Kakalis2015-09-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | generating the environment's plist. The script no longer parses the values from the Platform's Info.plist, which contained the values used to compile the Platform's library *itself*, rather than the values of the actual running environment. Also the BuildMachineOSBuild is being read from the sw_version, rather than the Xcode's plist, and the DTSDKBuild is determined by the plist under sdk-path. An example environment.plist: { BuildMachineOSBuild = 14F27; DTCompiler = "com.apple.compilers.llvm.clang.1_0"; DTPlatformBuild = 12H141; DTPlatformVersion = "8.4"; DTSDKBuild = 12H141; DTXCodeBuild = 6E35b; DTXcode = 0640; } -- MOS_MIGRATED_REVID=103079006
* Increase size of test timeout flaky on ci.bazel.ioGravatar Damien Martin-Guillerez2015-09-11
| | | | | | | | | See http://ci.bazel.io/job/Bazel/PLATFORM_NAME=darwin-x86_64/104/console process_wrapper_test is actually failing inside the timeout test so it is probably don't have enough time too. -- MOS_MIGRATED_REVID=102841728
* Fix BUILD_SCM_* being looked for in the stable status file and test it.Gravatar Brian Silverman2015-09-11
| | | | | | | | | | | | They're actually in the volatile status file, which is where it seems like they belong. Fixes #216. -- Change-Id: Ibec7737538ff5c1003b61d1bd3396948c61886de Reviewed-on: https://bazel-review.googlesource.com/1950 MOS_MIGRATED_REVID=102791996
* sandbox: Add a test to make sure opting-out via local=1 works.Gravatar Philipp Wollermann2015-09-09
| | | | | -- MOS_MIGRATED_REVID=102651489
* Deactivate flaky test //src/test/shell/bazel:generate_workspace_testGravatar Damien Martin-Guillerez2015-09-08
| | | | | | | Tracking issue: #432 -- MOS_MIGRATED_REVID=102592907
* sandbox: Show user-friendly mount paths in the namespace-sandbox debug log.Gravatar Philipp Wollermann2015-09-08
| | | | | | | Improvement for #424. -- MOS_MIGRATED_REVID=102566748
* Display TIMEOUT for test that times outGravatar Damien Martin-Guillerez2015-09-08
| | | | | | | | | Previously the timing out information wasn't propagated to the user, leading to a wrong FAILED message whereas the test was timing out. -- MOS_MIGRATED_REVID=102535481
* Increase size of some testGravatar Damien Martin-Guillerez2015-09-08
| | | | | | | They are regularly timing out. -- MOS_MIGRATED_REVID=102534770
* Remove BUILD.glob and incorporate the necessary filegroups into the ↵Gravatar Lukacs Berki2015-09-08
| | | | | | | | | android_{ndk,sdk}_repository rules themselves. This is to that the Android tests also work on OS X (otherwise, we'd end up creating a file called "BUILD" in its root, which doesn't work, because it already has a directory called "build") -- MOS_MIGRATED_REVID=102484286
* Shard and increase size of //src/test/shell/bazel:local_repository_testGravatar Damien Martin-Guillerez2015-09-08
| | | | | | | This test is timeout flaky on ci.bazel.io -- MOS_MIGRATED_REVID=102477110
* Move generate_workspace to src/toolsGravatar Kristina Chodorow2015-09-04
| | | | | | | | Seems like a better location for it (easier for people to run than src/main/java/com/google/devtools/build etc). -- MOS_MIGRATED_REVID=102354250
* Make the Android integration test verify if STL still works for our Android ↵Gravatar Lukacs Berki2015-09-04
| | | | | | | rules. -- MOS_MIGRATED_REVID=102336906
* Setup the ci build to test also Android tests when availableGravatar Damien Martin-Guillerez2015-09-04
| | | | | | | | | | | | With this script, the easiest way to run the test suite is now: bash -c "export ANDROID_SDK_PATH=$HOME/bin/android-sdk-linux; \ export ANDROID_NDK_PATH=$HOME/bin/android-ndk-r10e; \ source ./scripts/ci/build.sh; \ bazel_build output/ci" -- MOS_MIGRATED_REVID=102334239
* Make android_binary use a constant, hard-coded, checked-in debug key. Gravatar Lukacs Berki2015-09-04
| | | | | | | This is because apkbuilder uses $HOME/.android/debug.keystore by default, which does not exist when running within the sandbox, thus, it always generates a new debug key, and thus, "adb install -r" doesn't work. -- MOS_MIGRATED_REVID=102331570
* Add an integration test for Android rules.Gravatar Lukacs Berki2015-09-03
| | | | | | | Currently only building them is tested, not running them or mobile-install, but it's still a good start. -- MOS_MIGRATED_REVID=102237496
* Make Python rules work in external repositories.Gravatar Lukacs Berki2015-09-03
| | | | | | | | | This is necessary to make mobile-install work using an android_local_tools_repository. Fixes #415. -- MOS_MIGRATED_REVID=102235910
* Change URLs to bazelbuildGravatar Kristina Chodorow2015-09-01
| | | | | -- MOS_MIGRATED_REVID=102022958
* Fix breakage of bazel_sandboxing_test:test_sandbox_block_filesystem.Gravatar Philipp Wollermann2015-08-31
| | | | | | | | This failed, because if the Bazel workspace is in your home directory, obviously /home gets created in the sandbox. -- MOS_MIGRATED_REVID=101921457
* Fixes #400: Linux sandboxing and relative symbolic links.Gravatar Philipp Wollermann2015-08-28
| | | | | | | Symlink resolution did not work in all cases and broke ./compile.sh on certain Linux distros. -- MOS_MIGRATED_REVID=101775459
* Fix $(location //external:some_tool) expansion for genrules.Gravatar Brian Silverman2015-08-28
| | | | | | | | | | | | Previously, targets in "tools" of genrules could only be expanded in $(location)s as the target of the bind. This is another part of fully fixing #90. -- Change-Id: I91444fbfe551b651c46811014639f08f779c70aa Reviewed-on: https://bazel-review.googlesource.com/#/c/1750/ MOS_MIGRATED_REVID=101760690
* Make dangling symlinks in external repositories work to some degree.Gravatar Lukacs Berki2015-08-28
| | | | | | | | | | | | | | | | | This seems to be the least insane approach within the following boundaries: - Skyframe apparently doesn't allow GlobFunction to recover if FileFunction had already raised an exception that Skyframe knows about (this is somewhat surprising) - I didn't want to change FileFunction not to throw an exception for dangling symlinks because this part of the code is scary - I didn't want to revert to Skyframe-based symlink resolution for symlinks in immutable directories because that would be a performance hit - I didn't want to write yet another symlink resolver and the two existing ones (FileSystem#resolveSymlinks() and and FileFunction#getSymlinkTargetRootedPath()) don't work: the former cannot resolve just one level of symlinks and the latter cannot do its job without adding Skyframe dependencies I had to put in a placeholder value for realRootedPath when the FileValue represents a dangling symlink, because FileStateValue.create() relies on the symlink target being different than the symlink itself. RELNOTES: -- MOS_MIGRATED_REVID=101756189
* Make load() work in remote repositories too.Gravatar Lukacs Berki2015-08-27
| | | | | | | | | Previously, load() always looked up .bzl files in the main repository. Ideally, it would just take a label and then it would work by default, but for the time being, this quick fix will do. I had to put in an evil hack to make load() statements work in the prelude, because we currently have no way to distinguish load() statements from the prelude and from the BUILD file. Again, a proper label-based load() would solve this. -- MOS_MIGRATED_REVID=101677502
* Port to FreeBSD.Gravatar Doug Rabson2015-08-26
| | | | | | | -- Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7 Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840 MOS_MIGRATED_REVID=101462155
* Execute spawns inside sandboxes to improve hermeticity (spawns can no longer ↵Gravatar Philipp Wollermann2015-08-26
| | | | | | | | | | | | use non-declared inputs) and safety (spawns can no longer affect the host system, e.g. accidentally wipe your home directory). This implementation works on Linux only and uses Linux containers ("namespaces"). The strategy works with all actions that Bazel supports (C++ / Java compilation, genrules, test execution, Skylark-based rules, ...) and in tests, Bazel could successfully bootstrap itself and pass the whole test suite using sandboxed execution. This is not the default behavior yet, but can be activated explicitly by using: bazel build --genrule_strategy=sandboxed --spawn_strategy=sandboxed //my:stuff -- MOS_MIGRATED_REVID=101457297
* Mark flaky test external_integration_test as manual.Gravatar Philipp Wollermann2015-08-26
| | | | | -- MOS_MIGRATED_REVID=101456399
* Make Bazel handle visibility through //external: labels correctly: ↵Gravatar Lukacs Berki2015-08-25
| | | | | | | | | //external: targets can depend on anything and visibility is checked a the edges incoming to said labels. Fixes #388. -- MOS_MIGRATED_REVID=101363086
* Do not consider //external: a repository-local reference.Gravatar Lukacs Berki2015-08-25
| | | | | | | Fixes #360. -- MOS_MIGRATED_REVID=101360551
* Prepare our tests that can't run under sandboxing to explicitly request a ↵Gravatar Philipp Wollermann2015-08-24
| | | | | | | non-sandboxing spawn strategy (this is a no-op until sandboxing is there). -- MOS_MIGRATED_REVID=101219854
* Fix a missing dependency in a Skylark rule in local_repository_test.sh.Gravatar Philipp Wollermann2015-08-24
| | | | | -- MOS_MIGRATED_REVID=101216575
* Add missing redirect to $TEST_log in our test-setup.sh.Gravatar Philipp Wollermann2015-08-24
| | | | | -- MOS_MIGRATED_REVID=101210076
* Find parent and submodule definitions before fully resolving a pomGravatar Kristina Chodorow2015-08-21
| | | | | | | | | | | | | | | | | | The Maven API has two options for parsing pom files: getting the "raw model" (which parses the pom to ensure it is correct, but doesn't do any resolution nor variable substitution) and getting the "effective model," which does all resolution. Before this CL, generate_workspace was just getting the effective model immediately, which is easily foiled by having an artifact that depends on a "sibling" (the parent cannot be resolved until the siblings are and the siblings can only be resolved if they happen to arrive in the right order). This changes the code to get the raw models first to get locations of all artifacts, then fully resolve them. This fixes #383. -- MOS_MIGRATED_REVID=101129094
* Add profile support to generate_workspaceGravatar Kristina Chodorow2015-08-20
| | | | | | | Fixes one part of #383. -- MOS_MIGRATED_REVID=100925734
* Properly extract symlinks from tar archives.Gravatar Brian Silverman2015-08-13
| | | | | | | | | | This includes rewriting absolute symlink targets by interpreting them relative to the root of the archive. -- Change-Id: Ia6b8accd6fed3205809d621ed8984058d3b5a356 Reviewed-on: https://bazel-review.googlesource.com/#/c/1780 MOS_MIGRATED_REVID=100478005
* Split out some sections of external_integration_testGravatar Kristina Chodorow2015-08-12
| | | | | | | Also added a little more error message to the fetch test. -- MOS_MIGRATED_REVID=100475915
* Use full package identifier in containing package checkGravatar Kristina Chodorow2015-08-12
| | | | | | | Otherwise a @x//a/b will be seen as crossing @y//a's package boundary. -- MOS_MIGRATED_REVID=100465538
* Fix test flakinessGravatar Kristina Chodorow2015-08-11
| | | | | | | Also improves the error message when no repositories can be found. -- MOS_MIGRATED_REVID=100307390
* Add custom repositories to the WORKSPACE fileGravatar Kristina Chodorow2015-08-06
| | | | | | | | If a non-Maven-Central repository was used to access an artifact, record that in the generated WORKSPACE file. -- MOS_MIGRATED_REVID=100058489
* Add output_dir option and improve repository handlingGravatar Kristina Chodorow2015-08-06
| | | | | | | | | | | I finally worked out how to get a simple test maven repository working, so added back integration testing. This removes the dependency on Aether and just uses the maven model lib to resolve dependencies, which seems to work better in the face of custom repositories. -- MOS_MIGRATED_REVID=100031414
* Follow redirects in HTTP-based remote repositories.Gravatar Damien Martin-Guillerez2015-08-04
| | | | | | | | The content is checked for determinism using SHA-256 sum. Following redirection allows for using mirror based service. -- MOS_MIGRATED_REVID=99819904
* Rollback of commit da3cb806351e929becef19652c65d39efa61b9d9.Gravatar Googler2015-08-04
| | | | | | | | | | | | | *** Reason for rollback *** Breaking builds. [] *** Original change description *** RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change. -- MOS_MIGRATED_REVID=99742398
* RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into ↵Gravatar Googler2015-08-04
| | | | | | | bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change. -- MOS_MIGRATED_REVID=99521906
* Make OutputFileConfiguredTarget create artifacts that are consistent with ↵Gravatar Lukacs Berki2015-07-30
| | | | | | | | | RuleContext#internalCreateOutputArtifact(). Fixes #351. -- MOS_MIGRATED_REVID=99478770
* Fix middleman conflicts in external repositories by appending the package pathGravatar Damien Martin-Guillerez2015-07-30
| | | | | | | Fixes #341. -- MOS_MIGRATED_REVID=99390495
* Check that most output artifacts are under a directory determined by the ↵Gravatar Lukacs Berki2015-07-29
| | | | | | | | | repository and package of the rule being analyzed. Currently this directory is PACKAGE for rules in the main repository and external/REPOSITORY_NAME/PACKAGE for rules in other repositories. This is a plan to fix #293. Ideally, we would simply make it impossible to create artifacts not under that location, but in practice, we cannot do that because some rules do want to do this, mostly those that are already problematic due to shared actions. So the battle plan is to eliminate as many calls to AnalysisEnvironment.getDerivedArtifact() as I possibly can and audit the rest. -- MOS_MIGRATED_REVID=99351151
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-04 16:30:30 +0000