-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[extension/storage/dbstorage] Flaky Test #11451
Comments
Yes, I also stumbled into it. looking |
I did too. I could not make sense of that failure. Good luck Dmitrii. |
Got another occurence https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/3379452850/jobs/5611039833. Looks like another module got stanza dependancy. Re-running it for now |
The warnings seem to be related to mattn/go-sqlite3#803 |
@dmitryax the run you reference shows this error:
Is that correct? It doesn't seem this like this failure is related to dbstorage. What am I missing? |
No, the error is the same as posted here initially
|
Actually you're right. I got confused by the warnings. Sorry. I'll need to create another issue |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
These warnings are annoying. Do we want them fixed as part of this issue? Close and open a new one? It appears this issue is no longer occurring. |
@atoulme, a clean issue sounds reasonable to me. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I had followed up with #19152, and am not sure we still see those warnings since I updated the version. I'll take a look. |
I don't see warnings again, and the failure doesn't occur anymore. Good to close this. |
…19421 (#28680) **Description:** Update go-sqlite3 on cmd/configschema (same as #19421) to start re-enabling tests currently being skipped on Windows, see #28679. **Link to tracking Issue:** First part of #28679 Related to #11451 **Testing:** Local tests of `cmd/configschema`. **Documentation:** N/A
…pen-telemetry#19421 (open-telemetry#28680) **Description:** Update go-sqlite3 on cmd/configschema (same as open-telemetry#19421) to start re-enabling tests currently being skipped on Windows, see open-telemetry#28679. **Link to tracking Issue:** First part of open-telemetry#28679 Related to open-telemetry#11451 **Testing:** Local tests of `cmd/configschema`. **Documentation:** N/A
…ssue)" This reverts commit aca655a.
…ssue)" This reverts commit 7d494a2.
…pen-telemetry#19421 (open-telemetry#28680) **Description:** Update go-sqlite3 on cmd/configschema (same as open-telemetry#19421) to start re-enabling tests currently being skipped on Windows, see open-telemetry#28679. **Link to tracking Issue:** First part of open-telemetry#28679 Related to open-telemetry#11451 **Testing:** Local tests of `cmd/configschema`. **Documentation:** N/A
…ixes (open-telemetry#28682) **Description:** Part 2 of open-telemetry#28679 these are the tests that can be re-enabled without requiring any code changes after open-telemetry#28680 is merged. **Link to tracking Issue:** Related to open-telemetry#28679
…n Windows (#29532) **Description:** Last part to re-enable all Windows tests disabled due to issue #11451. Notes: * The default test timeout is not enough for the `cmd` GROUP on CI and it was increased to 1200s just for this group on Windows, the default stays at 300s (which was also enough for my local run). * The `fileexporter` life cycle test indicates an issue that shouldn't affect most usages of the collector: if the same configuration is used to export multiple signals it opens one file handle for each signal but just closes the one of them at shutdown (the helper only executes the shutdown for the one signal). This is an issue for the test because during cleanup the testing attempts to delete the test folder and there are still handles open to the file that lives inside it. This shouldn't be a problem for collector users. That said the exporter should close all file handles on shutdown. I will take look at what can be done to correct this behavior. * Fixed a minor typo on the receivers test that affected many lines. **Link to tracking Issue:** Fix #28679 - last part. **Testing:** Local run and GH CI on my fork with `Run Windows` label. **Documentation:** N/A
Observed here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/7009845542?check_suite_focus=true#step:7:1415
The text was updated successfully, but these errors were encountered: