Skip to content

Failing some filesystem tests for a specific tool-chain #7439

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.

Sign up for GitHub

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

Jump to bottom
Closed
aashishc1988 opened this issue Jul 6, 2018 · 6 comments
Closed

Failing some filesystem tests for a specific tool-chain #7439

aashishc1988 opened this issue Jul 6, 2018 · 6 comments
Labels
type: bug

Comments

@aashishc1988
Copy link
Contributor

aashishc1988 commented Jul 6, 2018 •
edited by 0xc0170
Loading

Description

  • Type: Bug
  • Priority: Major

Bug

Target
KL25Z

Toolchain:
GCC_ARM
(6-2017-q2-update)

mbed-os sha:
13dcef6

Tests we are failing:
features-tests-filesystem-util_block_device
features-tests-filesystem-mbr_block_device
features-tests-filesystem-heap_block_device
features-tests-filesystem-buffered_block_device (although i think this test was added as a part of that merge).

Steps to reproduce
mbed test -m KL25Z -t GCC_ARM -n features-tests-filesystem-util_block_device -v

log snippet

> 
mbedgt:

 greentea test automation tool ver. 1.4.0
mbedgt: using multiple test specifications from current directory!
        using 'BUILD\tests\KL25Z\GCC_ARM\test_spec.json'
mbedgt: detecting connected mbed-enabled devices...
mbedgt: entering global resource manager mbed-ls dummy mode!
        adding dummy platform 'KL25Z'
mbedgt: detected 1 device
        +---------------+----------------------+-------------+-------------+-----------+
        | platform_name | platform_name_unique | serial_port | mount_point | target_id |
        +---------------+----------------------+-------------+-------------+-----------+
        | KL25Z         | KL25Z[0]             | DUMMY       | DUMMY       | DUMMY     |
        +---------------+----------------------+-------------+-------------+-----------+
mbedgt: processing target 'KL25Z' toolchain 'GCC_ARM' compatible platforms... (note: switch set to --parallel 1)
        +---------------+----------------------+-------------+-------------+-----------+
        | platform_name | platform_name_unique | serial_port | mount_point | target_id |
        +---------------+----------------------+-------------+-------------+-----------+
        | KL25Z         | KL25Z[0]             | DUMMY:9600  | DUMMY       | DUMMY     |
        +---------------+----------------------+-------------+-------------+-----------+
mbedgt: test case filter (specified with -n option)
        features-tests-filesystem-util_block_device
        test filtered in 'features-tests-filesystem-util_block_device'
mbedgt: running 1 test for platform 'KL25Z' and toolchain 'GCC_ARM'
        use 1 instance of execution threads for testing
mbedgt: checking for 'host_tests' directory above image directory structure
        'host_tests' directory not found: two directory levels above image path checked
mbedgt: selecting test case observer...
        calling mbedhtrun: mbedhtrun -m KL25Z -p DUMMY:9600 -f "BUILD/tests/KL25Z/GCC_ARM/features/TESTS/filesystem/util_block_device/util_block_device.bin" --grm raas_client:10.118.12.40:8000 -C 4 --sync 5 -P 60
mbedgt: mbed-host-test-runner: started
[1530916015.09][HTST][INF] host test executor ver. 1.3.1
[1530916015.09][HTST][INF] copy image onto target... SKIPPED!
[1530916015.09][HTST][INF] starting host test process...
[1530916015.80][CONN][INF] starting connection process...
[1530916015.80][CONN][INF] notify event queue about extra 60 sec timeout for serial port pooling
[1530916015.80][CONN][INF] initializing global resource mgr listener...
[1530916015.80][HTST][INF] setting timeout to: 60 sec
[1530916015.89][GLRM][INF] remote resources initialization: remote(host=10.118.12.40, port=8000)
[1530916015.90][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916015.90][urllib3.connectionpool]http://10.118.12.40:8000 "POST /login HTTP/1.1" 200 213
[1530916015.90][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916015.91][urllib3.connectionpool]http://10.118.12.40:8000 "GET /socket.io/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6InVzZXIiLCJncm91cCI6InVzZXIiLCJpYXQiOjE1MzA5MTYwMTUsImV4cCI6MTUzMTUyMDgxNX0.cc_AGaogEAUMHxeTgXV2GRczmdm9htjCGsaTn1Pg5t8&EIO=3&transport=polling&t=1530916015901-0 HTTP/1.1" 200 101
[1530916015.91][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916015.92][urllib3.connectionpool]http://10.118.12.40:8000 "GET /resource HTTP/1.1" 200 8312
[1530916015.92][GLRM][INF] remote resources count: 6
[1530916015.92][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916015.93][urllib3.connectionpool]http://10.118.12.40:8000 "GET /resource HTTP/1.1" 200 8312
[1530916015.93][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916015.93][urllib3.connectionpool]http://10.118.12.40:8000 "PUT /resource/0200000024404e45001d3018ffff000fffffffff97969900/allocate HTTP/1.1" 200 1813
[1530916015.94][GLRM][INF] remote resources flashing with 'BUILD/tests/KL25Z/GCC_ARM/features/TESTS/filesystem/util_block_device/util_block_device.bin'...
[1530916027.19][GLRM][INF] opening connection to platform at baudrate='9600'
[1530916027.19][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916027.39][urllib3.connectionpool]http://10.118.12.40:8000 "PUT /resource/0200000024404e45001d3018ffff000fffffffff97969900/connect HTTP/1.1" 200 15
[1530916027.40][GLRM][INF] remote resources reset...
[1530916029.65][GLRM][TXD] mbedmbedmbedmbedmbedmbedmbedmbedmbedmbed
[1530916029.65][CONN][INF] sending up to 5 __sync packets (specified with --sync=5)
[1530916029.65][CONN][INF] sending preamble '60cbae3b-66ab-4bf8-b516-3b3480b11411'
[1530916029.66][GLRM][TXD] {{__sync;60cbae3b-66ab-4bf8-b516-3b3480b11411}}
[1530916030.83][CONN][RXD] mbedmbedmbedmbedmbedmbedmbedmbed
[1530916030.83][CONN][INF] found SYNC in stream: {{__sync;60cbae3b-66ab-4bf8-b516-3b3480b11411}} it is #0 sent, queued...
[1530916030.83][CONN][INF] found KV pair in stream: {{__version;1.3.0}}, queued...
[1530916030.85][HTST][INF] sync KV found, uuid=60cbae3b-66ab-4bf8-b516-3b3480b11411, timestamp=1530916030.832000
[1530916030.85][HTST][INF] DUT greentea-client version: 1.3.0
[1530916030.93][CONN][RXD] >>> Running 3 test cases...
[1530916030.93][CONN][INF] found KV pair in stream: {{__timeout;10}}, queued...
[1530916030.93][CONN][INF] found KV pair in stream: {{__host_test_name;default_auto}}, queued...
[1530916030.94][HTST][INF] setting timeout to: 10 sec
[1530916030.94][HTST][INF] host test class: '<class 'mbed_host_tests.host_tests.default_auto.DefaultAuto'>'
[1530916030.94][HTST][INF] host test setup() call...
[1530916030.94][HTST][INF] CALLBACKs updated
[1530916030.94][HTST][INF] host test detected: default_auto
[1530916031.03][CONN][INF] found KV pair in stream: {{__testcase_name;Testing slicing of a block device}}, queued...
[1530916031.03][CONN][INF] found KV pair in stream: {{__testcase_name;Testing chaining of block devices}}, queued...
[1530916031.13][CONN][RXD]
[1530916031.13][CONN][INF] found KV pair in stream: {{__testcase_name;Testing profiling of block devices}}, queued...
[1530916031.23][CONN][RXD] >>> Running case #1: 'Testing slicing of a block device'...
[1530916031.24][CONN][INF] found KV pair in stream: {{__testcase_start;Testing slicing of a block device}}, queued...
**mbedgt: :104::FAIL: Expected 0 Was -4001**
[1530916031.34][CONN][RXD] :104::FAIL: Expected 0 Was -4001
[1530916031.34][CONN][INF] found KV pair in stream: {{__testcase_finish;Testing slicing of a block device;0;1}}, queued...
[1530916031.44][CONN][RXD] >>> 'Testing slicing of a block device': 0 passed, 1 failed with reason 'Assertion Failed'
[1530916031.44][CONN][RXD]
[1530916031.54][CONN][RXD] >>> Test cases: 0 passed, 1 failed with reason 'Assertion Failed'
[1530916031.54][CONN][RXD] >>> TESTS FAILED!
[1530916031.54][CONN][INF] found KV pair in stream: {{__testcase_summary;0;1}}, queued...
[1530916031.64][CONN][INF] found KV pair in stream: {{max_heap_usage;0}}, queued...
[1530916031.64][CONN][INF] found KV pair in stream: {{reserved_heap;0}}, queued...
[1530916031.64][CONN][INF] found KV pair in stream: {{end;failure}}, queued...
[1530916031.64][CONN][INF] found KV pair in stream: {{__exit;0}}, queued...
[1530916031.64][HTST][ERR] orphan event in main phase: {{max_heap_usage;0}}, timestamp=1530916031.637000
[1530916031.64][HTST][ERR] orphan event in main phase: {{reserved_heap;0}}, timestamp=1530916031.637000
[1530916031.64][HTST][INF] __exit(0)
[1530916031.64][HTST][INF] __notify_complete(False)
[1530916031.64][HTST][INF] __exit_event_queue received
[1530916031.64][HTST][INF] test suite run finished after 0.70 sec...
[1530916031.64][CONN][INF] received special event '__host_test_finished' value='True', finishing
[1530916031.64][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916031.67][urllib3.connectionpool]http://10.118.12.40:8000 "PUT /resource/0200000024404e45001d3018ffff000fffffffff97969900/disconnect HTTP/1.1" 200 2
[1530916031.68][urllib3.connectionpool]Starting new HTTP connection (1): 10.118.12.40:8000
[1530916034.93][urllib3.connectionpool]http://10.118.12.40:8000 "PUT /resource/0200000024404e45001d3018ffff000fffffffff97969900/release HTTP/1.1" 200 66
[1530916034.95][HTST][INF] CONN exited with code: 0
[1530916034.95][HTST][INF] Some events in queue
[1530916034.95][HTST][INF] stopped consuming events
[1530916034.95][HTST][INF] host test result() call skipped, received: False
[1530916034.95][HTST][INF] calling blocking teardown()
[1530916034.95][HTST][INF] teardown() finished
[1530916034.95][HTST][INF] {{result;failure}}
mbedgt: retry mbedhtrun 1/1
mbedgt: ['mbedhtrun', '-m', 'KL25Z', '-p', 'DUMMY:9600', '-f', u'"BUILD/tests/KL25Z/GCC_ARM/features/TESTS/filesystem/util_block_device/util_block_device.bin"', '--grm', 'raas_client:10.118.12.40:8000', '-C', '4', '--sync', '5', '-P', '60'] failed after 1 count
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'FAIL'
mbedgt: test on hardware with target id: DUMMY
mbedgt: test suite 'features-tests-filesystem-util_block_device' ..................................... FAIL in 20.56 sec
        test case: 'Testing chaining of block devices' ............................................... SKIPPED in 0.00 sec
        test case: 'Testing profiling of block devices' .............................................. SKIPPED in 0.00 sec
        test case: 'Testing slicing of a block device' ............................................... FAIL in 0.10 sec
mbedgt: test case summary: 0 passes, 1 failure
mbedgt: utest test case summary mismatch: utest reported passes and failures miscount!
        reported by utest: passes = 0, failures 1)
        test case result count: passes = 0, failures 3)
mbedgt: all tests finished!
mbedgt: shuffle seed: 0.8261063699
mbedgt: test suite report:
+---------------+---------------+---------------------------------------------+--------+--------------------+-------------+
| target        | platform_name | test suite                                  | result | elapsed_time (sec) | copy_method |
+---------------+---------------+---------------------------------------------+--------+--------------------+-------------+
| KL25Z-GCC_ARM | KL25Z         | features-tests-filesystem-util_block_device | FAIL   | 20.56              | default     |
+---------------+---------------+---------------------------------------------+--------+--------------------+-------------+
mbedgt: test suite results: 1 FAIL
mbedgt: test case report:
+---------------+---------------+---------------------------------------------+------------------------------------+--------+--------+---------+--------------------+
| target        | platform_name | test suite                                  | test case                          | passed | failed | result  | elapsed_time (sec) |
+---------------+---------------+---------------------------------------------+------------------------------------+--------+--------+---------+--------------------+
| KL25Z-GCC_ARM | KL25Z         | features-tests-filesystem-util_block_device | Testing chaining of block devices  | 0      | 0      | SKIPPED | 0.0                |
| KL25Z-GCC_ARM | KL25Z         | features-tests-filesystem-util_block_device | Testing profiling of block devices | 0      | 0      | SKIPPED | 0.0                |
| KL25Z-GCC_ARM | KL25Z         | features-tests-filesystem-util_block_device | Testing slicing of a block device  | 0      | 1      | FAIL    | 0.1                |
+---------------+---------------+---------------------------------------------+------------------------------------+--------+--------+---------+--------------------+
mbedgt: test case results: 1 FAIL / 2 SKIPPED
mbedgt: completed in 23.45 sec
mbedgt: exited with code 1

[ ] Question
[ ] Enhancement 
[X ] Bug
@ciarmcom
Copy link
Member

ciarmcom commented Jul 6, 2018

ARM Internal Ref: MBOTRIAGE-1111

@davidsaada
Copy link
Contributor

davidsaada commented Jul 11, 2018 •
edited
Loading

@aashishc1988 #7465 Should fix this problem. However, our CI doesn't have the KL25Z board, so I can't confirm it. Can you confirm this PR fixes the problem?
In addition, I suspect that tests-mbed_platform-error_handling may be failing as well (before the fix). Can you check it too?

@aashishc1988
Copy link
Contributor Author

@davidsaada , I checked the PR and we are now passing all those tests. :)
Also, the test tests-mbed_platform-error_handling was passing even before the fix, so I am not sure if that raises more concerns or not.

@davidsaada
Copy link
Contributor

@aashishc1988 Thanks for confirming. As for the error handling test - it doesn't raise any concerns. It failed on another board, the same way the tests pointed out in this PR did. Just wanted to make sure this PR fixed the failure if it occurred on your board as well.

@davidsaada davidsaada mentioned this issue Jul 13, 2018
Merged
@davidsaada
Copy link
Contributor

This can be closed now that #7465 was merged.

@aashishc1988
Copy link
Contributor Author

I pulled in the merge and verified the fix again. Closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@0xc0170 @ciarmcom @davidsaada @aashishc1988