fix(build): update surefire report processing to handle time format#2962
fix(build): update surefire report processing to handle time format#2962liferoad merged 6 commits intoGoogleCloudPlatform:mainfrom
Conversation
…nd skip on errors Modify sed command to properly handle time format in test reports and add skipSurefireReport configuration to prevent build failures when encountering parsing issues
Summary of ChangesHello @liferoad, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue in the build process related to Surefire report parsing. It modifies the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2962 +/- ##
============================================
- Coverage 50.31% 50.31% -0.01%
+ Complexity 4998 4995 -3
============================================
Files 966 966
Lines 59134 59131 -3
Branches 6440 6440
============================================
- Hits 29756 29753 -3
+ Misses 27274 27272 -2
- Partials 2104 2106 +2
🚀 New features to boost your workflow:
|
|
Re-running the integration test workflow before merging, this PR is a release blocker though |
|
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 914.844 s <<< FAILURE! - in com.google.cloud.teleport.templates.python.PubSubToBigQueryYamlIT |
|
https://pantheon.corp.google.com/cloud-build/builds;region=global/63da88fc-9b25-4d90-8399-3a5cedcc9676;step=0?e=13802955&mods=dm_deploy_from_gcs&project=cloud-teleport-testing seems fine now without using cache. |
...es-maven-plugin/src/main/java/com/google/cloud/teleport/plugin/maven/TemplatesStageMojo.java
Show resolved
Hide resolved
…2962) * fix(build): update surefire report processing to handle time format and skip on errors Modify sed command to properly handle time format in test reports and add skipSurefireReport configuration to prevent build failures when encountering parsing issues * check import jsonschema * use python * use python3 * disable cache * fixed the dockerfile
…oogleCloudPlatform#2962) * fix(build): update surefire report processing to handle time format and skip on errors Modify sed command to properly handle time format in test reports and add skipSurefireReport configuration to prevent build failures when encountering parsing issues * check import jsonschema * use python * use python3 * disable cache * fixed the dockerfile
Before sed:
After sed:
TODO: