-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🐛 Bug fix on java validator for failed test due to $DEFAULT at rule evaluation #27842
🐛 Bug fix on java validator for failed test due to $DEFAULT at rule evaluation #27842
Conversation
Hey @ampproject/wg-caching, these files were changed:
|
validator/java/src/main/java/dev/amp/validator/css/Canonicalizer.java
Outdated
Show resolved
Hide resolved
@GeorgeLuo @honeybadgerdontcare @Gregable A couple questions about these tests:
|
@rsimha yes, I can run a clean pull and see if tests fail, due to discrepancies with my local repos. I might ask to enable debugging for the build if it works from my local environment, just for a little visibility. |
Thanks for the help. If you're developing on Linux or MacOS, you should be able to run these tests by checking out the For local debugging, you'll see more logging by changing Line 74 in 62248e7
|
Thank you! My maven build with a clean env was successful. When trying with gulp it actually looks it's hanging after the resource files are pulled down, with "Did you forget to signal async completion". It doesn't look like the tests are even ran. This happens in the case when the files already exist as well. Either a resolution comes from the gulp job or our shell script to fetch resources needs modification. Have you seen this class of error before? |
I'm unfamiliar with this. Can you temporarily increase the verbosity in your PR and see what the Travis logs reveal? |
I can do that. here is what I'm observing
I added the "done copying" to the end of amphtml/validator/java/src/main/bin/copyValidatorJavaSource.sh It hangs after that. So it looks like it's not returning from that script gracefully, or whatever is calling that is not returning gracefully. What is the path from "gulp validator-java" to the shell script? I see it referenced in BUILD and nowhere else. But I'm not sure who is handling that BUILD file. It seems to be bazel. |
When I run the build and test script, the ./build.sh step takes 30 seconds or so, successfully though. Could there be some kind of timeout when bringing travis into the equation? Curiously, the output here proceeds through to the test output, displaying failure. Has any of the build logic been changed since? |
…m/GeorgeLuo/amphtml into GeorgeLuo-catchup-default-at-rule
…m/GeorgeLuo/amphtml into GeorgeLuo-catchup-default-at-rule
change tagchowder
It worked courtesy of @nhant01. bazel was silently failing during the build phase because we only updated the tagchowder library in maven and didn't do the same in the bazel WORKSPACE. we'll probably need to figure out how to splay these types of errors. I'm going to clean up some of the echos and such. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glad you were able to figure this out. Now that tests are green, I'm going to merge this in order to unblock all the java validator upgrade PRs.
These tests are still failing during CI. See logs. Any idea what's going on? /invite @GeorgeLuo @nhant01 |
An invitation to join |
unclear but pulling the latest proto seems to have introduced compilation failure cases to do with css specs. I imagine we're in a state where the .proto under java validator compiled fine (outdated), but the protoascii has introduced new models and flows. I'll get the engine changes in and then see about the tests. |
Thanks @GeorgeLuo. Meanwhile, we have a large backlog of package upgrade PRs for the Java validator that are all blocked by the test failures. Since Under normal circumstances, once the file is up to date, there will be far fewer upgrade PRs each week, and they can be individually tested and merged as they appear. Edit: I've filed #27939 to track this work. |
business logic change + test for fix + update tagchowder to newer version