Skip to content

fix: fix null pointer dereference issue when parent task storage registration fails #725

fix: fix null pointer dereference issue when parent task storage registration fails

fix: fix null pointer dereference issue when parent task storage registration fails #725

Triggered via pull request August 25, 2024 04:13
Status Success
Total duration 40m 55s
Artifacts 45
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

e2e-v1.yml

on: pull_request
Matrix: e2e_tests
Fit to window
Zoom out
Zoom in

Annotations

27 warnings
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/manager/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/scheduler/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: build/images/dfdaemon/Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size Digest
cache-list-metadata-e2e-tests-logs Expired
17.3 MB
sha256:95e45f9a7b51bfb80f8bf6d1efb3692870db66227ccf0cd0ad8d9a786be9e2e2
concurent-back-source-e2e-tests-logs Expired
17.3 MB
sha256:0b6c7c7d295142f4decb68164fc5b3d94b26ba7cdcf3099647212868ca675d07
disable-seed-peer-e2e-tests-logs Expired
10 MB
sha256:d765d3927e5c94e840cbc7db1021f4f5ed6c68291365a7c513666c082485ef5b
dragonflyoss~Dragonfly2~219QEE.dockerbuild Expired
30.9 KB
sha256:d7f1cc66a832d79aabbd3e220f2666e27285097bea9cbde0ebe6ef32b8b1805e
dragonflyoss~Dragonfly2~2KD3PH.dockerbuild Expired
31 KB
sha256:88911b1c56455085b93210ece1d758ab1e4b60b34fef885082733740c02f0cac
dragonflyoss~Dragonfly2~3IO87G.dockerbuild Expired
41.2 KB
sha256:45a972a50aadacad1c17a1809f955ad44c8caf6003c0547e792f60737697af72
dragonflyoss~Dragonfly2~3RMV6V.dockerbuild Expired
18.1 KB
sha256:4dbcabc5b6dd8be91e87d503935261b8915f16767a71c2bf9aa6eb4b296e6edf
dragonflyoss~Dragonfly2~5D99AN.dockerbuild Expired
48.5 KB
sha256:e133877d40f6a0e179e132bce9722a87d085f6d1c78f0aaec3f2788bbe17423b
dragonflyoss~Dragonfly2~5E5QD6.dockerbuild Expired
41.4 KB
sha256:e18d646801065b62fbe0de288f6f7742c11416753f0f8545bc73422b6e5739d8
dragonflyoss~Dragonfly2~6O85CN.dockerbuild Expired
47.9 KB
sha256:12fc3c32e5d5055d3cb5ac963599ee3effd6b7f40e263a27c6e5f965acfafcdc
dragonflyoss~Dragonfly2~6PY9EX.dockerbuild Expired
48.4 KB
sha256:7bc954729ce609742aade102e1518fc80de272cad4269591bc5e4f549fcb8cc0
dragonflyoss~Dragonfly2~7PGGU7.dockerbuild Expired
17.7 KB
sha256:8217a2e711e45791e093c0ec7689cfecc07dba773b350b33e61dd4b2bc828254
dragonflyoss~Dragonfly2~AU53YP.dockerbuild Expired
41.3 KB
sha256:ba0fc18c61d7c080c888300635733ce88cb7c1a0b85d81ab2d44817d18737f8d
dragonflyoss~Dragonfly2~BZOEEG.dockerbuild Expired
49.3 KB
sha256:25df0ba79f0ff27c58a5b29e290287ff72938d6f98403f6e27f98d494c06e371
dragonflyoss~Dragonfly2~DKNRPY.dockerbuild Expired
30.3 KB
sha256:a5018ead0d054f9df31d1edffbd77b60212de1b4e9969ae117bc549f59573f0a
dragonflyoss~Dragonfly2~DSMPV7.dockerbuild Expired
48.9 KB
sha256:d5544ac660db52cc570e304963c35e8cc53cbc3a54f5802cf4db8483c4c5d238
dragonflyoss~Dragonfly2~FVGA3G.dockerbuild Expired
48.1 KB
sha256:31a5c5d0d9df3a85bc26b61f9cfb9c70ca1a29a34dd59ceb96d8816e69b0028c
dragonflyoss~Dragonfly2~JJD06M.dockerbuild Expired
30.2 KB
sha256:59a61932c14f41fd25a50699b17cd0e4af20c14fc46e919529cbe31283141fd4
dragonflyoss~Dragonfly2~JRCWMX.dockerbuild Expired
41.8 KB
sha256:83147588aa1463a3c31a346f98f5d38aba6af8b166abe7e3dc00f2d0d585645d
dragonflyoss~Dragonfly2~KEGU0F.dockerbuild Expired
18.2 KB
sha256:25cdbd685afa08c7bdc0fc744a666d7b3f14eba9aaf95d4a32ace8b58e98e4f1
dragonflyoss~Dragonfly2~KI8CT5.dockerbuild Expired
48.4 KB
sha256:5f587eeb3bb0dd6b278747248bba80e3317baece52b2bb5f9c8c865a35a47fb0
dragonflyoss~Dragonfly2~LE641D.dockerbuild Expired
41.6 KB
sha256:b0d2afb092c819080521590686e8e1c5c917426948dc35294908bc537a2a9fef
dragonflyoss~Dragonfly2~LEGMC5.dockerbuild Expired
31.1 KB
sha256:8e7a553cef40d86e2e76ceaa7e5737b794230012ee2576d81a9e3be113ff1043
dragonflyoss~Dragonfly2~M5NKRW.dockerbuild Expired
17.8 KB
sha256:80c6ef2d4472394c81aa3ef4d7534adb340d108c603fb8eb1b20a7949ee8b71f
dragonflyoss~Dragonfly2~MAVJ83.dockerbuild Expired
41 KB
sha256:d360633bcca91f110de6cc3c60c1abc9a5ee69d4f4c5657b491f6ad152e4ec76
dragonflyoss~Dragonfly2~PI14NI.dockerbuild Expired
30.5 KB
sha256:9fb5d11b6500f504611c427896ce61ba089b782cb374de90d43c4b0d51a5a2c6
dragonflyoss~Dragonfly2~QDIPJM.dockerbuild Expired
48.6 KB
sha256:a6649dc12fcf7137b8e6350cb19ddc4d01961857936b7611c3a79dd66127c8bf
dragonflyoss~Dragonfly2~QJMPKP.dockerbuild Expired
18.1 KB
sha256:ee0d87a82bae0d7721f2457885ef26d721ba9c596d1909b36eaa2813bfe91bab
dragonflyoss~Dragonfly2~RB3JJQ.dockerbuild Expired
18.1 KB
sha256:9589f9eeb1219c1ee5cfdc6df6146a6304ac7b3d5da514fe65ac363f4a92e95c
dragonflyoss~Dragonfly2~RDL4YO.dockerbuild Expired
17.8 KB
sha256:a668ef366653b23cad1e72a99efbf6babae8e369a56038bf6cdff5888ba676cb
dragonflyoss~Dragonfly2~RISEVN.dockerbuild Expired
30.5 KB
sha256:e75f1d93bca6b679e2a8216eb2207c91f10e5d5313b8c43dfab8b7a7dcf47f82
dragonflyoss~Dragonfly2~S0SP4O.dockerbuild Expired
42.1 KB
sha256:01cd3b25ad804bf84439eaade871ee8c5c1e754335124608d6e0c70d7ffdbc48
dragonflyoss~Dragonfly2~SVB37H.dockerbuild Expired
48.1 KB
sha256:a9ebc6a388ad9a8b2886e318a9cf375a8d3ac186b16515c2fe8ce059d693fb8c
dragonflyoss~Dragonfly2~SY1BJI.dockerbuild Expired
41.4 KB
sha256:3a4283ce77c82f1ba4655243456a40fba9eeec334d6409b2739952c74176b330
dragonflyoss~Dragonfly2~UPHXX3.dockerbuild Expired
17.8 KB
sha256:00db6d70f04758a0e517589416ee15cd4a503022c9ee0bfa020452790c904200
dragonflyoss~Dragonfly2~VJN31E.dockerbuild Expired
30.5 KB
sha256:ae76d0fb3c151762675f03fa9470fb2d9f58975adec12abd2e9a313efba13699
dragonflyoss~Dragonfly2~W6CIC5.dockerbuild Expired
41.3 KB
sha256:bfd2e30cbfa42a7e2c1a91d9c7675b33fcb2d6e2334fe3978338e7e68e304ba3
dragonflyoss~Dragonfly2~YFMJEO.dockerbuild Expired
30.6 KB
sha256:114eeb19a34a7377f0b60b5de79e4a64cb5ebddd63bdd8024345882f44e9025f
dragonflyoss~Dragonfly2~Z5AES0.dockerbuild Expired
17.8 KB
sha256:83a69cc98983653518b860c905610f2a293cf328c1d131dd8606eee1b8caf36b
grpc-tls-e2e-tests-logs Expired
15.9 MB
sha256:e65806d275d9fd8d933b9f4057834fdb2ee2523fa56c4abaa719c1c52d2a9899
grpc-tls-ipv6-e2e-tests-logs Expired
15.4 MB
sha256:d108a0f21f9a8ca2a4b73d1dffcffc5af5d1cb0287b8ce55085e649228fe41b1
ipv6-e2e-tests-logs Expired
15.8 MB
sha256:d1d9d34eb01821235714173a0a5c24c244ab45e0059a45826c77e2b13a7a2bd3
normal-e2e-tests-logs Expired
16.3 MB
sha256:c61639aadd9af8afa94125cf0e023d7a4be084b7b910a0737804a75995e2f850
split-running-tasks-e2e-tests-logs Expired
16.4 MB
sha256:c045ee82c48e5eab15780afd0a65fdae353aad193d32ba6e781e0582699bf5ed
write-buffer-size-e2e-tests-logs Expired
17.1 MB
sha256:968623d1a1ace70b2807799edc452eab078bbfc4cd506bf2a5ecbaeadd20e26b