Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flaky tests #511

Open
Danielius1922 opened this issue Aug 30, 2023 · 2 comments
Open

Flaky tests #511

Danielius1922 opened this issue Aug 30, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Danielius1922
Copy link
Member

Danielius1922 commented Aug 30, 2023

Reset at 3. 11. 2023:

Unit tests:

plgd/device tests:

    getOwnerships_test.go:41: 
        	Error Trace:	/go/src/github.com/plgd-dev/device/client/core/getOwnerships_test.go:41
        	            				/go/src/github.com/plgd-dev/device/client/core/getOwnerships_test.go:81
        	Error:      	Not equal: 
        	            	expected: true
        	            	actual  : false
        	Test:       	TestGetOwnerships
    getDevice_test.go:78: 
        	Error Trace:	/go/src/github.com/plgd-dev/device/client/core/getDevice_test.go:78
        	            				/usr/local/go/src/runtime/asm_amd64.s:1594
        	Error:      	Received unexpected error:
        	            	(NotFound) no response from the device with ip 10.1.0.11
        	Test:       	TestClientGetDeviceParallel

plgd/hub tests:

@Danielius1922 Danielius1922 added the bug Something isn't working label Aug 30, 2023
@Danielius1922 Danielius1922 self-assigned this Aug 30, 2023
@jkralik
Copy link
Member

jkralik commented Sep 18, 2023

coverage: 62.9% of statements in ./...
=== RUN   TestClientGetDeviceByIPWithIP4
--- FAIL: TestClientGetDeviceByIPWithIP4 (10.00s)
panic: (Internal) no response from the device d3cea882-9a26-4c35-404f-5086237a24a3 [recovered]
	panic: (Internal) no response from the device d3cea882-9a26-4c35-404f-5086237a24a3

@jkralik
Copy link
Member

jkralik commented Nov 29, 2023

5: [OC 2023-11-29T10:54:21.800334Z] ERROR: oc_swupdate.c:974 <oc_swupdate_dump>: swupdate: cannot dump data for device(0) to store: error(-2)
5: [OC 2023-11-29T10:54:22.006930Z] WARNING: oc_certs_validate.c:56 <validate_x509v1_fields>: certificate not yet active
5: /home/runner/work/iotivity-lite/iotivity-lite/security/unittest/obt_certstest.cpp:626: Failure
5: Value of: flags
5:   Actual: 512
5: Expected: 0
5: [OC 2023-11-29T10:54:22.007015Z] ERROR: oc_store.c:76 <oc_sec_dump_doxm>: cannot dump doxm to storage: error(-2)

512 flag means that certificate will be valid in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants