Re: [Wireshark-dev] pipeline failed
On 10/28/21 12:29 PM, Zoran Bošnjak wrote: Hello wireshark developers, please advice how do I reproduce the pipeline build failure in local environment. In particular, this one: https://gitlab.com/zoranbosnjak/wireshark/-/pipelines/397393242 The following problems are reported on merge request: 1. Checking cache for Code Checks + Clang Warnings-master... FATAL: file does not exist I have no idea, which file does not exist. The file that doesn't exist is GitLab CI's job cache[1]. The job cache lets you share files between builds, and many of our jobs use it to store ccache data. I'm not sure why it prints a red "FATAL" message; it's not fatal. Other than disabling the cache it's not something we have direct control over. 2. GCC warnings Based on error output, I have found some unit tests that indeed fail and I will try to fix them. But I am getting a different error locally. I would appreciate an exact command, to reproduce the same error. The relevant errors are near the bottom on line 62 and 63: License 'UNKNOWN' for 'tools/asterix/update-specs.py' is not allowed. License 'UNKNOWN' for 'tools/asterix/README.md' is not allowed. FAILED The first failure is valid. You should add an "SPDX-License-Identifier:" line to update-specs.py. The second failure is a false positive. A fix for that is inbound in MR 4889. [1]https://docs.gitlab.com/ee/ci/caching/ ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] pipeline failed
Hello wireshark developers, please advice how do I reproduce the pipeline build failure in local environment. In particular, this one: https://gitlab.com/zoranbosnjak/wireshark/-/pipelines/397393242 The following problems are reported on merge request: 1. Checking cache for Code Checks + Clang Warnings-master... FATAL: file does not exist I have no idea, which file does not exist. 2. GCC warnings Based on error output, I have found some unit tests that indeed fail and I will try to fix them. But I am getting a different error locally. I would appreciate an exact command, to reproduce the same error. Zoran ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Issue with the NR-RRC Di-sector
Hi, Le jeu. 28 oct. 2021 à 17:45, Chilla Sunil Kumar-Trainee < csku...@parallelwireless.com> a écrit : > Hi, > > I had an issue with RRC messages. > >1. In F1Setup Request message , it is not Showing the complete message >information. SIB1 Information is missing and showing that *[Expert >Info (Warning/Undecoded): something unknown here [too long >integer(per_normally_small_nonnegative_whole_number)]]* >*[something unknown here [too long >integer(per_normally_small_nonnegative_whole_number)]]* >*[Severity level: Warning]* >*[Group: Undecoded].* Please find this in the attached snapshot – F1 >setup issue.png > > We cannot provide any support with a screenshot only. It could be that your SIB1 message is not properly encoded of a bug in Wireshark. > >1. >2. I am not able to see some RRC messages like *NAS Security mode >Command Complete* and *AS Security mode Command.* Please find the >attached snapshot - RRC.png > > If you use ciphering, this is expected as Wirehark does not include the (potentially patented) code to perform deciphering (that would be UE specific also due to the different ciphering key). > >1. >2. Not able to find the message transmission in between gNB_DU and UE >(Over the Air messages) - Please find this in the attached snapshot –need >rrc.png > > See the response above. > >1. > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
