Skip to content
New issue

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

Enable rerunning of tests failing with minification turned on #8013

Closed
ricowind opened this issue Jan 21, 2013 · 4 comments
Closed

Enable rerunning of tests failing with minification turned on #8013

ricowind opened this issue Jan 21, 2013 · 4 comments
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@ricowind
Copy link
Contributor

Since it can be hard to figure out if a test failed because of a newly introduced issue or because of an error in minification we should rerun tests failing with minification turned on, and provide developers with this information (i.e., if the test also fails without minification)

@ricowind
Copy link
Contributor Author

Issue #7928 has been merged into this issue.


cc @mkustermann.

@peter-ahe-google
Copy link
Contributor

I have written some code to decode source maps. We might be better off using that to pre-process stack traces.

@ricowind
Copy link
Contributor Author

Peter: Is that source map decoding ready for usage?


Removed Area-Test label.
Added Area-Infrastructure label.

@mkustermann
Copy link
Member

cc @whesse.
Removed the owner.

@ricowind ricowind added Type-Defect area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. labels Jan 13, 2014
@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed triaged labels Feb 29, 2016
@matanlurey matanlurey added the closed-obsolete Closed as the reported issue is no longer relevant label Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

5 participants