Travis CI failing `should properly compose sourcemaps when multiple transformations are chained` test
See original GitHub issueHere’s the error I see in the most recent build:
gulp-google-[secure]: TypeError: Cannot read property 'b' of null
at l6b (/home/travis/build/google/[secure]/node_modules/[secure]-npm/packages/google-[secure]-js/jscomp.js:8755:375)
at zxd (/home/travis/build/google/[secure]/node_modules/[secure]-npm/packages/google-[secure]-js/jscomp.js:8175:160)
at h2b (/home/travis/build/google/[secure]/node_modules/[secure]-npm/packages/google-[secure]-js/jscomp.js:6209:103)
at Z1b (/home/travis/build/google/[secure]/node_modules/[secure]-npm/packages/google-[secure]-js/jscomp.js:8416:290)
which causes a test failure
1) gulp-google-[secure]
javascript version
should properly compose sourcemaps when multiple transformations are chained:
Uncaught Error: gulp-google-[secure]: Compilation errors occurred
at CompilationStream._compilationComplete (lib/gulp/index.js:256:28)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Common Build Problems - Travis CI Docs
A very common cause when a test is suddenly breaking without any major code changes involved is a change in upstream dependencies. This...
Read more >@jest/source-map | Yarn - Package Manager
Jest will set process.env.NODE_ENV to 'test' if it's not set to something else. You can use that in your configuration to conditionally setup...
Read more >rollup changelog
Fix a situation where invalid code was rendered when dynamically importing a module with synthetic named exports when preserving modules (#3738) ...
Read more >Mapping Crime: Principle and Practice
using crime mapping technology, we hope this guide will spark ideas about new ways to use it. Jeremy Travis. Director. National Institute of...
Read more >Best Practices and Common Mistakes with Travis CI ...
For simple changes like these, add “[ci skip]” to your commit message, and Travis will automatically skip that build. The other common reason...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve debugged the sourcemap issue some more. Here’s the stack trace causing a test failure w/ a pretty-printed GWT compiler:
Here’s the compiled
$getSourceMapping
method:The stack trace points to the last line in the function,
implying that
source
is null.This function corresponds to
getSourceMapping
inCompiler.java
: https://github.com/google/closure-compiler/blob/4bf54b232b13162f6c621b2d1f12cddab5b00701/src/com/google/javascript/jscomp/Compiler.java#L2871https://github.com/google/closure-compiler/commit/dac995ac563bfe3170280899112699845768e135 introduced a reference to
source
in the return for that function without first checking that it’s non-null. Probablysource
was already null in the GWT compiled test before that commit, but it just didn’t matter earlier.I don’t know why it’s only null in the GWT tests though. That might be an unrelated bug?
Bradford pointed out that prior to https://github.com/google/closure-compiler/commit/dac995ac563bfe3170280899112699845768e135 the Travis build was failing with what looks like a timeout.