| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118500217
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=116801400
|
|
|
|
|
|
|
|
| |
A failing test could use a previous run's timestamp, resulting in awkward
negative times, especially in the case of sub-second runs.
--
MOS_MIGRATED_REVID=111345693
|
|
|
|
|
|
|
| |
will get rid of all the "ghost flakes" where tests crashed with no apparant reason printed into our logs. Now a stack trace is printed and an easy to understand failure reason, too.
--
MOS_MIGRATED_REVID=110142957
|
|
|
|
|
|
|
| |
such.
--
MOS_MIGRATED_REVID=109991616
|
|
|
|
|
|
|
|
|
|
| |
On calls to fail, the failure message is written to $TEST_TMPDIR/__fail. This
is cat-ed to get the message, but if the test exited without calling fail then
an annoying 'cat: blah/blah/blah/__fail: No such file or directory' message is
printed. This throws out the error message if the cat fails.
--
MOS_MIGRATED_REVID=109896051
|
|
|
|
|
|
|
| |
I have no idea why this is a problem: apparently, postincrement fails (but only the first one, so theoretically, changing only that line would be enough), preincrement works and i=$(( $i + 1 )) also works. The documentation of bash is of no help, I checked the file on the off chance that there are weird Unicode characters on that line (or where i is set) and I had no more ideas after (other than there being a bug in bash)
--
MOS_MIGRATED_REVID=108774915
|
|
|
|
|
|
|
|
|
| |
a sparse array with holes. This appears to be due to the sub shell launching of the tests. By using FUNCNAME as our count of stack frames, and "ignoring" the holes, we get much better stack output on the Mac. Previously we were just erroring out.
RELNOTES:none
--
MOS_MIGRATED_REVID=107255705
|
|
|
|
|
|
|
|
|
| |
No need to worry about escaping any perl-related chars.
RELNOTES:
--
MOS_MIGRATED_REVID=104207407
|
|
|
|
|
|
|
| |
the test log output we would fails to report the tests that failed (and show the whole raw output instead). This is because we inline a text inside a perl program but we were only escaping } character.
--
MOS_MIGRATED_REVID=104102328
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
|
|
|
|
| |
Bazel test environment set -eu and when giving an argument
to the test suite, the for loop matching for test to run
was returning an error, resulting in the whole test to fails.
--
MOS_MIGRATED_REVID=103727268
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
|
| |
If the set_up method fails then the start timestamp file is not created and
the start timestamp argument to in the timestamp computation function will
be undefined leading to an unwanted error if set -u is activated.
--
Change-Id: I188e9302bbdb1049dc317765eaa653bafc5a51de
MOS_MIGRATED_REVID=92946436
|
|
|
|
|
|
|
| |
This makes installation easier for systems that don't come with bc installed (e.g., Travis CI and Ubuntu Vivid Vervet).
--
MOS_MIGRATED_REVID=91297054
|
|
|
|
|
|
|
|
|
| |
Test sharding run the same "bazel" test in parallel. The
unittest.bash framework then distribute the test functions
equally on the various shard.
--
MOS_MIGRATED_REVID=90990754
|
|
|
|
|
|
|
|
| |
Bazel tests set -u and that prevented selection of test to run in a test
suite with --test_arg.
--
MOS_MIGRATED_REVID=90497934
|
|
|
|
|
|
|
|
| |
In OS X date does not support the %N formatting, so using python
to print out date instead
--
MOS_MIGRATED_REVID=89303112
|
|
|
|
|
|
|
|
|
|
|
| |
This change allows tests to fails silently and have the test output by
function preserved.
Without it, a script that would set +e and have a failing command would
generate a failure on the fetching of the failure message, making the
whole test suite fails.
--
MOS_MIGRATED_REVID=89120786
|
|
This is part of the shell test infrastructure for Bazel. It creates
test suites in Bazel shell. Handling the test ouputs efficiently for
making test summaries.
--
MOS_MIGRATED_REVID=88929067
|