-
Notifications
You must be signed in to change notification settings - Fork 41
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
Just a test of current CI: empty commit to test CI #308
Conversation
OK we have reproduced test failure on main with no changes! Annoying! I wonder what changed since last succesful test runs. The error is somehow only in Error seems to be on all browser tests, a browser console error (hooray for browser console errors included in test output) that says:
I wonder if some JS code is getting run twice? I will try to reproduce locally and diagnose and fix. |
have succesfully reproduced locally. not yet debugged or diagnosed, tricky to figure out what's up with propshaft. |
OK in generated .internal_test_app application.js there is indeed a duplicate:
So have to figure out what's generating that and fix it! Maybe some version of BL 7.x started adding something not previously added. |
Based on run history, seems build worked for this cell with BL 8.6.1, but broke with BL 8.7.0. (it actually failed in a PR we merged anyway recently, not sure why we did that!). Haven't yet reproduced locally. |
OK, I think our generator for BL 8 fixup is no longer necessary in BL 8.7.0 and in fact causes problems. Good that BL 8.7.0 changed to make our extra generator fixup not necessary, but, phew! Will PR separately. |
@jrochkind Thanks so much for tracking all that down. The test matrix all passed in the original PR #305 which was issued Dec 3, so that would've been using BL 8.6.1. Once the PR was merged to |
And actually causes problems in 8.7.0, trying to do something that was already done. See #308
Fixed in #309 |
No description provided.