-
Notifications
You must be signed in to change notification settings - Fork 4.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
#28472 fix flaky tests in libbeat fmtstr to use time.UTC instead of time.Local #28473
#28472 fix flaky tests in libbeat fmtstr to use time.UTC instead of time.Local #28473
Conversation
…ad of time.Local
💚 CLA has been signed |
This pull request does not have a backport label. Could you fix it @hinchliff? 🙏
NOTE: |
I should be covered under my employer's CCLA. There is a CCLA with Optiv Security that includes me. |
cla/check |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
jenkins run tests |
* upstream/master: [libbeat] Fix add_labels flattening of arrays values (elastic#29211) Change elastic-agent pprof default to false (elastic#29155) elastic#28472 fix flaky tests in libbeat fmtstr to use time.UTC instead of time.Local (elastic#28473) Adopt `parsers` in Filebeat's journald input (elastic#29070) [Elastic Agent] Add process error handling guidelines (elastic#29152) winlogbeat/sys/winevent: use reflect IsZero method (elastic#29190) Remove Journalbeat (elastic#29131) Add note that there is no warranty or support for generator code (elastic#28797) packetbeat: preparation for npcap addition (elastic#29017) Use the generic helper for opening file to read in filestream (elastic#29180) Workflow for macos (elastic#29174) Fix `decode_json_fields` processor to always add error key (elastic#29107)
What does this PR do?
There are four unit tests that seem to be about re-formatting a timestamp in UTC. However, the unit tests generate the expected time using
time.Local
, which produces inconsistent results based on the local timezone used by e.g. the developer. If my understanding of the purpose of the test cases is correct, then usingtime.UTC
should resolve any potential inconsistencies.Why is it important?
Tests should work everywhere.
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Ci/CD tests should pass as normal. You should be able to run the same tests locally on a box that does not use UTC, and have them pass.
Related issues
Use cases
Screenshots
Logs
See ticket #28472