This corrects/normalizes license headers in misc. files, such as
config files, docs, build tools, tests, and externs. This does not
affect the compiled output, and is only done for consistency.
Issue #2638
Change-Id: I9d8da2de55243b08d7df2b743aac73c6f15e858a
This greatly speeds up startup time when running tests on a modern
browser. This change also fixes a bug in one of the tests that only
worked with Babel running.
Change-Id: I1493ef30388c5043dcdf8350bec7817ab5d28d55
The default test timeout is 120 seconds, which makes debugging test
timeouts take a long time. This allows changing the timeout on the
command-line.
Change-Id: Ibb27e35b9ae4b71f192841ecc6ccd90ab652b0cf
Now the spell-checking is run over the scripts too. The spelling
regexes are stored in another file to avoid having them be caught by
the check itself (or needing to whitelist the Python file).
This also fixes another spelling error and some line-length issues.
Change-Id: Ieabef3cf3e46c6dd2cd4341dfc6c158a9d6a50ea
This ensures you spell the browsers correctly when excluding browsers
instead of silently ignoring badly spelled browsers.
Change-Id: I039c4a418f0e716d54daa195588890f37af3bb7a
When running the tests many times with --runs, the specifics of any
failures can be lost in the scrollback buffer of the terminal. It can
be helpful to check the failure rate of a long test run in progress
without waiting for the final report. To this end, this change adds
additional output to show the number of failed runs along the way.
Change-Id: I1b4c6134f35accbe19e99d72a806c70d665bef13
This will make it easier for encoder/packager vendors and other groups
to verify compatibility between Shaka Player and their custom streams.
Change-Id: I601fe4d071cef4d0bcf01b89352a61b9b9d767f0
- Translate uncaught Promise rejections into test failures
(Chrome only until the event is more widely implemented)
- Clean up uncaught Promise rejection caused by exceptions thrown
after destroy() in:
- CastProxy
- CastReceiver
- NetworkingEngine
- StreamingEngine
- Clean up uncaught Promise rejection caused by test cases in:
- CancelableChain unit tests
- DrmEngine unit tests
- StreamingEngine unit and integration tests
- Player unit and integration tests
- Speed up rejection in NetworkingEngine when we should not retry
- Add --delay-tests to test.py, to aid in debugging uncaught
Promise rejections and other types of async test pollution
Closes#1323
Change-Id: I5a8f5702a22430929babeb071bf6650c52c5ad17
In the test launcher, it is useful to resolve the list of default
browsers after parsing command-line arguments. This allows derived
tools to use command-line arguments to influence the set of default
browsers.
Bug: 72452551
Change-Id: I309e48fc3f0335ee6107510fe35ed2d46367e65d
This avoids line-length limits on Windows in the node module's
pass-through shell script.
The long list of files, combined with a node module's bin file,
tripped the Windows command-line length limit of 8k. The transition
to eslint, therefore, broke the Windows build.
Issue #1157Closes#1228
Change-Id: Ie57624efbbbfb4a27035e82ab12e788d18652ae3
Now we can snoop in the karma config and find a list of all usable
browser launchers. This allows us to provide hints for what browsers
could be used.
Change-Id: I7116eb72957c7f8b924380c26c4c66cdca50c0bc
Have you heard? The build/test.py arguments have been driving people
crazy, yes, CRAZY. To help cure the out-of-control insanity that is
sweeping the nation, I have taken our build/test.py and karam.conf.js
scripts and changed how they process command line arguments.
For build/test.py we are now using argparse (standard python library)
to parse the command line arguments. From there we build a JSON
object that is passed to Karma. This allows all command line parsing
to be done in Python and then our Karma conf only needs to read
the settings out of an object.
Fixes: 34107973
Change-Id: Iad631ca18778a031c7ce8bb613c52449069868e3
This reverts commit c950647fdf.
Reason for revert: Reverting this for now as it breaks cross_browser.
Change-Id: I8a2b6bfa007e37674bc2c435fe2fa863ae77a824
Have you heard? The build/test.py arguments have been driving people
crazy, yes, CRAZY. To help cure the out-of-control insanity that is
sweeping the nation, I have taken our build/test.py and karam.conf.js
scripts and changed how they process command line arguments.
For build/test.py we are now using argparse (standard python library)
to parse the command line arguments. From there we build a JSON
object that is passed to Karma. This allows all command line parsing
to be done in Python and then our Karma conf only needs to read
the settings out of an object.
Bug: 34107973
Change-Id: I22f35a4f9bc89cda0d4a07ff030efa6e22467ba3
Rather than using print, use the logging module. This allows embedding
environments to setup logging how they want. This also ensures the logs
are flushed properly.
The prints for check.py, checkversion.py, stats.py, and for the --help
flag will still be printed to stdout since that would be the expected
output location.
Change-Id: I26e1bc866803c42981628c7e62261d13c7b3ff2b
/usr/bin/env python is preferable, since it allows us to support
executable scripts on systems where python is installed in places
other than /usr/bin.
Incidentally, this was the only thing I needed to do to confirm
full build support on Windows, so I'm dropping a TODO about Windows
support for the extern generator.
Change-Id: Ice93174428e0d8015d0a7787f07a17e8ac808dc7
When a program (e.g. Java) cannot be found in the build scripts, it
will now print a more specific error message and quit early to avoid
other confusing messages.
Change-Id: I5f1f26a6c05b8db45355bfbc8d799d603c80c55c
* Node binaries should have .cmd appended to file name.
* htmlhint cannot find .htmlhintrc file.
* Use same python environment for subprocesses.
Closes#526
Change-Id: I6b4c898b39a3e2eb8d808feb2b46b79fba5dc455
Fixes "No changes detected, not building. Use --force to override." when
executing build/all.py and build/test.py with --force.
Change-Id: Ib230b5b21d4f10fa67dd686c90124f51f2b585d4
On versions before v1.3.12, 'npm update' appears to do nothing and
and returns success. This causes the tests to fail if the node
modules are not installed yet. Now it will detect the npm version
and print an error message if it is unsupported.
Closes#318
Change-Id: Iff1db8a6f85d5ce705e5504ee9cb23d2246b87c3
Tests all demo assets through the compiled library. To debug,
use --uncompiled to run them with the uncompiled library.
These new tests are off by default because they use external assets
and run very slowly. Use --external to run these tests.
Change-Id: If1648108dbb9a323d59f6b0e14b4fe6c446a90d2
This expands our list of browser targets using WebDriver and drops
the BrowserStack targets. We will no longer be using BrowserStack.
This also drops xvfb-run for Linux. As we move toward testing
primarily over WebDriver, the overhead of starting an Xvfb is not
necessary.
Change-Id: If2dd26caf3dea88ba39c20644f329451de48c273
Remove the need for --single-run and simplify how the karma command is
found and how the command-line is built.
Change-Id: Ic926219e3100ff043289a1c5f0c224a517b0188e
Firefox stable now supports MP4 on Linux with default flags.
This also updates comments on Firefox and Opera in build/test.py.
Change-Id: I2b7d1696c390f775576a5cca0a24197f8d7f2915
If a user has locally-installed node modules, they should take
precedence over any global installation.
Change-Id: I5b58d910a45d9640146fc8126bbd6ccb7cc43ff6
Joey Parrish
Jacob Trimble
Sandra Lokshina
Aaron Vaage
Chad Assareh