We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a developer, I want to resolve warnings and errors in builds so that I do not become desensitized to them and miss real problems in the noise.
In our Run Tests section of build process, we get several warnings, including 404. A snippet of these warnings follows:
16 10 2020 11:42:12.902:WARN [middleware:karma]: Invalid file type (browserify), defaulting to js. HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 0 of 434 SUCCESS (0 secs / 0 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 1 of 434 SUCCESS (0 secs / 0 secs) 16 10 2020 11:42:14.625:WARN [web-server]: 404: /v1/rad-analyst?api_key=12345&per_page=1&committee_id=12345 HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 2 of 434 SUCCESS (0 secs / 0 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 3 of 434 SUCCESS (0 secs / 0 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 4 of 434 SUCCESS (0 secs / 0 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 5 of 434 SUCCESS (0 secs / 0 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 6 of 434 SUCCESS (0 secs / 0.003 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 7 of 434 SUCCESS (0 secs / 0.004 secs) HeadlessChrome 78.0.3882 (Linux 0.0.0): Executed 8 of 434 SUCCESS (0 secs / 0.004 secs)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
User story
As a developer, I want to resolve warnings and errors in builds so that I do not become desensitized to them and miss real problems in the noise.
Summary
In our Run Tests section of build process, we get several warnings, including 404. A snippet of these warnings follows:
The text was updated successfully, but these errors were encountered: