quarantine_zephyr: Enabled zephyr mesh sample again

[m-alperen-sener]

Fixed here: 1883f06

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 7

Inputs:

Sources:

sdk-nrf: PR head: eff7f39a7a31497c54edecd3d27bfecd0bd53737

more details

sdk-nrf:

PR head: eff7f39a7a31497c54edecd3d27bfecd0bd53737
merge base: ae518d055670fcca964fbe0f10809a4dd4481e8b
target head (main): 96683e2782923209e3f4bb9e6e0b48db770afee7
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
✅	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (1)

scripts
│  │ quarantine_zephyr.yaml

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain
• ◻️ Build twister
• ◻️ Integration tests

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-proprietary_esb
  • test-fw-nrfconnect-ps
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread
  • test-fw-nrfconnect-zigbee
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-sidewalk
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[PerMac]

looks like CI error, the run is marked as successful in jenkins, but not on github. cc @jangalda-nsc

[thst-nordic]

looks like CI error, the run is marked as successful in jenkins, but not on github. cc @jangalda-nsc

Run#3 was triggered with 'RUN_DOWNSTREAM' turned off.
We return 'COMPLETED/CANCELED' in this situation to make sure the PR doesn't merge without HW testing.

I've started run#4, it should pass soon with no code changes.

[PerMac]

I guess this must be some error within the workflow/ not synchronized features. I think the idea was that if only quarantine is changed there is no need for downstream jobs
"We return 'COMPLETED/CANCELED' in this situation to make sure the PR doesn't merge without HW testing." maybe this policy should be updated as well?

[DatGizmo]

I guess this must be some error within the workflow/ not synchronized features. I think the idea was that if only quarantine is changed there is no need for downstream jobs "We return 'COMPLETED/CANCELED' in this situation to make sure the PR doesn't merge without HW testing." maybe this policy should be updated as well?

There is a difference between, downstream skipped because they are not needed, and RUN_DOWNSTERAM == false
The first is detected by the system, so success can be sent to GH
The latter is a user input, so we don't know if the downstreams should have been executed, there fore we sent Canceled to prevent the PR from merging.

[m-alperen-sener]

Well I was trying to trigger the tests on twister; what I wanted to do was to run the tests I am enabling. It seems I did something wrong along the way.

Well I have no problem locally when I run the tests. We can merge as it is then.