| Summary: | When running testimage test_parselogs failed (oeqa.runtime.parselogs.ParseLogsTest) Volume was not properly unmounted. Some data may be corrupt. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Francisco Pedraza <francisco.j.pedraza.gonzalez> | ||||
| Component: | bsps-meta-yocto | Assignee: | Saul Wold <sgw> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | Francisco Pedraza <francisco.j.pedraza.gonzalez> | ||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | benjamin.esquivel | ||||
| Version: | 2.1 | ||||||
| Target Milestone: | 2.1 M4 | ||||||
| Hardware: | NUC | ||||||
| OS: | x86_64 | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Found by QA test) | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
Francisco it looks like some of the latest bugs you filed are related with IO (xorg bug also has IO errors in the log). Can we try to reproduce this bug at another setup? also, what is the reproducibility of this bug? (In reply to comment #1) > Francisco it looks like some of the latest bugs you filed are related with > IO (xorg bug also has IO errors in the log). Can we try to reproduce this > bug at another setup? also, what is the reproducibility of this bug? Hi, this was tested on LAVA server, I just follow instructions to raise this one. However I can reproduce it from my end. Good to know, thanks for the info This was observed once on LAVA and I wonder if there was a corrupt image that time. We have not seen anything like this since or on other hardware, so closing this as a corrupt image issue. Please reopen if this is reproducible with additional details about the image. Indeed Saul, when I saw the logs it was looking a lot like an issue specific to the setup. |
Created attachment 3096 [details] logs Central error: [ 7.014585] udevd[309]: inotify_add_watch(6, /dev/loop0, 10) failed: No such file or directory STATUS: FAILED BUILD: 2.1_M3.RC2: 21823cb466e79540567ad1a43ae6f93d850e4057 ENVIRONMENT: genericx86-64 on NUC STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored. EXPECTED OUTCOME: No errors or fails should be present in logs