Actions
action #18162
closed[tools][openqa-monitoring] START_AFTER_TEST not found
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
2017-03-30
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
observation¶
[Wed Mar 29 23:20:25 2017] [4347:warn] START_AFTER_TEST=RAID0:64bit not found - check for typos and dependency cycles
[Wed Mar 29 23:56:50 2017] [9214:warn] START_AFTER_TEST=RAID0:64bit not found - check for typos and dependency cycles
[Wed Mar 29 23:57:00 2017] [9214:warn] START_AFTER_TEST=install_only:64bit not found - check for typos and dependency cycles
[Wed Mar 29 23:57:09 2017] [9214:warn] START_AFTER_TEST=install_only:64bit not found - check for typos and dependency cycles
[Wed Mar 29 23:57:10 2017] [8449:warn] START_AFTER_TEST=install_only:64bit not found - check for typos and dependency cycles
[Wed Mar 29 23:57:10 2017] [8449:warn] START_AFTER_TEST=install_only:64bit not found - check for typos and dependency cycles
[Wed Mar 29 23:57:10 2017] [8449:warn] START_AFTER_TEST=install_only:64bit not found - check for typos and dependency cycles
[and many moreā¦]
suggestion¶
Since this is now a known issue and not critical for the work of the server, I'll provide a PR for the logwarn-script of okurz to ignore this warning.
Updated by okurz almost 7 years ago
https://github.com/okurz/openqa_monitoring/pull/9 merged and deployed
Updated by coolo almost 7 years ago
- Project changed from openQA Project to openQA Tests
- Category changed from Regressions/Crashes to Infrastructure
This is not an openQA bug, but a setup failure
Updated by coolo over 5 years ago
- Status changed from New to Resolved
By now we even have test suites that rely on START_AFTER_TEST only creating a warning. I find the warning still relevant in case of typos, but the seen ones are unfortunately expected warnings.
So filtering this, is the right thing to do: resolved
Actions