11-lorawan: mark task06 as local only #240
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mark task06 as local only since it will work with chirpstack but not ttn.
|
I'm fine with it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mark task06 as local only since it will work with chirpstack(some versions) but not ttn. It can be removed once RIOT-OS/RIOT#16962 is addressed. It should keep release-tests outputs clean IMO.
I'm also pushing for this because it seems that the failing test messes with the following iterations of the LoraWAN tests (something in the TTN state for that node). I'm able to fix it by resetting the node test: e.g.:
ttn-lw-cli end-devices reset release-tests eui-70b3d57ed00463e7-otaa, but I haven't found an mqtt interface for this. I'm not sure why this happens either, but I can't investigate this further ATM.