Vinicius Felizardo would like Owners Override to review this change.
[infra] Updates nuc_env to nuc7_env and nuc11_env.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Commit-Queue | +1 |
foreach(env, environments) {
Vinicius FelizardoWould it be possible to add some validation here that if a test has NUC7 included in its envs, it also has NUC11?
Something like:
```
has_nuc7 = false
has_nuc11 = false
foreach(env, environments) {
if (env.dimensions.device_type = "Intel NUC Kit NUC7i5DNHE") {
has_nuc7 = true
}
if (env.dimensions.device_type = "Intel NUC Kit NUC11TNHv5") {
has_nuc11 = true
}
...
}
// (not sure if this is the correct value to check, but we need some
// sort of exemption for this test)
if (name != "core-tests-hpet") {
assert(!has_nuc7 || has_nuc11, "every test that runs on nuc7 must also run on nuc11")
}
```
Vinicius FelizardoDone
FYI I cant add this check in this CL because of the skew issue of other CLs that will only include nuc7 for now. However, they are actually including nuc11 too given the existing logic to replace nuc_env with nuc7 + nuc11.
Therefore, when I get to delete this hack of adding nuc7 + nuc11, I can also add the check here: https://paste.googleplex.com/5374925699547136
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
foreach(env, environments) {
Vinicius FelizardoWould it be possible to add some validation here that if a test has NUC7 included in its envs, it also has NUC11?
Something like:
```
has_nuc7 = false
has_nuc11 = false
foreach(env, environments) {
if (env.dimensions.device_type = "Intel NUC Kit NUC7i5DNHE") {
has_nuc7 = true
}
if (env.dimensions.device_type = "Intel NUC Kit NUC11TNHv5") {
has_nuc11 = true
}
...
}
// (not sure if this is the correct value to check, but we need some
// sort of exemption for this test)
if (name != "core-tests-hpet") {
assert(!has_nuc7 || has_nuc11, "every test that runs on nuc7 must also run on nuc11")
}
```
Vinicius FelizardoDone
FYI I cant add this check in this CL because of the skew issue of other CLs that will only include nuc7 for now. However, they are actually including nuc11 too given the existing logic to replace nuc_env with nuc7 + nuc11.
Therefore, when I get to delete this hack of adding nuc7 + nuc11, I can also add the check here: https://paste.googleplex.com/5374925699547136
skew issue of other repositories*
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
File not formatted properly.
Run the following to format:fx format-code --changed-lines --files=zircon/system/utest/device-enumeration/boards/nuc7.cc
I run this but no changes take effect: https://paste.googleplex.com/5051469229457408
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Commit-Queue | +2 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |