| Summary: |
We should add IGNORE as an option for the diskmonitor so that a user can override what the system wants to do |
| Product: |
[Build System, Metadata & Runtime] BitBake
|
Reporter: |
brian avery <brian.avery> |
| Component: |
bitbake | Assignee: |
brian avery <brian.avery> |
| Status: |
RESOLVED
NOTABUG
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
poky.bs.watcher, poky.watcher
|
| Version: |
2.2 | |
|
| Target Milestone: |
2.2 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Yes (doc changes required)
|
|---|
We currently only allow "ABORT", "STOPTASKS", "WARN" for actions. This means that even if I know that my mount point is ok, I can't tell the system to leave it alone. We should either allow IGNORE for the action or add a Variable to disable the monitor altogether. To add IGNORE, all we need to do is : change bitbake/lib/bb/monitordisk.py - if action not in ("ABORT", "STOPTASKS", "WARN"): to - if action not in ("ABORT", "STOPTASKS", "WARN", "IGNORE"): Nicely, all of the action dispatch code checks for keyword matches, but we should probably add an: elif action == "IGNORE": pass just to be clear. ----- Why this mattered to me: I'm running on a Docker container inside a VM on MacOSX. My sstate is in a bind (effectively) mounted OSX dir which the container can see. bitbake is unhappy with the inode number; but because of the odd driver being used, that number does not reflect reality. With the explosion of filesystems, I'd prefer to have an override option in case the user does know better.