Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Entwicklung
    4. Problem beim integrationstest mit github-actions

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Problem beim integrationstest mit github-actions

    This topic has been deleted. Only users with topic management privileges can see it.
    • OliverIO
      OliverIO last edited by OliverIO

      Hallo,

      seit einigen Tagen schläg der integrationstest von 2 Adapter fehl (bei einem 3.Adapter, den ich ebenfalls umgestellt habe funktioniert es ohne Probleme).

      Der Integrationstest wird mit einem timeout-Fehler abgebrochen.
      Leider sehe ich im log, außer dem timeout-Fehler nicht wirklich hinweise an was es liegen könnte:
      https://github.com/oweitman/ioBroker.tvprogram/runs/4961040754?check_suite_focus=true
      Fehler ist im Bereich der zeile 482

      Evtl seht ihr da noch etwas?

      AlCalzone 1 Reply Last reply Reply Quote 0
      • AlCalzone
        AlCalzone Developer @OliverIO last edited by

        @oliverio Du scheinst iobroker.vis in den Adapter-Dependencies zu haben. Das wird dann mitinstalliert, die Installation klappt aber wohl nicht:

        > iobroker.vis@1.4.6 install /tmp/test-iobroker.tvprogram/node_modules/iobroker.vis
        > node main.js --install
        
        apollon77 OliverIO 2 Replies Last reply Reply Quote 0
        • apollon77
          apollon77 @AlCalzone last edited by

          @alcalzone Also ja vis install von "npm latest" ist aktuell komisch weil läuft pot auf einen error, aber auch nur das kannte ich bisher ... das es hängt ist komisch

          1 Reply Last reply Reply Quote 0
          • OliverIO
            OliverIO @AlCalzone last edited by

            @alcalzone @apollon77
            für mich sieht es so aus als ob vis install kein problem macht, aber der nächste befehl dann
            openliga ist identisch (sofern ich das überblicken kann), auch mit vis, dort läuft der test aber durch.
            kann man das irgendwie lokal in einem docker nachstellen?

            apollon77 1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 @OliverIO last edited by

              @oliverio Bitte restarte mal das testing

              OliverIO 1 Reply Last reply Reply Quote 0
              • OliverIO
                OliverIO @apollon77 last edited by

                @apollon77
                ok läuft
                https://github.com/oweitman/ioBroker.tvprogram/actions/runs/1754235327

                sind gleich weg, kann das Ergebnis erst später sehen

                AlCalzone 1 Reply Last reply Reply Quote 0
                • AlCalzone
                  AlCalzone Developer @OliverIO last edited by

                  @oliverio Sieht aus wie vorher. Läuft es lokal beim Testen durch?
                  Linux:

                  DEBUG=testing:* npm run test:integration
                  

                  oder Windows:

                  set DEBUG=testing:* & npm run test:integration
                  
                  OliverIO 1 Reply Last reply Reply Quote 0
                  • OliverIO
                    OliverIO @AlCalzone last edited by

                    @alcalzone
                    ja lokal (debian im buanet) läuft es immer astrein durch.
                    allerdings hab ich mir die warnungen (eigentlich immer optional dependencies) angeschaut.
                    habe festgestellt, das ein paar prod dependencies in dev drin waren.
                    habe nun umgestellt, warte nun auf die github actions. scheint alles gerade etwas überlastet zu sein.

                    OliverIO 1 Reply Last reply Reply Quote 0
                    • OliverIO
                      OliverIO @OliverIO last edited by

                      also dependencies und warnungen sind überprüft.
                      debugging env mit eingefügt.
                      allerdings hat sich vom Ergebnis nix getan.

                      https://github.com/oweitman/ioBroker.mytime/runs/5014206508?check_suite_focus=true

                      das debugging hat leider auch nicht mehr informationen produziert.
                      evtl hilft auch noch diese information
                      die letzte test and release action die funktioniert hat

                      https://github.com/oweitman/ioBroker.mytime/runs/4877133925
                      und die action nach der es nicht mehr funktioniert hat
                      https://github.com/oweitman/ioBroker.mytime/actions/runs/1726759260

                      beides dependabot pulls zur aktualisierung von dependencies
                      leider reichen meine Kenntnisse dazu nicht aus, da etwas zu finden

                      apollon77 1 Reply Last reply Reply Quote 0
                      • apollon77
                        apollon77 @OliverIO last edited by

                        @oliverio @AlCalzone kann es daran liegen das ggf kein echter iobroker da ist oder so? Am Ende will das post install Skript von Vis zur db verbinden und da Dinge tun … nicht das das irgendwie hängt?

                        AlCalzone 1 Reply Last reply Reply Quote 0
                        • AlCalzone
                          AlCalzone Developer @apollon77 last edited by

                          @apollon77 Aber warum läuft es lokal dann durch?

                          @oliverio sagte in Problem beim integrationstest mit github-actions:

                          ja lokal (debian im buanet) läuft es immer astrein durch.

                          Nur um sicher zu gehen: @OliverIO wenn du lokal auf deinem Dev-Rechner ohne ioBroker den entsprechenden Befehl ausführst, siehe https://forum.iobroker.net/post/751003, dann läuft das Testing durch?

                          OliverIO 1 Reply Last reply Reply Quote 0
                          • OliverIO
                            OliverIO @AlCalzone last edited by

                            @alcalzone

                            ja, ist ein docker-container von buanet

                            hier das log für test:integration

                            > iobroker.mytime@0.7.12 test:integration /opt/iobroker/ioBroker.mytime
                            > DEBUG=testing:* & mocha test/integration --exit
                            
                            
                            Running tests in /tmp/test-iobroker.mytime
                            
                            
                            
                             Test the adapter (in a live environment)
                            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
                            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
                            npm WARN test-iobroker.mytime@1.0.0 No description
                            npm WARN test-iobroker.mytime@1.0.0 No repository field.
                            
                            added 2 packages from 2 contributors in 5.557s
                            
                            21 packages are looking for funding
                             run `npm fund` for details
                            
                            Deprecated! Please use require("@iobroker/db-objects-file").Server in tests to start a server and then use require("@iobroker/db-objects-file").Client to connect with a client against this server!
                            Server Data File: /tmp/test-iobroker.mytime/iobroker-data/objects.json
                            Server Objects DB uses file write interval of 5000 ms
                            Server  Redis inMem-objects listening on port 9001
                            Redis Objects: Use Redis connection: 127.0.0.1:19001
                            Objects client ready ... initialize now
                            Objects create System PubSub Client
                            Objects client initialize lua scripts
                            Objects connected to redis: 127.0.0.1:19001
                            Deprecated! Please use require("@iobroker/db-states-file").Server in tests to start a server and then use require("@iobroker/db-states-file").Client to connect with a client against this server!
                            Server Data File: /tmp/test-iobroker.mytime/iobroker-data/states.json
                            Server States DB uses file write interval of 30000 ms
                            redis psubscribe cfg.o.*
                            Server  Redis inMem-states listening on port 9000
                            Redis States: Use Redis connection: 127.0.0.1:19000
                            States create System PubSub Client
                            States connected to redis: 127.0.0.1:19000
                            Server Redis Publish Object system.adapter.test.0={"common":{},"type":"instance","_id":"system.adapter.test.0"}
                            Objects system redis pmessage */cfg.o.system.adapter.test.0:{"common":{},"type":"instance","_id":"system.adapter.test.0"}
                            Server Redis Publish Object system.adapter.mytime.0.alive={"_id":"system.adapter.mytime.0.alive","type":"state","common":{"name":"mytime.0 alive","type":"boolean","read":true,"write":true,"role":"indicator.state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217856,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.alive:{"_id":"system.adapter.mytime.0.alive","type":"state","common":{"name":"mytime.0 alive","type":"boolean","read":true,"write":true,"role":"indicator.state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217856,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.connected={"_id":"system.adapter.mytime.0.connected","type":"state","common":{"name":"mytime.0 is connected","type":"boolean","read":true,"write":false,"role":"indicator.state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217866,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.connected:{"_id":"system.adapter.mytime.0.connected","type":"state","common":{"name":"mytime.0 is connected","type":"boolean","read":true,"write":false,"role":"indicator.state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217866,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.compactMode={"_id":"system.adapter.mytime.0.compactMode","type":"state","common":{"name":"mytime.0.compactMode","type":"boolean","read":true,"write":false,"role":"indicator.state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217872,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.compactMode:{"_id":"system.adapter.mytime.0.compactMode","type":"state","common":{"name":"mytime.0.compactMode","type":"boolean","read":true,"write":false,"role":"indicator.state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217872,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.cpu={"_id":"system.adapter.mytime.0.cpu","type":"state","common":{"name":"mytime.0.cpu","type":"number","read":true,"write":false,"role":"indicator.state","unit":"% of one core"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217878,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.cpu:{"_id":"system.adapter.mytime.0.cpu","type":"state","common":{"name":"mytime.0.cpu","type":"number","read":true,"write":false,"role":"indicator.state","unit":"% of one core"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217878,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.cputime={"_id":"system.adapter.mytime.0.cputime","type":"state","common":{"name":"mytime.0.cputime","type":"number","read":true,"write":false,"role":"indicator.state","unit":"seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217884,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.cputime:{"_id":"system.adapter.mytime.0.cputime","type":"state","common":{"name":"mytime.0.cputime","type":"number","read":true,"write":false,"role":"indicator.state","unit":"seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217884,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.memHeapUsed={"_id":"system.adapter.mytime.0.memHeapUsed","type":"state","common":{"name":"mytime.0 heap actually Used","type":"number","read":true,"write":false,"role":"indicator.state","unit":"MB"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217890,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.memHeapUsed:{"_id":"system.adapter.mytime.0.memHeapUsed","type":"state","common":{"name":"mytime.0 heap actually Used","type":"number","read":true,"write":false,"role":"indicator.state","unit":"MB"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217890,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.memHeapTotal={"_id":"system.adapter.mytime.0.memHeapTotal","type":"state","common":{"name":"mytime.0 total Size of the Heap","read":true,"write":false,"type":"number","role":"indicator.state","unit":"MB"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217895,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.memHeapTotal:{"_id":"system.adapter.mytime.0.memHeapTotal","type":"state","common":{"name":"mytime.0 total Size of the Heap","read":true,"write":false,"type":"number","role":"indicator.state","unit":"MB"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217895,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.memRss={"_id":"system.adapter.mytime.0.memRss","type":"state","common":{"name":"mytime.0 resident Set Size","desc":"Resident set size","read":true,"write":false,"type":"number","role":"indicator.state","unit":"MB"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217901,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.memRss:{"_id":"system.adapter.mytime.0.memRss","type":"state","common":{"name":"mytime.0 resident Set Size","desc":"Resident set size","read":true,"write":false,"type":"number","role":"indicator.state","unit":"MB"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217901,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.uptime={"_id":"system.adapter.mytime.0.uptime","type":"state","common":{"name":"mytime.0 uptime","type":"number","read":true,"write":false,"role":"indicator.state","unit":"seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217906,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.uptime:{"_id":"system.adapter.mytime.0.uptime","type":"state","common":{"name":"mytime.0 uptime","type":"number","read":true,"write":false,"role":"indicator.state","unit":"seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217906,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.inputCount={"_id":"system.adapter.mytime.0.inputCount","type":"state","common":{"name":"mytime.0 events input counter","desc":"State's inputs in 15 seconds","type":"number","read":true,"write":false,"role":"state","unit":"events/15 seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217912,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.inputCount:{"_id":"system.adapter.mytime.0.inputCount","type":"state","common":{"name":"mytime.0 events input counter","desc":"State's inputs in 15 seconds","type":"number","read":true,"write":false,"role":"state","unit":"events/15 seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217912,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.outputCount={"_id":"system.adapter.mytime.0.outputCount","type":"state","common":{"name":"mytime.0 events output counter","desc":"State's outputs in 15 seconds","type":"number","read":true,"write":false,"role":"state","unit":"events/15 seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217917,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.outputCount:{"_id":"system.adapter.mytime.0.outputCount","type":"state","common":{"name":"mytime.0 events output counter","desc":"State's outputs in 15 seconds","type":"number","read":true,"write":false,"role":"state","unit":"events/15 seconds"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217917,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.eventLoopLag={"_id":"system.adapter.mytime.0.eventLoopLag","type":"state","common":{"name":"mytime.0 Node.js event loop lag","desc":"Node.js event loop lag in ms averaged over 15 seconds","type":"number","read":true,"write":false,"role":"state","unit":"ms"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217923,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.eventLoopLag:{"_id":"system.adapter.mytime.0.eventLoopLag","type":"state","common":{"name":"mytime.0 Node.js event loop lag","desc":"Node.js event loop lag in ms averaged over 15 seconds","type":"number","read":true,"write":false,"role":"state","unit":"ms"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217923,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.sigKill={"_id":"system.adapter.mytime.0.sigKill","type":"state","common":{"name":"mytime.0 kill signal","type":"number","read":true,"write":false,"desc":"Process id that must survive. All other IDs must terminate itself","role":"state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217929,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.sigKill:{"_id":"system.adapter.mytime.0.sigKill","type":"state","common":{"name":"mytime.0 kill signal","type":"number","read":true,"write":false,"desc":"Process id that must survive. All other IDs must terminate itself","role":"state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217929,"user":"system.user.admin"}
                            Server Redis Publish Object system.adapter.mytime.0.logLevel={"_id":"system.adapter.mytime.0.logLevel","type":"state","common":{"name":"mytime.0 loglevel","type":"string","read":true,"write":true,"desc":"Loglevel of the adapter. Will be set on start with defined value but can be overridden during runtime","role":"state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217934,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.system.adapter.mytime.0.logLevel:{"_id":"system.adapter.mytime.0.logLevel","type":"state","common":{"name":"mytime.0 loglevel","type":"string","read":true,"write":true,"desc":"Loglevel of the adapter. Will be set on start with defined value but can be overridden during runtime","role":"state"},"native":{},"from":"system.adapter.mytime.0","ts":1643709217934,"user":"system.user.admin"}
                            Server Redis Publish Object mytime.0.info={"_id":"mytime.0.info","type":"channel","common":{"name":"Information"},"native":{"counter":{}},"from":"system.adapter.mytime.0","ts":1643709217940,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.mytime.0.info:{"_id":"mytime.0.info","type":"channel","common":{"name":"Information"},"native":{"counter":{}},"from":"system.adapter.mytime.0","ts":1643709217940,"user":"system.user.admin"}
                            Server Redis Publish Object mytime.0.info.connection={"_id":"mytime.0.info.connection","type":"state","common":{"role":"indicator.connected","name":"Device or service connected","type":"boolean","read":true,"write":false,"def":false},"native":{},"from":"system.adapter.mytime.0","ts":1643709217945,"user":"system.user.admin"}
                            Objects system redis pmessage */cfg.o.mytime.0.info.connection:{"_id":"mytime.0.info.connection","type":"state","common":{"role":"indicator.connected","name":"Device or service connected","type":"boolean","read":true,"write":false,"def":false},"native":{},"from":"system.adapter.mytime.0","ts":1643709217945,"user":"system.user.admin"}
                            2022-02-01 10:53:37.960  - info: mytime.0 (3535) starting. Version 0.7.12 in /tmp/test-iobroker.mytime/node_modules/iobroker.mytime, node: v14.18.2, js-controller: 4.0.0-alpha.46-20220119-9e487e55
                            2022-02-01 10:53:37.999  - debug: mytime.0 (3535) main onReady start
                            2022-02-01 10:53:38.002  - debug: mytime.0 (3535) main onReady open mytime
                            2022-02-01 10:53:38.004  - debug: mytime.0 (3535) init
                            2022-02-01 10:53:38.006  - debug: mytime.0 (3535) setState connection true
                            2022-02-01 10:53:38.008  - debug: mytime.0 (3535) setCountdownInfo {}
                            2022-02-01 10:53:38.010  - debug: mytime.0 (3535) setTimeseriesInfo {}
                            Server memory publish system.adapter.mytime.0.logLevel {"val":"debug","ack":true,"ts":1643709218015,"q":0,"from":"system.adapter.mytime.0","lc":1643709218015}
                            Server Redis Publish State system.adapter.mytime.0.logLevel={"val":"debug","ack":true,"ts":1643709218015,"q":0,"from":"system.adapter.mytime.0","lc":1643709218015}
                            Server Redis Publish State system.adapter.mytime.0.logLevel={"val":"debug","ack":true,"ts":1643709218015,"q":0,"from":"system.adapter.mytime.0","lc":1643709218015}
                            Server memory publish system.adapter.mytime.0.alive {"val":true,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017,"expire":true}
                            Server Redis Publish State system.adapter.mytime.0.alive={"val":true,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017,"expire":true}
                            Server memory publish system.adapter.mytime.0.connected {"val":true,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017,"expire":true}
                            Server Redis Publish State system.adapter.mytime.0.connected={"val":true,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017,"expire":true}
                            Server memory publish system.adapter.mytime.0.memRss {"val":66.08,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017}
                            Server Redis Publish State system.adapter.mytime.0.memRss={"val":66.08,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017}
                            Server memory publish system.adapter.mytime.0.memHeapTotal {"val":47.61,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017}
                            Server Redis Publish State system.adapter.mytime.0.memHeapTotal={"val":47.61,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017}
                            States system redis pmessage */system.adapter.mytime.0.logLevel:{"val":"debug","ack":true,"ts":1643709218015,"q":0,"from":"system.adapter.mytime.0","lc":1643709218015}
                            States system redis pmessage */system.adapter.mytime.0.alive:{"val":true,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017,"expire":true}
                            States system redis pmessage */system.adapter.mytime.0.connected:{"val":true,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017,"expire":true}
                            States system redis pmessage */system.adapter.mytime.0.memRss:{"val":66.08,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017}
                            States system redis pmessage */system.adapter.mytime.0.memHeapTotal:{"val":47.61,"ack":true,"ts":1643709218017,"q":0,"from":"system.adapter.mytime.0","lc":1643709218017}
                            Server memory publish system.adapter.mytime.0.memHeapUsed {"val":13.79,"ack":true,"ts":1643709218025,"q":0,"from":"system.adapter.mytime.0","lc":1643709218025}
                            Server Redis Publish State system.adapter.mytime.0.memHeapUsed={"val":13.79,"ack":true,"ts":1643709218025,"q":0,"from":"system.adapter.mytime.0","lc":1643709218025}
                            Server memory publish system.adapter.mytime.0.uptime {"val":1,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server Redis Publish State system.adapter.mytime.0.uptime={"val":1,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server memory publish system.adapter.mytime.0.inputCount {"val":3,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server Redis Publish State system.adapter.mytime.0.inputCount={"val":3,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server memory publish system.adapter.mytime.0.outputCount {"val":9,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server Redis Publish State system.adapter.mytime.0.outputCount={"val":9,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server memory publish system.adapter.mytime.0.compactMode {"val":false,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server Redis Publish State system.adapter.mytime.0.compactMode={"val":false,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            States system redis pmessage */system.adapter.mytime.0.memHeapUsed:{"val":13.79,"ack":true,"ts":1643709218025,"q":0,"from":"system.adapter.mytime.0","lc":1643709218025}
                            States system redis pmessage */system.adapter.mytime.0.uptime:{"val":1,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            States system redis pmessage */system.adapter.mytime.0.inputCount:{"val":3,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            States system redis pmessage */system.adapter.mytime.0.outputCount:{"val":9,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            States system redis pmessage */system.adapter.mytime.0.compactMode:{"val":false,"ack":true,"ts":1643709218026,"q":0,"from":"system.adapter.mytime.0","lc":1643709218026}
                            Server memory publish mytime.0.info.connection {"val":false,"ack":true,"ts":1643709218037,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709214918}
                            Server Redis Publish State mytime.0.info.connection={"val":false,"ack":true,"ts":1643709218037,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709214918}
                            Server Redis Publish State mytime.0.info.connection={"val":false,"ack":true,"ts":1643709218037,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709214918}
                            Server memory publish mytime.0.info.connection {"val":true,"ack":true,"ts":1643709218038,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709218038}
                            Server Redis Publish State mytime.0.info.connection={"val":true,"ack":true,"ts":1643709218038,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709218038}
                            Server Redis Publish State mytime.0.info.connection={"val":true,"ack":true,"ts":1643709218038,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709218038}
                            States system redis pmessage */mytime.0.info.connection:{"val":false,"ack":true,"ts":1643709218037,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709214918}
                            States system redis pmessage */mytime.0.info.connection:{"val":true,"ack":true,"ts":1643709218038,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709218038}
                            2022-02-01 10:53:38.044  - info: mytime.0 (3535) state mytime.0.info.connection changed: false (ack = true)
                            Server memory publish system.adapter.mytime.0.cpu {"val":0,"ack":true,"ts":1643709218040,"q":0,"from":"system.adapter.mytime.0","lc":1643709218040}
                            Server Redis Publish State system.adapter.mytime.0.cpu={"val":0,"ack":true,"ts":1643709218040,"q":0,"from":"system.adapter.mytime.0","lc":1643709218040}
                            Server memory publish system.adapter.mytime.0.cputime {"val":1.24,"ack":true,"ts":1643709218041,"q":0,"from":"system.adapter.mytime.0","lc":1643709218041}
                            Server Redis Publish State system.adapter.mytime.0.cputime={"val":1.24,"ack":true,"ts":1643709218041,"q":0,"from":"system.adapter.mytime.0","lc":1643709218041}
                            States system redis pmessage */system.adapter.mytime.0.cpu:{"val":0,"ack":true,"ts":1643709218040,"q":0,"from":"system.adapter.mytime.0","lc":1643709218040}
                            States system redis pmessage */system.adapter.mytime.0.cputime:{"val":1.24,"ack":true,"ts":1643709218041,"q":0,"from":"system.adapter.mytime.0","lc":1643709218041}
                            2022-02-01 10:53:38.047  - info: mytime.0 (3535) state mytime.0.info.connection changed: true (ack = true)
                            The adapter started successfully.
                               ✔ The adapter starts (6213ms)
                            Server memory publish system.adapter.mytime.0.sigKill {"val":-1,"ack":false,"ts":1643709223038,"q":0,"from":"system.host.testing","lc":1643709223038}
                            Server Redis Publish State system.adapter.mytime.0.sigKill={"val":-1,"ack":false,"ts":1643709223038,"q":0,"from":"system.host.testing","lc":1643709223038}
                            Server Redis Publish State system.adapter.mytime.0.sigKill={"val":-1,"ack":false,"ts":1643709223038,"q":0,"from":"system.host.testing","lc":1643709223038}
                            States system redis pmessage */system.adapter.mytime.0.sigKill:{"val":-1,"ack":false,"ts":1643709223038,"q":0,"from":"system.host.testing","lc":1643709223038}
                            2022-02-01 10:53:43.043  - info: mytime.0 (3535) Got terminate signal TERMINATE_YOURSELF
                            2022-02-01 10:53:43.044  - debug: mytime.0 (3535) main onUnload try
                            2022-02-01 10:53:43.045  - debug: mytime.0 (3535) closeConnections
                            2022-02-01 10:53:43.046  - debug: mytime.0 (3535) deleteObservers
                            2022-02-01 10:53:43.047  - info: mytime.0 (3535) cleaned everything up...
                            2022-02-01 10:53:43.048  - info: mytime.0 (3535) terminating
                            2022-02-01 10:53:43.049  - info: mytime.0 (3535) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            Server memory publish mytime.0.info.connection {"val":false,"ack":true,"ts":1643709223052,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709223052}
                            Server Redis Publish State mytime.0.info.connection={"val":false,"ack":true,"ts":1643709223052,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709223052}
                            Server Redis Publish State mytime.0.info.connection={"val":false,"ack":true,"ts":1643709223052,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709223052}
                            States system redis pmessage */mytime.0.info.connection:{"val":false,"ack":true,"ts":1643709223052,"q":0,"from":"system.adapter.mytime.0","user":"system.user.admin","lc":1643709223052}
                            mytime.0(3535) Redis QUIT received, close connection
                            Server States 127.0.0.1:48802 close Redis connection
                            mytime.0(3535) Redis QUIT received, close connection
                            Server States 127.0.0.1:48804 close Redis connection
                            mytime.0(3535) Redis QUIT received, close connection
                            Server States 127.0.0.1:48806 close Redis connection
                            mytime.0(3535) Redis QUIT received, close connection
                            Server Objects 127.0.0.1:52030 close Redis connection
                            mytime.0(3535) Redis QUIT received, close connection
                            Server Objects 127.0.0.1:52034 close Redis connection
                            mytime.0(3535) Redis QUIT received, close connection
                            Server Objects 127.0.0.1:52032 close Redis connection
                            Server Redis QUIT received, close connection
                            Server Objects 127.0.0.1:52016 close Redis connection
                            Server Redis QUIT received, close connection
                            Server Objects 127.0.0.1:52018 close Redis connection
                            Server Redis QUIT received, close connection
                            Server States 127.0.0.1:48786 close Redis connection
                            Server Redis QUIT received, close connection
                            Server States 127.0.0.1:48788 close Redis connection
                            
                            
                             1 passing (31s)
                            

                            AlCalzone 1 Reply Last reply Reply Quote 0
                            • AlCalzone
                              AlCalzone Developer @OliverIO last edited by

                              @oliverio Ich schau mir das auf Windows mal an. Weil ichs aber grade sehe: Alle Libraries, die nur im Frontend benötigt werden, haben in dependencies nix zu suchen. Die werden beim Kompilieren gebundlet und dann als eine Datei ausgeliefert.

                              Mindestens folgende gehören stattdessen in die devDependencies:

                              "@iobroker/adapter-react": "^2.0.15",
                              "@material-ui/icons": "^4.11.2",
                              "@material-ui/lab": "^4.0.0-alpha.60",
                              "@material-ui/pickers": "^3.3.10",
                              "@material-ui/core": "^4.12.3",
                              "react": "^17.0.2",
                              "react-dom": "^17.0.2",
                              "react-icons": "^4.3.1",
                              "prop-types": "^15.8.1",
                              
                              1 Reply Last reply Reply Quote 0
                              • AlCalzone
                                AlCalzone Developer last edited by

                                Also bei mir läuft's auch unter Windows nicht:

                                npm ERR! code 1
                                npm ERR! path C:\Users\domin\AppData\Local\Temp\test-iobroker.mytime\node_modules\iobroker.vis
                                npm ERR! command failed
                                npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node main.js --install
                                npm ERR! C:\Users\domin\AppData\Local\Temp\test-iobroker.mytime\node_modules\@iobroker\js-controller-adapter\build\lib\adapter\adapter.js:61
                                npm ERR!         throw new Error(`Cannot find ${configFileName}`);
                                npm ERR!         ^
                                npm ERR!
                                npm ERR! Error: Cannot find C:/Users/domin/AppData/Local/Temp/test-iobroker.mytime/iobroker-data/iobroker.json
                                npm ERR!     at new Adapter (C:\Users\domin\AppData\Local\Temp\test-iobroker.mytime\node_modules\@iobroker\js-controller-adapter\build\lib\adapter\adapter.js:61:15)
                                npm ERR!     at Object.<anonymous> (C:\Users\domin\AppData\Local\Temp\test-iobroker.mytime\node_modules\iobroker.vis\main.js:20:24)
                                npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1101:14)
                                npm ERR!     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
                                npm ERR!     at Module.load (node:internal/modules/cjs/loader:981:32)
                                npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
                                npm ERR!     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:79:12)
                                npm ERR!     at node:internal/main/run_main_module:17:47
                                

                                Das liegt wohl wirklich daran, dass beim npm install schon die DB laufen muss. Ich nehm das in meinen PR für die nächste Testing-Version mit auf.

                                apollon77 1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 @AlCalzone last edited by

                                  @alcalzone sagte in Problem beim integrationstest mit github-actions:

                                  Das liegt wohl wirklich daran, dass beim npm install schon die DB laufen muss. Ich nehm das in meinen PR für die nächste Testing-Version mit auf.

                                  Hängen bleiben oder so einen fehler werfen sollte es aber dennoch nicht

                                  AlCalzone 1 Reply Last reply Reply Quote 0
                                  • AlCalzone
                                    AlCalzone Developer @apollon77 last edited by

                                    @apollon77 Im Testing wird alles auf einmal installiert (npm install --production), aber da läuft weder der Controller (weil er gerade auch installiert wird), noch wurde setup first ausgeführt. vis scheint aber davon auszugehen.

                                    apollon77 1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 @AlCalzone last edited by

                                      @alcalzone ich dachte an sich das (zumindestens früher) das install auch geht wennes auch ist ... deswegen -> issue anlegen bei vis!

                                      AlCalzone 1 Reply Last reply Reply Quote 0
                                      • AlCalzone
                                        AlCalzone Developer @apollon77 last edited by

                                        @apollon77 sagte in Problem beim integrationstest mit github-actions:

                                        deswegen -> issue anlegen bei vis!

                                        Ich denke das ist spezifisch ein Problem im Testing-Setup, wo bei der Installation noch gar nichts aus dem ioBroker-Umfeld existiert.

                                        apollon77 1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 @AlCalzone last edited by

                                          @alcalzone Interessant ist: Wenn ich "npm install iobroker.vis" mache dann ist dem post install Skript egal das ioBroker nicht läuft - wie es soll ... warum ist es beim testing nicht?

                                          1 Reply Last reply Reply Quote 0
                                          • OliverIO
                                            OliverIO last edited by

                                            also,
                                            nach dem neu sortieren der dependencies laufen die tests nun durch.
                                            warum das so ist weiß ich nicht.
                                            falls da was fehlte oder ein konflikt entstanden ist, dann sollten die fehlermeldungen auch irgendwie erscheinen. ansonsten ist das wirklich schwierig. rauszufinden.

                                            ich verstehe natürlich, das wenn der test auf unterschiedlichen platformen (github/lokal) unterschiedliche ergebnisse liefert, eine fehlersuche sehr schwer ist.

                                            AlCalzone 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            792
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            3
                                            26
                                            1330
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo