[QUESTION] How to finetune wmt22-comet-da and have results scaled to 0-1 range

I am trying to fine-tune the wmt22-comet-da model on new DA data, using its checkpoint and the configs available in the configs/ folder here. I know that this model scales the result scores between 0 and 1, but after fine-tuning, the new fine-tuned model generates negative scores as well, similarly to the older COMET models.
My main question is, where exactly is the configuration I should change for the model to scale the results like wmt22-comet-da does? I haven't been able to find that in the code. My configs are exactly the same as those in configs/ except for filepaths and the checkpoint to load.

Yep, Julia you are right. You need first to rescale the data to be between 0 and 1.
The rescaling I used was actually borrowed from BLEURT. The rescaling is the following:

Find a reasonable "min value". This is done by finding all annotations with more than 1 annotator where all annotators agreed that the score was 0. Then your "min_value" is the average z-score for those segments.
Find a reasonable "max value". This is done by finding all annotations with more than 1 annotator where all annotators agreed that the translation is perfect (100 score). Then your "max_value" is the average z-score for those segments.
apply a min_max_scaler to your data and truncate every score above 1 and bellow 0.

This rescaling won't impact your model correlations and your model will output scores in that range.


robots

Add project robots so pages can be crawled and indexed; required for SEO

This is not required because https://www.palladiumhotelgroup.com/robots.txt will apply


mec15xxevb_assy6853:running tests/kernel/sched/schedule_api/ failed

Describe the bug
running tests/kernel/sched/schedule_api/ error, it showed me assertion failed.
To Reproduce
Steps to reproduce the behavior:
sanitycheck --hardware-map ~/mec1.file  --device-testing  -T tests/kernel/sched/schedule_api/
see error
START - test_slice_reset
PASS - test_slice_reset

===================================================================
START - test_slice_scheduling
AB
AB
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
A
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
FAIL - test_slice_scheduling

==================================================================
START - test_priority_scheduling
AB
AB
AB
AB
AB
PASS - test_priority_scheduling

===================================================================
START - test_wakeup_expired_timer_thread
PASS - test_wakeup_expired_timer_thread

===================================================================
START - test_user_k_wakeup
PASS - test_user_k_wakeup

===================================================================
START - test_user_k_is_preempt
PASS - test_user_k_is_preempt

===================================================================
Test suite threads_scheduling failed.

===================================================================
PROJECT EXECUTION FAILED

Environment (please complete the following information):
OS: Fedora28
Toolchain: Zephyr-sdk-0.11.3
Commit ID: 122bc38fad

The same test fails for me with the current master (6a15118937a817968701b386b3f3c4b47879bde3) on the efm32pg_stk3402a board (ubuntu 18.04, zephyr sdk 0.11.1):
$ sanitycheck -p efm32pg_stk3402a -v --device-testing --device-serial /dev/ttyACM1 -s tests/kernel/sched/schedule_api/kernel.scheduler

...

$ cat .../handler.log

...

START - test_slice_reset
PASS - test_slice_reset
===================================================================
START - test_slice_scheduling
ABCDEFGHI
AB
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
C
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
D
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
E
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
F
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
G
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
H
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
I
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
A
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
FAIL - test_slice_scheduling
===================================================================
START - test_priority_scheduling
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
PASS - test_priority_scheduling

The test tests/kernel/sched/schedule_api/kernel.scheduler.multiq fails in the same way.

The same test fails for me with the current master (6a15118) on the efm32pg_stk3402a board (ubuntu 18.04, zephyr sdk 0.11.1):
$ sanitycheck -p efm32pg_stk3402a -v --device-testing --device-serial /dev/ttyACM1 -s tests/kernel/sched/schedule_api/kernel.scheduler

...

$ cat .../handler.log

...

START - test_slice_reset
PASS - test_slice_reset
===================================================================
START - test_slice_scheduling
ABCDEFGHI
AB
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
C
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
D
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
E
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
F
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
G
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
H
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
I
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
A
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
FAIL - test_slice_scheduling
===================================================================
START - test_priority_scheduling
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
PASS - test_priority_scheduling

The test tests/kernel/sched/schedule_api/kernel.scheduler.multiq fails in the same way.

Thanks for that data. At least, I see both boards are Cortex M4, so it can help me to investigate a root cause.

I don't see that bug happens on the Microchip board using the latest commit
sanitycheck --hardware-map ~/mec1.file --device-testing -T tests/kernel/sched/schedule_api/ -vv
34cf1c74c21b10acfbc6504cd9bc212317c726d0
For the efm32pg_stk3402a I don't have that hardware, could you check that test again @chrta ? If you still see the bug for your board, please open new issue. I will close that one.

INFO    - JOBS: 8
DEBUG   - Reading test case configuration files under /home/ztest/work/zephyrpro                                                                                ject/zephyr/tests/kernel/sched/schedule_api...
DEBUG   - scanning /home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/sche                                                                                dule_api
DEBUG   - Found possible test case in /home/ztest/work/zephyrproject/zephyr/test                                                                                s/kernel/sched/schedule_api
DEBUG   - Reading platform configuration files under /home/ztest/work/zephyrproj                                                                                ect/zephyr/boards...

DEBUG   - Found platform configuration /home/ztest/work/zephyrproject/zephyr/scr                                                                                ipts/sanity_chk/boards/unit/unit_testing/unit_testing.yaml
DEBUG   - platform filter: ['mec15xxevb_assy6853']
DEBUG   -     arch_filter: None
DEBUG   -      tag_filter: None
DEBUG   -     exclude_tag: None
INFO    - Building initial testcase list...
INFO    - 4 test configurations selected, 0 configurations discarded due to filt                                                                                ers.

Device testing on:

| Platform            | ID       | Serial device   |
|---------------------|----------|-----------------|
| mec15xxevb_assy6853 | FT9FPJYP | /dev/ttyUSB2    |

INFO    - Adding tasks to the queue...
DEBUG   - Running cmake on /home/ztest/work/zephyrproject/zephyr/tests/kernel/sc                                                                                hed/schedule_api for mec15xxevb_assy6853
DEBUG   - Calling cmake with arguments: ['-B/home/ztest/work/zephyrproject/zephy                                                                                r/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.schedule                                                                                r.multiq_no_timeslicing', '-S/home/ztest/work/zephyrproject/zephyr/tests/kernel/                                                                                sched/schedule_api', '-DEXTRA_CFLAGS="-Werror"', '-DEXTRA_AFLAGS="-Wa,--fatal-wa                                                                                rnings', '-DEXTRA_LDFLAGS="-Wl,--fatal-warnings"', '-GUnix Makefiles', '-DCONF_F                                                                                ILE=prj_multiq.conf', '-DOVERLAY_CONFIG=/home/ztest/work/zephyrproject/zephyr/sa                                                                                nity-out/mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.scheduler.mu                                                                                ltiq_no_timeslicing/sanitycheck/testcase_extra.conf', '-DBOARD=mec15xxevb_assy68                                                                                53']
DEBUG   - Running cmake on /home/ztest/work/zephyrproject/zephyr/tests/kernel/sc                                                                                hed/schedule_api for mec15xxevb_assy6853
DEBUG   - Calling cmake with arguments: ['-B/home/ztest/work/zephyrproject/zephy                                                                                r/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.schedule                                                                                r.multiq', '-S/home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/schedule_                                                                                api', '-DEXTRA_CFLAGS="-Werror"', '-DEXTRA_AFLAGS="-Wa,--fatal-warnings', '-DEXT                                                                                RA_LDFLAGS="-Wl,--fatal-warnings"', '-GUnix Makefiles', '-DCONF_FILE=prj_multiq.                                                                                conf', '-DOVERLAY_CONFIG=/home/ztest/work/zephyrproject/zephyr/sanity-out/mec15x                                                                                xevb_assy6853/tests/kernel/sched/schedule_api/kernel.scheduler.multiq/sanitychec                                                                                k/testcase_extra.conf', '-DBOARD=mec15xxevb_assy6853']
DEBUG   - Running cmake on /home/ztest/work/zephyrproject/zephyr/tests/kernel/sc                                                                                hed/schedule_api for mec15xxevb_assy6853
DEBUG   - Running cmake on /home/ztest/work/zephyrproject/zephyr/tests/kernel/sc                                                                                hed/schedule_api for mec15xxevb_assy6853
DEBUG   - Calling cmake with arguments: ['-B/home/ztest/work/zephyrproject/zephy                                                                                r/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.schedule                                                                                r.no_timeslicing', '-S/home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/s                                                                                chedule_api', '-DEXTRA_CFLAGS="-Werror"', '-DEXTRA_AFLAGS="-Wa,--fatal-warnings'                                                                                , '-DEXTRA_LDFLAGS="-Wl,--fatal-warnings"', '-GUnix Makefiles', '-DOVERLAY_CONFI                                                                                G=/home/ztest/work/zephyrproject/zephyr/sanity-out/mec15xxevb_assy6853/tests/ker                                                                                nel/sched/schedule_api/kernel.scheduler.no_timeslicing/sanitycheck/testcase_extr                                                                                a.conf', '-DBOARD=mec15xxevb_assy6853']
DEBUG   - Calling cmake with arguments: ['-B/home/ztest/work/zephyrproject/zephy                                                                                r/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.schedule                                                                                r', '-S/home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/schedule_api', '                                                                                -DEXTRA_CFLAGS="-Werror"', '-DEXTRA_AFLAGS="-Wa,--fatal-warnings', '-DEXTRA_LDFL                                                                                AGS="-Wl,--fatal-warnings"', '-GUnix Makefiles', '-DOVERLAY_CONFIG=/home/ztest/w                                                                                ork/zephyrproject/zephyr/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/sched                                                                                ule_api/kernel.scheduler/sanitycheck/testcase_extra.conf', '-DBOARD=mec15xxevb_a                                                                                ssy6853']
DEBUG   - DONE FEEDING
DEBUG   - Finished building /home/ztest/work/zephyrproject/zephyr/tests/kernel/s                                                                                ched/schedule_api for mec15xxevb_assy6853
DEBUG   - Finished building /home/ztest/work/zephyrproject/zephyr/tests/kernel/s                                                                                ched/schedule_api for mec15xxevb_assy6853
DEBUG   - Finished building /home/ztest/work/zephyrproject/zephyr/tests/kernel/s                                                                                ched/schedule_api for mec15xxevb_assy6853
DEBUG   - Finished building /home/ztest/work/zephyrproject/zephyr/tests/kernel/s                                                                                ched/schedule_api for mec15xxevb_assy6853
DEBUG   - build test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel                                                                                .scheduler.multiq_no_timeslicing
DEBUG   - Building /home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/sche                                                                                dule_api for mec15xxevb_assy6853
DEBUG   - build test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel                                                                                .scheduler.no_timeslicing
DEBUG   - Building /home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/sche                                                                                dule_api for mec15xxevb_assy6853
DEBUG   - build test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel                                                                                .scheduler
DEBUG   - Building /home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/sche                                                                                dule_api for mec15xxevb_assy6853
DEBUG   - build test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel                                                                                .scheduler.multiq
DEBUG   - Building /home/ztest/work/zephyrproject/zephyr/tests/kernel/sched/sche                                                                                dule_api for mec15xxevb_assy6853
DEBUG   - run test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler
DEBUG   - run test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler.multiq
DEBUG   - run test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler.multiq_no_timeslicing
DEBUG   - run test: mec15xxevb_assy6853/tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler.no_timeslicing
DEBUG   - Using serial device /dev/ttyUSB2
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 0.
Done!

DEBUG   - Flash command: ['west', 'flash', '--skip-rebuild', '-d', '/home/ztest/                                                                                work/zephyrproject/zephyr/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/sche                                                                                dule_api/kernel.scheduler', '--runner', 'dediprog']
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 1.
Done!

DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v2.4.0-617-g34cf1c74c21b  *                                                                                **
DEBUG   - DEVICE: Running test suite threads_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_bad_priorities
DEBUG   - DEVICE: PASS - test_bad_priorities
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_cooperative
DEBUG   - DEVICE: PASS - test_priority_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible
DEBUG   - DEVICE: PASS - test_priority_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: PASS - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_yield_cooperative
DEBUG   - DEVICE: PASS - test_yield_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_cooperative
DEBUG   - DEVICE: PASS - test_sleep_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: PASS - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_pending_thread_wakeup
DEBUG   - DEVICE: PASS - test_pending_thread_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_preemptible
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_time_slicing_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: PASS - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_lock_preemptible
DEBUG   - DEVICE: PASS - test_lock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_preemptible
DEBUG   - DEVICE: PASS - test_unlock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: START - test_unlock_nested_sched_lock
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_unlock_nested_sched_lock
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sched_is_preempt_thread
DEBUG   - DEVICE: PASS - test_sched_is_preempt_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_reset
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_slice_reset
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_scheduling
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_slice_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_scheduling
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: PASS - test_priority_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: PASS - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_wakeup
DEBUG   - DEVICE: PASS - test_user_k_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_is_preempt
DEBUG   - DEVICE: PASS - test_user_k_is_preempt
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: Test suite threads_scheduling succeeded
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL
DEBUG   - run status: passed
DEBUG   - Using serial device /dev/ttyUSB2
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 0.
Done!

DEBUG   - Flash command: ['west', 'flash', '--skip-rebuild', '-d', '/home/ztest/                                                                                work/zephyrproject/zephyr/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/sche                                                                                dule_api/kernel.scheduler.multiq', '--runner', 'dediprog']
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 1.
Done!

DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v2.4.0-617-g34cf1c74c21b  *                                                                                **
DEBUG   - DEVICE: Running test suite threads_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_bad_priorities
DEBUG   - DEVICE: PASS - test_bad_priorities
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_cooperative
DEBUG   - DEVICE: PASS - test_priority_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible
DEBUG   - DEVICE: PASS - test_priority_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: PASS - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_yield_cooperative
DEBUG   - DEVICE: PASS - test_yield_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_cooperative
DEBUG   - DEVICE: PASS - test_sleep_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: PASS - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_pending_thread_wakeup
DEBUG   - DEVICE: PASS - test_pending_thread_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_preemptible
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_time_slicing_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: PASS - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_lock_preemptible
DEBUG   - DEVICE: PASS - test_lock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_preemptible
DEBUG   - DEVICE: PASS - test_unlock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_nested_sched_lock
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_unlock_nested_sched_lock
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sched_is_preempt_thread
DEBUG   - DEVICE: PASS - test_sched_is_preempt_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_reset
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_slice_reset
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_scheduling
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_slice_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_scheduling
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: PASS - test_priority_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: PASS - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_wakeup
DEBUG   - DEVICE: PASS - test_user_k_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_is_preempt
DEBUG   - DEVICE: PASS - test_user_k_is_preempt
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: Test suite threads_scheduling succeeded
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL
DEBUG   - run status: passed
DEBUG   - Using serial device /dev/ttyUSB2
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 0.
Done!

DEBUG   - Flash command: ['west', 'flash', '--skip-rebuild', '-d', '/home/ztest/                                                                                work/zephyrproject/zephyr/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/sche                                                                                dule_api/kernel.scheduler.multiq_no_timeslicing', '--runner', 'dediprog']
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 1.
Done!

DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v2.4.0-617-g34cf1c74c21b  *                                                                                **
DEBUG   - DEVICE: Running test suite threads_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_bad_priorities
DEBUG   - DEVICE: PASS - test_bad_priorities
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_cooperative
DEBUG   - DEVICE: PASS - test_priority_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible
DEBUG   - DEVICE: PASS - test_priority_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: PASS - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_yield_cooperative
DEBUG   - DEVICE: PASS - test_yield_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_cooperative
DEBUG   - DEVICE: PASS - test_sleep_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: PASS - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_pending_thread_wakeup
DEBUG   - DEVICE: PASS - test_pending_thread_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_preemptible
DEBUG   - DEVICE: SKIP - test_time_slicing_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: SKIP - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_lock_preemptible
DEBUG   - DEVICE: PASS - test_lock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_preemptible
DEBUG   - DEVICE: PASS - test_unlock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_nested_sched_lock
DEBUG   - Waiting for device mec15xxevb_assy6853 to become available
DEBUG   - DEVICE: PASS - test_unlock_nested_sched_lock
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sched_is_preempt_thread
DEBUG   - DEVICE: PASS - test_sched_is_preempt_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_reset
DEBUG   - DEVICE: SKIP - test_slice_reset
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_scheduling
DEBUG   - DEVICE: SKIP - test_slice_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_scheduling
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: PASS - test_priority_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: PASS - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_wakeup
DEBUG   - DEVICE: PASS - test_user_k_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_is_preempt
DEBUG   - DEVICE: PASS - test_user_k_is_preempt
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: Test suite threads_scheduling succeeded
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL
DEBUG   - run status: passed
DEBUG   - Using serial device /dev/ttyUSB2
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 0.
Done!

DEBUG   - Flash command: ['west', 'flash', '--skip-rebuild', '-d', '/home/ztest/                                                                                work/zephyrproject/zephyr/sanity-out/mec15xxevb_assy6853/tests/kernel/sched/sche                                                                                dule_api/kernel.scheduler.no_timeslicing', '--runner', 'dediprog']
DEBUG   -
Searching for connected FTDI devices with USB VID:PID=0x0403:0x6001...
MATCH: FTDI device 0 (FTDI TTL232R-3V3, Serial #: FT9FPJZR)
SKIPPING: FTDI device 1 (FTDI TTL232R-3V3, Serial #: FT9FTT5P)
Setting GPIO 0x01 to 1.
Done!

DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v2.4.0-617-g34cf1c74c21b  *                                                                                **
DEBUG   - DEVICE: Running test suite threads_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_bad_priorities
DEBUG   - DEVICE: PASS - test_bad_priorities
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_cooperative
DEBUG   - DEVICE: PASS - test_priority_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible
DEBUG   - DEVICE: PASS - test_priority_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: PASS - test_priority_preemptible_wait_prio
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_yield_cooperative
DEBUG   - DEVICE: PASS - test_yield_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_cooperative
DEBUG   - DEVICE: PASS - test_sleep_cooperative
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: PASS - test_sleep_wakeup_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_pending_thread_wakeup
DEBUG   - DEVICE: PASS - test_pending_thread_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_preemptible
DEBUG   - DEVICE: SKIP - test_time_slicing_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: SKIP - test_time_slicing_disable_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_lock_preemptible
DEBUG   - DEVICE: PASS - test_lock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_preemptible
DEBUG   - DEVICE: PASS - test_unlock_preemptible
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_unlock_nested_sched_lock
DEBUG   - DEVICE: PASS - test_unlock_nested_sched_lock
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_sched_is_preempt_thread
DEBUG   - DEVICE: PASS - test_sched_is_preempt_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_reset
DEBUG   - DEVICE: SKIP - test_slice_reset
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_slice_scheduling
DEBUG   - DEVICE: SKIP - test_slice_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_priority_scheduling
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: AB
DEBUG   - DEVICE: PASS - test_priority_scheduling
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: PASS - test_wakeup_expired_timer_thread
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_wakeup
DEBUG   - DEVICE: PASS - test_user_k_wakeup
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: START - test_user_k_is_preempt
DEBUG   - DEVICE: PASS - test_user_k_is_preempt
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: Test suite threads_scheduling succeeded
DEBUG   - DEVICE: ==============================================================                                                                                =====
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL
DEBUG   - run status: passed
INFO    - 1/4 mec15xxevb_assy6853       tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler.no_timeslicing PASSED (device 54.248s)
INFO    - 2/4 mec15xxevb_assy6853       tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler.multiq_no_timeslicing PASSED (device 54.246s)
INFO    - 3/4 mec15xxevb_assy6853       tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler.multiq PASSED (device 61.261s)
INFO    - 4/4 mec15xxevb_assy6853       tests/kernel/sched/schedule_api/kernel.s                                                                                cheduler   PASSED (device 61.276s)

DEBUG   - running footprint_reports
INFO    - 4 of 4 tests passed (100.00%), 0 failed, 0 skipped with 0 warnings in                                                                                238.54 seconds
INFO    - In total 72 test cases were executed on 1 out of total 292 platforms (                                                                                0.34%)
INFO    - 4 tests executed on platforms, 0 tests were only built.

Hardware distribution summary:

| Board               | ID       |   Counter |
|---------------------|----------|-----------|
| mec15xxevb_assy6853 | FT9FPJYP |         4 |

Just for reference: The tests are now all PASSED for efm32pg_stk3402a.
$ sanitycheck -p efm32pg_stk3402a -v --device-testing --device-serial /dev/ttyACM1 -T tests/kernel/sched/schedule_api/ -vv
...
DEBUG   - run status: passed
INFO    - 1/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler   PASSED (device 19.918s)
INFO    - 2/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler.multiq PASSED (device 19.930s)
INFO    - 3/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler.no_timeslicing PASSED (device 4.392s)
INFO    - 4/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler.multiq_no_timeslicing PASSED (device 4.691s)

DEBUG   - running footprint_reports
INFO    - 4 of 4 tests passed (100.00%), 0 failed, 0 skipped with 0 warnings in 81.13 seconds
INFO    - In total 72 test cases were executed on 1 out of total 292 platforms (0.34%)
INFO    - 4 tests executed on platforms, 0 tests were only built.
...

Just for reference: The tests are now (revision 3ce7afd) all PASSED for efm32pg_stk3402a.
$ sanitycheck -p efm32pg_stk3402a -v --device-testing --device-serial /dev/ttyACM1 -T tests/kernel/sched/schedule_api/ -vv
...
DEBUG   - run status: passed
INFO    - 1/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler   PASSED (device 19.918s)
INFO    - 2/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler.multiq PASSED (device 19.930s)
INFO    - 3/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler.no_timeslicing PASSED (device 4.392s)
INFO    - 4/4 efm32pg_stk3402a          tests/kernel/sched/schedule_api/kernel.scheduler.multiq_no_timeslicing PASSED (device 4.691s)

DEBUG   - running footprint_reports
INFO    - 4 of 4 tests passed (100.00%), 0 failed, 0 skipped with 0 warnings in 81.13 seconds
INFO    - In total 72 test cases were executed on 1 out of total 292 platforms (0.34%)
INFO    - 4 tests executed on platforms, 0 tests were only built.
...

Great!


Local / npx script produces different outputs

Issue
Running lilmolly via node_modules vs npx produced a different output. Local node_modules appears to be incorrectly identifying unused components.
This might onlt be an issue with pnpm, I haven't tested with yarn or npm yet.
Details
I have a somewhat large SvelteKit project. I installed molly with pnpm add lilmolly -D.
When running lilmolly, most of my components are marked as unused, though not all. (right of screenshot)
However, running npx lilmolly produces a more accurate output. (left of screenshot)

Hi Ollie,
Thanks for the note. I realized I neglected to publish some bug fixes/updates to npm 1.3.4. It's now there (1.3.7). https://www.npmjs.com/package/lilmolly When I try to reproduce your bug now, I don’t see a discrepancy. I was wondering, can you try again and let me know if the problem is gone or remains?

@renefournier 👍 yup, looks like this is resolved. Thank you!


Update links to the repository

I replaced old links to the repository to the new ones after migrating the repository to the netcanv organization. By the way I fixed the link to the issues page and a little typo.
In the topic of updating various strings - there are also a few which I'm not sure about.

Should we update the copyright notice in main.rs:2 - // Copyright 2021-2022, liquidev, the year seems obvious but what about the signature, should it refer the organization's name those days?
In the windows-icons.ps1:20 script there's a line - $company_name = "liquidev", this one also should be updated to netcanv I think.

Please take those points into account and maybe give me a feedback about whether it should be changed in this PR or it's a subject for an another, new issue, thanks.

In main.rs, please update the years to 2021-2024 liquidev as that's when I last contributed something to the project, while it was under my name and not this organization. Other than that you're free to do whatever you wish with the copyright notice; I'd probably do something like 2024-today NetCanv contributors to not have to update it every year.
As for the Windows metadata, changing liquidev to NetCanv or NetCanv contributors would be fine by me.

@devildefu done


Implemented AndroidNotification API

Follow up to #12

@stewartmiles I've documented all internal types and properties (some of it was done in #12, and merged back here).


where is the source code of 'tanh' and 'relu' activationin Theano

These days,im studying activation functions,but i can't find the source code of them.

How is that related to keras? Anyway, you can find the implementations here:
https://github.com/Theano/Theano/blob/master/theano/tensor/nnet/nnet.py (includes relu)
https://github.com/Theano/Theano/blob/master/theano/tensor/basic.py (includes tanh)


FEAT/ category predictions model for new texts

https://trello.com/c/iOSrB5Oj
One more step is left and that is to pickle this and put it in the FastAPI

awesome, we are getting really close with this! as you said, next step is pickling and deploying in the API


test-branch/execute-job/quoted-authorization/8e433b02-e320-4b6c-8fdf-60a8040e51a8

PR for testing a64908b086d03bcf9d36f20fd3fe873571b281f5

/canonical/self-hosted-runners/run-workflows a64908b086d03bcf9d36f20fd3fe873571b281f5


Micro organization?

I really like micro as an alternative to Koa - have you given any thought to creating something like a Micro JS community organization where people can host plugins etc?

That might conflict with https://github.com/micro. But it's an interesting idea 👍

cc @leo

Why would people want to host plugins in a centralized place instead of being able to manage their own account completely and without restrictions?

I'd imagine for the same reason koa, Hapi, Express have them - to build a community around the framework. Given how minimal micro is though I'd understand if that isn't a goal of the project.

Looks like someone is already doing that: https://github.com/zeit/micro/issues/134#issuecomment-275637858. 😄


Tabbing around screen

While the tabbing order is intuitive, the tabbing highlights all hyperlinks on the page (even the ones "behind the scenes"), so that after you have tabbed out of the form, you have to continue tabbing many many times to get back to the form; it seems to be picking up links to external vocabularies, etc.

I had the same experience, here's how I described it:  Although the tab stops are straightforward, they do not immediately seem so, visually.  Blue text is not highlighted when tabbing alights on it, so tabbing "disappears" momentarily; and highlighting around the tooltip for RDA is hard to notice at first so tabbing may seem to disappear for those clicks too.

re the tab focus disappearing see #1277
the other issue seems to be the same as #1256, after you finish tabbing through the form, the tabbing continues into the footer and then header of the page, and that's when it goes to the items on the Help & Resources menu
closing as duplicate of those other 2 tix


Update circe, logback, objenesis, bcpkix, bcprov, http4s, typesafeConfig versions

Update circe-core, circe-generic, ... to 0.14.9
Update logback-classic to 1.5.7
Update objenesis to 3.4
Update bcpkix-jdk15on, bcprov-jdk15on to 1.78.1
chore: add sbt-scalafix plugin
chore: update circe-generic-extras to version 0.14.4
chore: update http4sVersion to 0.22.15
chore: update typeSafeConfig to version 1.4.3

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.23%. Comparing base (c04d33c) to head (e6760e0).
Report is 9 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1732      +/-   ##
==========================================
- Coverage   79.35%   79.23%   -0.12%
==========================================
  Files         144      144
  Lines        5008     5009       +1
  Branches      670      674       +4
==========================================
- Hits         3974     3969       -5
- Misses       1034     1040       +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Drawing Image on Chat

The problem
Prompt: Draw a cat like Louis Wain
If this prompt is typed, bing generates an image so the bot goes into a bug and appears to be typing forever.
Version of python
latest
Version of EdgeGPT-Telegram-Bot
latest
Operating system running EdgeGPT-Telegram-Bot
latest
Running on your machine? Running on docker?
latest
Additional information & file uploads
No response

I need logs

Can't replicate

Currently, image generation is handled by another library (BingImageCreator), so you have to guide the bot to do what you wanted. By default, messages without /image command will query Bing using EdgeGPT (which doesn't handle inline images). If it generates an exception because it doesn't expect that response, the bot will crash due to that exception.


[Feature] Check for _clone_excluded_m2o_or_o2m_fields is None instead of truthy

Is this feature missing in the latest version?

[X] I'm using the latest release

Is your feature request related to a problem? Please describe.
We want to enforce the use of the clone_excluded* fields and set them on our BaseModel:
class BaseModel(CloneMixin, models.Model):

    _clone_excluded_fields = []
    _clone_excluded_m2m_fields = []
    _clone_excluded_m2o_or_o2m_fields = []
    _clone_excluded_o2o_fields = []

The problem now is that empty lists are of course falsy. Line 491 in mixins/clone.py then return false and no field is copied.
if any(
    [
        f.get_accessor_name() in self._clone_m2o_or_o2m_fields,
>      self._clone_excluded_m2o_or_o2m_fields
        and f.get_accessor_name()
        not in self._clone_excluded_m2o_or_o2m_fields,
    ]
)

At least for me that wasn't the expected behaviour.
Describe the solution you'd like?
This should be easily handled by checking for self._clone_excluded_* is not None.
Describe alternatives you've considered?
I'll just make them self._clone_excluded_* = [''] for now.
Anything else?
Happy to make a PR if you're ok with my proposal
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@saschahofmann Sure I’ll welcome a PR but I’m still somewhat puzzled about your proposed solution, are you suggesting we use a default of [‘’] instead of an empty list

Nope! That's my workaround for now. I suggest we make None the default and check for is None instead of the truthyness of the argument.

It'd be non backwards compatible if someone would overwrite the default itself with an empty list but I would think that's rare and acceptable?


ses.funcLike fails on bound functions on Chrome

ses.funcLike(function() {}, function x() {}.bind(null))
⇒ SyntaxError: Unexpected identifier

Works on Firefox, fails on Chrome 50.0.2661.102

What's happening is that makeStandinMaker is generating and evaling the following string, presumably because the name of
function x() {}.bind(null)

on Chrome 50 is "bound x". Will fix.
(function makeStandin(newF) {
  "use strict";
  return function bound x() {
    return newF.apply(this, arguments);
  }
})

The change needed is that the line at https://github.com/google/caja/blob/master/src/com/google/caja/ses/repairES5.js#L1133 which is currently
if (!/[a-zA-Z][a-zA-Z0-9]*/.test(standinName)) {

should instead be
if (!/^[a-zA-Z][a-zA-Z0-9]*$/.test(standinName)) {

IOW, the test for checking that it is an identifier was already there, but I forgot to anchor the ends of the regexp.
Kevin, I'm still traveling. Could you take it from here and I'll review? Thanks.


dependency conflict + inference on GPU

Hello, thank you for this software. I wanted to point out some issues.

the dependencies in requirements.txt are conflicting for me (Ubuntu 20.04) . The error message:
`ERROR: Cannot install -r requirements.txt (line 9) and sip==5.0.0 because these package versions have conflicting dependencies.

The conflict is caused by:
The user requested sip==5.0.0
pyqt5 5.10.1 depends on sip<4.20 and >=4.19.4`
I managed to install it using pip though, but would prefer to build from source. Perhaps you can find a version of sip and/or pyqt5 which is compatible with everything else.

I notice when running inference that it is not using the GPU at all. Is it supposed to be this way or is there a line of code somewhere to enable GPU/CUDA inference?

Hello,
On my end, pip cannot resolve the conflicting dependencies. Here is the error:
ERROR: Cannot install labelstoma==0.1.1, labelstoma==0.1.10, labelstoma==0.1.11, labelstoma==0.1.12, labelstoma==0.1.13, labelstoma==0.1.14, labelstoma==0.1.15, labelstoma==0.1.16, labelstoma==0.1.17, labelstoma==0.1.18, labelstoma==0.1.19, labelstoma==0.1.2, labelstoma==0.1.21, labelstoma==0.1.23, labelstoma==0.1.24, labelstoma==0.1.25, labelstoma==0.1.26, labelstoma==0.1.28, labelstoma==0.1.29, labelstoma==0.1.30, labelstoma==0.1.31, labelstoma==0.1.32, labelstoma==0.1.33, labelstoma==0.1.34, labelstoma==0.1.35, labelstoma==0.1.36, labelstoma==0.1.37, labelstoma==0.1.38, labelstoma==0.1.39, labelstoma==0.1.40, labelstoma==0.1.6, labelstoma==0.1.7, labelstoma==0.1.8, labelstoma==0.1.9, labelstoma==0.2.0, labelstoma==0.2.1, labelstoma==0.2.2, labelstoma==0.2.3, labelstoma==0.2.4, labelstoma==0.2.5, labelstoma==0.2.6, labelstoma==0.2.7, labelstoma==0.2.8, labelstoma==0.2.9, labelstoma==0.3.0, labelstoma==0.3.1, labelstoma==0.3.2, labelstoma==0.3.3, labelstoma==0.3.4, labelstoma==0.3.5, labelstoma==0.3.6, labelstoma==0.3.7, labelstoma==0.3.8, labelstoma==1.0, labelstoma==1.1, labelstoma==1.2, labelstoma==1.3, labelstoma==1.4 and labelstoma==1.5 because these package versions have conflicting dependencies.

The conflict is caused by:
    labelstoma 1.5 depends on opencv_python==<IP_ADDRESS>
    labelstoma 1.4 depends on opencv_python==<IP_ADDRESS>
    labelstoma 1.3 depends on opencv_python==<IP_ADDRESS>
    labelstoma 1.2 depends on opencv_python==<IP_ADDRESS>
    labelstoma 1.1 depends on opencv_python==<IP_ADDRESS>
    labelstoma 1.0 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.8 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.7 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.6 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.5 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.4 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.3 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.2 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.1 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.3.0 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.9 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.8 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.7 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.6 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.5 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.4 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.3 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.2 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.1 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.2.0 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.40 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.39 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.38 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.37 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.36 depends on tensorflow==1.14.0
    labelstoma 0.1.35 depends on tensorflow==1.14.0
    labelstoma 0.1.34 depends on tensorflow==1.14.0
    labelstoma 0.1.33 depends on tensorflow==1.14.0
    labelstoma 0.1.32 depends on tensorflow==1.14.0
    labelstoma 0.1.31 depends on tensorflow==1.14.0
    labelstoma 0.1.30 depends on tensorflow==1.14.0
    labelstoma 0.1.29 depends on tensorflow==1.14.0
    labelstoma 0.1.28 depends on tensorflow==1.14.0
    labelstoma 0.1.26 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.25 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.24 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.23 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.21 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.19 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.18 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.17 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.16 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.15 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.14 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.13 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.12 depends on opencv_python==<IP_ADDRESS>
    labelstoma 0.1.11 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.10 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.9 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.8 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.7 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.6 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.2 depends on opencv_contrib_python==<IP_ADDRESS>
    labelstoma 0.1.1 depends on opencv_contrib_python==<IP_ADDRESS>

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies


Test: panel title area

[ ] win @ramya-rao-a
[ ] mac @mjbvz
[ ] linux @Tyriar

Complexity: 3
Open the panel and verify in the title area:

You can move / hide / show panels
Once there is not enough space in the title area you see nice overflow behavior
Badges are properly shown in panels
Panel title view state is preserved across vscode sessions
Be creative in trying to break it and feedback on how to further improve this UX is appricated

@isidorn

Badges are properly shown in panels

What are badges in the panel context and where do they appear?

@ramya-rao-a sorry about that, no panel has adopted this behavior yet so we currently do not have any badges.


use definitions ZLIB_COMPAT WITH_GZFILEOP in target_compile_definitions

(automatically used when zlib-ng linked with cmake)

Obviously can't use cmake commands introduced in cmake 3.x series.

Is this supported by cmake 2.8?

Sorry, this needs to be rebased.

Obsoleted


AKOscillator max frequency

It seems that AKOscillator only supports max 20000 frequency?
    let oscillator = AKOscillator()
    oscillator.amplitude = 0.3
    oscillator.frequency = 24000

    AudioKit.output = oscillator

    AudioKit.start()

    oscillator.start()

By design.  If you want to try to go beyond that limit, change the DSP Kernel for the AKOscillator to not clamp the value:
void setFrequency(float value) {
    frequency = clamp(value, (float)0, (float)20000);
    frequencyRamper.setImmediate(frequency);
}


fix for phantomjs send_keys

https://github.com/detro/ghostdriver/issues/249

Huge Thanks!
This looks very good and I will merge some of it!


Design QA - Confirmed message on Notifications

We should use this approach to show the status on the Notification box after an action is confirmed: The icon should dissappear after 1 or 2 seconds:

Figma reference:
https://www.figma.com/file/42QoTLQcbObu7esoTPjWRv/Augur-Bet-Design-System?node-id=1227%3A0

This appears but then after a few seconds the original notification message reappears with the action button. This then removes after a second or 2. Test it to see what I mean


Issue - Your connection is not private

Hi !
Thanks for the tutorial on Medium and this repo.
I've followed exactly what you've explained on, first Medium then by just downloading this repo but everytime I got the "Your connection is not private" issue:

Tried on Firefox, Edge and Chrome.
Windows 11 / WSL2

Found. We need to create an exception for self-signed certificate. To do this, we need to visit chrome://flags/#temporary-unexpire-flags-m118, search for localhost and enable the option.

@cavo789 Thanks for reaching out.
I am glad you found the tutorial useful.


optimise two-state model to produce pitchfork and saddle-node

we would like to test a model that has the ability to reproduce multiple bifurcation types and plot a dimensionally reduced  parameter regions that reproduce each behaviour.

start with 3D version then extend to 7D version

two state model gives rise to mutual activation and inhibition regimes in paper


How to install if I am using Swift 4?

If I install using cocoapods, I get compiler error e.g.
'AVLayerVideoGravityResize' has been renamed to 'AVLayerVideoGravity.resize'

Hi @irtefa
you can use the swift-4 branch to do this:
 pod 'SwiftyCam', :git => 'https://github.com/Awalz/SwiftyCam.git', :branch => 'Swift4'

Good day! Is the swift-4 branch stable?


[bug] route resource provisioner only supports exact path matches and needs to support prefix matching too

Let's see if we can make this switch using a score-compose specific annotation. In the real world the actual resource driver would be configured differently.
score-compose.score.dev/route-provisioner-path-type: Prefix vs Exact
This is very common for cases like deploying a small blog or webapp that has it's own content management.
We should also change the default path type to be prefix which is generally what folks expect!

And a related bug, The metadata dict is null during resource provisioning

The following modification to the route provisioner seems to do the trick:
{{ range $k, $v := $r }}
          # the basic path variant, "/" or "/one/two"
          location = {{ index $v "path" }} {
            set $backend {{ index $v "target" }};
            rewrite ^{{ index $v "path" }}(.*)$ /$1 break;
            proxy_pass http://$backend;
          }

          # The prefix match variants are included by default but can be excluded via 'score-compose.score.dev/route-provisioner-path-type' annotation
          {{ if eq (dig "score-compose.score.dev/route-provisioner-path-type" "Prefix" (dig "annotations" (dict) (.Metadata | default (dict)))) "Prefix" }}
          location {{ index $v "path" | trimSuffix "/" }}/ {
            set $backend {{ index $v "target" }};
            rewrite ^{{ index $v "path" }}/(.*)$ /$1 break;
            proxy_pass http://$backend;
          }
          {{ end}}

          {{ end }}


Add Kunal-Khanwalkar to Contributors list

Hi  @Kunal-khanwalkar, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Table header formatting doesn't render well

The header of tables is hard to read with the current color scheme, black on dark blue. It also doesn't seem to auto scale or line wrap longer column text properly and in some places a column's header text overlaps with the next column.
For example from https://qiskit.org/documentation/release_notes.html#version-history

I believe I know the source of this.

https://github.com/Qiskit/qiskit-terra/pull/5865

Closing as fixed.