id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
656583829 | Pinning integration: descope stats from Settings screen
Initial Settings mockups in WebUI include columns with basic stats: utilized storage as "Files" and "Bandwidth Used":
Problem
Pinning Service API spec does not provide endpoint for reading this information.
Additionally, after sync with @jacobheun @aschmahmann and @alanshaw we decided to make API secrets write-only in go/js-ipfs config for security reasons. This means WebUI won't be able to read API secret and make remote calls on its own.
Solutions
We have two ways of tackling this:
weeks: add /stats endpoint to Pinning Service API and then support for it needs to land in go/js-ipfs and webui
or
hours: descope this from MVP and remove "Files" and "Bandwidth Used" columns from Settings screen. User will still be able to check stats via three dot menu and a link to pinning service website.
Suggested solution
I don't believe vaue added by those columns is worth additional complexity and additional work on Pinning Service and Core Impl. WG ends – are we ok with descoping them from MVP?
cc @jacobheun @jessicaschilling @rafaelramalho19 for quick temperature check, before I escalate this upstream
@lidel while it's a very nice feature to have I agree we should not include it in the initial MVP work. It's not necessary for initial functionality and would be easy to add later without needing to change the existing spec.
+1, but let's be sure to consider thoroughly for post-MVP work.
I’d really like to keep this in scope if possible. It helps answer the question of “which pinning service am I using) without having to go check a bunch of different sites, which would be really annoying. If we need to replace - is there something we can replace it with to give that signal?
@momack2 Not suggesting to remove the rows themselves, rather just the "files" and "bandwidth used" columns.
We discussed this briefly during yesterday's review call.
My takeaway was we are ok with removing storage/bandwidth stats, as long we replace them with something that keeps "usage signal" to the user.
Potential candidate is "pin count" – number coud be read from count field returned by GET /pins?status=pinned in Pinning Service API (but we need to figure out how to expose this value over go-ipfs' HTTP API).
We could also add PinStatus.size field to indicate the size pinned DAG uses at the pinning service, but it brings similar question on how to expose it to WebUI from go-ipfs.
+1 for "pin count" being a good usage signal, at least for this version of the API. I suspect some others will emerge in time as more pinning services come on as adopters.
@lidel Are we OK to close this issue now that we're proceeding with "pin count"?
Yes, I talked with @aschmahmann and iiuc we will have some type of stat command that returns the number of pins in each state (queued/pinning/pinned/failed)
| gharchive/issue | 2020-07-14T12:44:38 | 2025-04-01T06:39:06.209194 | {
"authors": [
"jacobheun",
"jessicaschilling",
"lidel",
"momack2"
],
"repo": "ipfs-shipyard/ipfs-webui",
"url": "https://github.com/ipfs-shipyard/ipfs-webui/issues/1544",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
468223801 | Create 051-new-ipfs-release-process.md
First draft (aka outline) of explaining the new IPFS release process
Most probably, the best description of the release process should be https://github.com/ipfs/go-ipfs/blob/master/docs/releases.md. To land the new refreshed idea on people's heads, we can create an illustration so that people get it right away. Watchathink?
@momack2 thanks for the awesome review! I've addressed all but the two open comments and have reworked the background section and the lead paragraph to the main main section (renaming it from "Actions" to "Release Process")
@alanshaw LGTY?
@momack2 I've updated the beginning given @alanshaw's feedback. LGTY?
| gharchive/pull-request | 2019-07-15T16:31:52 | 2025-04-01T06:39:06.211972 | {
"authors": [
"Stebalien",
"daviddias",
"momack2"
],
"repo": "ipfs/blog",
"url": "https://github.com/ipfs/blog/pull/266",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
342408182 | ipfs-pack bag
Just a quick question
Is the ipfs-pack bag available in the latest version 0.6.0?
No. Neither car nor bag have been implemented, as far as I can tell.
ahaa.... Thanks
| gharchive/issue | 2018-07-18T16:44:02 | 2025-04-01T06:39:06.289448 | {
"authors": [
"Stebalien",
"ayham-madi"
],
"repo": "ipfs/ipfs-pack",
"url": "https://github.com/ipfs/ipfs-pack/issues/35",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
324782073 | PubSub API
Could some one explain how I'm supposed to properly use the subscribe part of the pubsub api? I'm new to multithreading and concurrency and I'm finding it really confusing. I'm using scala right now, but any java examples would be a huge help!
Thank you in advance
Hi! It's still a work in progress, but you can look at the tests for it:
https://github.com/ipfs/java-ipfs-api/blob/master/src/test/java/io/ipfs/api/APITest.java#L410
| gharchive/issue | 2018-05-21T04:13:06 | 2025-04-01T06:39:06.291050 | {
"authors": [
"abueide",
"ianopolous"
],
"repo": "ipfs/java-ipfs-api",
"url": "https://github.com/ipfs/java-ipfs-api/issues/73",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
300786265 | using api.get()
how do you use it? it's not clear from what's provided in the readme nor the go-ipfs docs.
my code looks like:
try! api.get(multihash) {
(result: ...) //not sure how to proceed
...
}
nevermind got itt
| gharchive/issue | 2018-02-27T20:45:38 | 2025-04-01T06:39:06.321339 | {
"authors": [
"samirry"
],
"repo": "ipfs/swift-ipfs-api",
"url": "https://github.com/ipfs/swift-ipfs-api/issues/11",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2217164112 | 🛑 CounterApi (brochure) is down
In e65fde2, CounterApi (brochure) (https://counterapi.com/) was down:
HTTP code: 502
Response time: 74 ms
Resolved: CounterApi (brochure) is back up in 1c85157 after 9 minutes.
| gharchive/issue | 2024-03-31T20:06:52 | 2025-04-01T06:39:06.328149 | {
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/1091",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2443920886 | 🛑 NowBoarding (tokyo) is down
In 6d98dd8, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:
HTTP code: 502
Response time: 63 ms
Resolved: NowBoarding (tokyo) is back up in 0406ea8 after 7 minutes.
| gharchive/issue | 2024-08-02T03:26:58 | 2025-04-01T06:39:06.330537 | {
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/1947",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2573995707 | 🛑 NowBoarding (tokyo) is down
In 8b87268, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: NowBoarding (tokyo) is back up in b952689 after 1 hour, 38 minutes.
| gharchive/issue | 2024-10-08T19:12:05 | 2025-04-01T06:39:06.333169 | {
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/2118",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2690890192 | 🛑 NowBoarding (tokyo) is down
In 1c1826c, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: NowBoarding (tokyo) is back up in 16eeef3 after 10 minutes.
| gharchive/issue | 2024-11-25T14:14:45 | 2025-04-01T06:39:06.335863 | {
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/2996",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2712210777 | 🛑 NowBoarding (tokyo) is down
In 4b572ab, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: NowBoarding (tokyo) is back up in d957cf9 after 5 minutes.
| gharchive/issue | 2024-12-02T14:46:38 | 2025-04-01T06:39:06.338264 | {
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/3167",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1191533198 | 🛑 Invitation (og.invt.co - v1) is down
In 42a4e64, Invitation (og.invt.co - v1) (https://og.invt.co/felix.png?fontSize=%40felix&theme=light&md=1&images=https%3A%2F%2Flh3.googleusercontent.com%2Fa-%2FAOh14GjUk2VKmkWxpgWZgY0CXWRFi_k6t7f2MBSsfSxR%3Ds96-c) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Invitation (og.invt.co - v1) is back up in 58dc321.
| gharchive/issue | 2022-04-04T09:52:27 | 2025-04-01T06:39:06.341787 | {
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/458",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2329043323 | Add: KTIV-DT6
Channel Name
KTIV-DT6
Alternative Names (optional)
No response
Network (optional)
Outlaw
Owners (optional)
Gray Television
Country
US
Subdivision (optional)
US-IA
City (optional)
Sioux City
Broadcast Area
c/US
Languages
eng
Categories (optional)
entertainment
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://publicfiles.fcc.gov/tv-profile/KTIV
Logo
https://static.wikia.nocookie.net/logopedia/images/c/c2/Outlaw_The_Western_Channel_2024.svg/revision/latest/scale-to-width-down/250?cb=20240103031057
Notes
No response
KTIVDT6.us: "logo" with value "https://static.wixstatic.com/media/c9b69f_d1a226f6aeb9451bb1b1807473228d0a~mv2.png/v1/fill/w_314,h_236,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/c9b69f_d1a226f6aeb9451bb1b1807473228d0a~mv2.png"
Edited
| gharchive/issue | 2024-06-01T09:46:16 | 2025-04-01T06:39:06.350556 | {
"authors": [
"PopeyeTheSai10r",
"ProPontifex"
],
"repo": "iptv-org/database",
"url": "https://github.com/iptv-org/database/issues/12014",
"license": "Unlicense",
"license_type": "permissive",
"license_source": "github-api"
} |
2125295167 | Remove: LoLo TV [LV]
Channel ID (required)
LoloTV.lv
Reason (required)
Duplicate
Notes
Duplicate of Pingviins.lv
Needs to be fixed in epg
| gharchive/issue | 2024-02-08T14:20:46 | 2025-04-01T06:39:06.352293 | {
"authors": [
"BellezaEmporium",
"Dum4G"
],
"repo": "iptv-org/database",
"url": "https://github.com/iptv-org/database/issues/9467",
"license": "Unlicense",
"license_type": "permissive",
"license_source": "github-api"
} |
312353528 | rpmlib: RPM reader API
This issue tracks the ability to read RPM package files. Presently no support is available.
Some reference information on the API is available here, courtesy the Fedora RPM Guide:
C API: TBD
Python API: https://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04.html
#11 is fixed, and #19 added transaction set support, so this is ready to work on for any interested takers.
The easiest bindings are rpmInstall() and rpmErase() in lib/rpminstall.c, copying rust args into the needed structure. There are also similar interfaces for query/verify/sign available. All the tables for popt option processing are available for needed flags if you also bind libpopt.
If you want a lower level interface, use rpmReadPackageFile() which verifies package signatures.
I would avoid doing similar to Python interfaces which were mis-designed to accomodate "I don't want to verify signatures! I don't want to use a transaction!" politics from a long time ago.
| gharchive/issue | 2018-04-08T23:44:46 | 2025-04-01T06:39:06.400578 | {
"authors": [
"n3npq",
"tony-iqlusion"
],
"repo": "iqlusion-io/crates",
"url": "https://github.com/iqlusion-io/crates/issues/14",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
728796415 | Contribute mbu
Fixed Dockerfile to build intel-qs automatically
Fixed get_started_examples notebook to work (fixed lib path, fixed setting of RNG)
Hi @mbuchberger1967
Thanks for the pull request!
I resolved the conflicts indicated by github (it appeared as "merge branch development into contribute-mbu").
I also updated the workflow to avoid deprecated actions.
Gian
| gharchive/pull-request | 2020-10-24T14:05:14 | 2025-04-01T06:39:06.405047 | {
"authors": [
"giangiac",
"mbuchberger1967"
],
"repo": "iqusoft/intel-qs",
"url": "https://github.com/iqusoft/intel-qs/pull/35",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
478016930 | Add Internet Connection Check To Elegent
https://trello.com/c/E8P2V8VP/7-internet-connection-check
Dear @AZIMAT, Please leave an issue for this PR and then in the description of your PR leave a comment that this PR closes or resolves or fixes #999. the 999 is a sample for your issue number. Thanks a lot
Hello @amerllica Shall I Open An Issue For Trello TO DOs?
well done @AZIMAT
I will add a contribution guide in readme, please open a new issue
We also need to discuss about the included package ✌️
| gharchive/pull-request | 2019-08-07T16:05:09 | 2025-04-01T06:39:06.409439 | {
"authors": [
"AZIMAT",
"amerllica",
"ramyareye"
],
"repo": "iran-react-community/elegant-react-native",
"url": "https://github.com/iran-react-community/elegant-react-native/pull/19",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1402345184 | Correctness failure for Stable Diffusion on Vulkan
What happened?
Using the stable diffusion IR from here: https://storage.googleapis.com/shark_tank/prashant_nod/stable_diff/stable_diff_torch.mlir
(this is the IR without the maxf change) vulkan produces incorrect results.
Vulkan:
$ ./stable_diff.sh
EXEC @forward
result[0]: hal.buffer_view
2x4x64x64xf32=[[[-0.79174 0.0641071 -0.112293 -0.167857 -0.126047 -0.130796 -0.148907 -0.160596 -0.161737 -0.158119
CPU:
$ ./stable_diff_cpu.sh
EXEC @forward
result[0]: hal.buffer_view
2x4x64x64xf32=[[[-1.15407 -0.181712 -0.0600768 -0.0311085 -0.0181836 0.0495643 0.0556104 0.0524104 0.0183131 0.00394016
When tracing the dispatches with --iree-flow-trace-dispatch-tensors, it reveals the following problematic dispatch
flow.executable private @forward_dispatch_470 {
flow.executable.export public
@forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1
workgroups(%arg0: index, %arg1: index, %arg2: index, %arg3: index) ->
(index, index, index) {
%x, %y, %z = flow.dispatch.workgroup_count_from_dag_root %arg0,
%arg1, %arg2, %arg3
flow.return %x, %y, %z : index, index, index
}
builtin.module {
func.func
@forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1(%arg0: !flow.dispatch.tensor<readonly:2x2560x8x8xf32>, %arg1: !flow.dispatch.tensor<readonly:1280x2560x1x1xf32>, %arg2: !flow.dispatch.tensor<readonly:1280xf32>, %arg3: !flow.dispatch.tensor<readonly:2x1280x8x8xf32>, %arg4: !flow.dispatch.tensor<readonly:1280xf32>, %arg5: !flow.dispatch.tensor<writeonly:2x1280x8x8xf32>) {
%cst = arith.constant 0.000000e+00 : f32
%0 = flow.dispatch.tensor.load %arg0, offsets = [0, 0, 0, 0], sizes = [2, 2560, 8, 8], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:2x2560x8x8xf32> -> tensor<2x2560x8x8xf32>
%1 = flow.dispatch.tensor.load %arg1, offsets = [0, 0, 0, 0], sizes = [1280, 2560, 1, 1], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:1280x2560x1x1xf32> -> tensor<1280x2560x1x1xf32>
%2 = flow.dispatch.tensor.load %arg2, offsets = [0], sizes = [1280], strides = [1] : !flow.dispatch.tensor<readonly:1280xf32> -> tensor<1280xf32>
%3 = flow.dispatch.tensor.load %arg3, offsets = [0, 0, 0, 0], sizes = [2, 1280, 8, 8], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:2x1280x8x8xf32> -> tensor<2x1280x8x8xf32>
%4 = flow.dispatch.tensor.load %arg4, offsets = [0], sizes = [1280], strides = [1] : !flow.dispatch.tensor<readonly:1280xf32> -> tensor<1280xf32>
%5 = linalg.init_tensor [2, 1280, 8, 8] : tensor<2x1280x8x8xf32>
%6 = linalg.fill ins(%cst : f32) outs(%5 : tensor<2x1280x8x8xf32>) -> tensor<2x1280x8x8xf32>
%7 = linalg.conv_2d_nchw_fchw {dilations = dense<1> : vector<2xi64>, strides = dense<1> : vector<2xi64>} ins(%0, %1 : tensor<2x2560x8x8xf32>, tensor<1280x2560x1x1xf32>) outs(%6 : tensor<2x1280x8x8xf32>) -> tensor<2x1280x8x8xf32>
%8 = linalg.generic {indexing_maps = [#map4, #map5, #map4, #map5, #map4], iterator_types = ["parallel", "parallel", "parallel", "parallel"]} ins(%7, %2, %3, %4 : tensor<2x1280x8x8xf32>, tensor<1280xf32>, tensor<2x1280x8x8xf32>, tensor<1280xf32>) outs(%5 : tensor<2x1280x8x8xf32>) {
^bb0(%arg6: f32, %arg7: f32, %arg8: f32, %arg9: f32, %arg10: f32):
%9 = arith.addf %arg8, %arg9 : f32
%10 = arith.addf %arg6, %arg7 : f32
%11 = arith.addf %10, %9 : f32
linalg.yield %11 : f32
} -> tensor<2x1280x8x8xf32>
flow.dispatch.tensor.store %8, %arg5, offsets = [0, 0, 0, 0], sizes = [2, 1280, 8, 8], strides = [1, 1, 1, 1] : tensor<2x1280x8x8xf32> -> !flow.dispatch.tensor<writeonly:2x1280x8x8xf32>
return
}
}
}
This dispatch is run twice in both CPU and Vulkan and produces correct results the first time it is invoked, but incorrect results the second time.
CPU Dispatch 1:
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 inputs ===
2x2560x8x8xf32=[[[3.6198
5.94259 5.895 5.52787 4.73762 4.97694 5.66628 3.86918][1.77425 2.63694
3.83037 3.30376 2.26205 3.52117 4.30773 2.55794][4.07651 4.98481 6.56503
5.85291 5.12699 6.54789 6.4936
1280x2560x1x1xf32=[[[0.00338601]][[0.0174164]][[-0.0049711]][[0.0294332]][[-0.00329635]][[-0.0144514]][[0.0100105]][[-0.0189708]][[0.00737147]][[-0.0111495]][[-0.0269729]][[-0.0129512]][[0.036161]][[-
1280xf32=0.00725812
0.0126243 0.0165255 0.0424039 -0.0191151 -0.0237755 -0.011133 0.0299926
-0.0127131 0.0199945 -0.00217063 0.0142683 0.0411093 0.0597119
-0.0102172 0.0363883 0.0162222 -0.0111609 0.0
2x1280x8x8xf32=[[[2.54439
2.13727 0.51493 0.606989 1.89327 0.513521 0.426492 -1.22695][0.243956
-0.0386933 -1.3011 -0.774492 0.139363 -1.46699 -1.97472
-2.25226][1.48181 1.59442 1.35016 2.31898 3.4753
1280xf32=0.00103825
0.00766396 0.0142408 0.0475349 -0.0188567 -0.0201855 -0.016479 0.0347956
-0.0136932 0.0202214 -0.00380049 0.0105387 0.0390535 0.0531989
-0.00855511 0.0296064 0.0148761 -0.0138457 0
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 outputs ===
2x1280x8x8xf32=[[[-0.53278
-0.59929 -2.00319 -1.73988 -0.667898 -1.92362 -1.79642
-2.3996][-2.32789 -2.58059 -3.69251 -3.3325 -2.64366 -4.46041 -5.11464
-4.20118][-1.42109 -2.18883 -1.23008 -0.60974 0
Vulkan Dispatch 1:
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 inputs ===
2x2560x8x8xf32=[[[3.61984
5.94261 5.8951 5.52793 4.73767 4.97701 5.66644 3.86915][1.77428 2.63686
3.83043 3.30371 2.26201 3.52115 4.30791 2.55795][4.07682 4.98482 6.5652
5.853 5.12705 6.54796 6.49388
1280x2560x1x1xf32=[[[0.00338601]][[0.0174164]][[-0.0049711]][[0.0294332]][[-0.00329635]][[-0.0144514]][[0.0100105]][[-0.0189708]][[0.00737147]][[-0.0111495]][[-0.0269729]][[-0.0129512]][[0.036161]][[-
1280xf32=0.00725812
0.0126243 0.0165255 0.0424039 -0.0191151 -0.0237755 -0.011133 0.0299926
-0.0127131 0.0199945 -0.00217063 0.0142683 0.0411093 0.0597119
-0.0102172 0.0363883 0.0162222 -0.0111609 0.0
2x1280x8x8xf32=[[[2.54456
2.13739 0.514955 0.607036 1.89338 0.513543 0.426497 -1.227][0.24413
-0.0386549 -1.30109 -0.774417 0.13953 -1.467 -1.97476 -2.25243][1.48189
1.59437 1.35009 2.31903 3.47545 1.
1280xf32=0.00103825 0.00766396
0.0142408 0.0475349 -0.0188567 -0.0201855 -0.016479 0.0347956 -0.0136932
0.0202214 -0.00380049 0.0105387 0.0390535 0.0531989 -0.00855511
0.0296064 0.0148761 -0.0138457 0
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 outputs ===
2x1280x8x8xf32=[[[-0.532302
-0.59896 -2.00301 -1.73973 -0.667703 -1.92351 -1.79623
-2.39929][-2.32742 -2.58033 -3.69232 -3.33225 -2.64334 -4.46028 -5.11448
-4.20095][-1.42078 -2.18876 -1.23 -0.609557
CPU Dispatch 2:
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 inputs ===
2x2560x8x8xf32=[[[-0.53278
-0.59929 -2.00319 -1.73988 -0.667898 -1.92362 -1.79642
-2.3996][-2.32789 -2.58059 -3.69251 -3.3325 -2.64366 -4.46041 -5.11464
-4.20118][-1.42109 -2.18883 -1.23008 -0.60974 0
1280x2560x1x1xf32=[[[-0.00274814]][[-0.00830614]][[-0.0135242]][[-0.0132497]][[-0.0126576]][[-0.000716772]][[0.0133444]][[0.0104749]][[0.0101474]][[-0.00608126]][[0.014927]][[0.00619813]][[-5.89535E-0
1280xf32=0.0163751
0.00127905 -0.00891779 0.0125289 0.0203168 0.0336943 -0.00530554
-0.0178778 0.000440216 -0.0127124 -0.0245813 -0.0183712 0.0217959
0.00401268 0.0329679 0.00990345 0.0181513 0.050881
2x1280x8x8xf32=[[[-0.509639
-1.50538 1.47679 2.24422 2.62407 2.9938 2.89996 0.66565][0.821302
0.233143 1.80799 3.92045 2.8173 3.50018 3.4897 3.25632][2.10995 -1.68188
3.26023 3.87505 3.47158 3.84622 3
1280xf32=0.016883 0.00528681
-0.00610743 0.0147028 0.0254413 0.0318061 -0.00147928 -0.0146085
0.00126152 -0.00792862 -0.0230432 -0.0153743 0.0172426 0.00446033
0.0259711 0.00516712 0.0165293 0.0495716
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 outputs ===
2x1280x8x8xf32=[[[-1.44686
-1.16947 2.47285 3.4618 4.01272 3.3545 3.06969 1.33065][-0.364352
-1.29714 0.42169 2.51774 1.42134 1.59979 1.73792 3.76969][1.34496
-2.86209 2.72345 2.93076 2.55507 2.42448
Vulkan Dispatch 2:
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 inputs ===
2x2560x8x8xf32=[[[-0.532302
-0.59896 -2.00301 -1.73973 -0.667703 -1.92351 -1.79623
-2.39929][-2.32742 -2.58033 -3.69232 -3.33225 -2.64334 -4.46028 -5.11448
-4.20095][-1.42078 -2.18876 -1.23 -0.609557
1280x2560x1x1xf32=[[[-0.00274814]][[-0.00830614]][[-0.0135242]][[-0.0132497]][[-0.0126576]][[-0.000716772]][[0.0133444]][[0.0104749]][[0.0101474]][[-0.00608126]][[0.014927]][[0.00619813]][[-5.89535E-0
1280xf32=0.0163751
0.00127905 -0.00891779 0.0125289 0.0203168 0.0336943 -0.00530554
-0.0178778 0.000440216 -0.0127124 -0.0245813 -0.0183712 0.0217959
0.00401268 0.0329679 0.00990345 0.0181513 0.050881
2x1280x8x8xf32=[[[-0.509756
-1.50548 1.47673 2.24419 2.62401 2.9938 2.89998 0.665559][0.820966
0.232818 1.80739 3.92 2.81671 3.49984 3.48955 3.25614][2.10991 -1.68236
3.25966 3.87445 3.47086 3.84586 3
1280xf32=0.016883 0.00528681
-0.00610743 0.0147028 0.0254413 0.0318061 -0.00147928 -0.0146085
0.00126152 -0.00792862 -0.0230432 -0.0153743 0.0172426 0.00446033
0.0259711 0.00516712 0.0165293 0.0495716
=== forward_dispatch_470::forward_dispatch_470_conv_2d_nchw_fchw_2x1280x8x8x2560x1x1 outputs ===
2x1280x8x8xf32=[[[0.613366
-1.04614 1.52429 2.5593 2.9567 3.20548 2.77693 1.2229][1.81082 1.50064
1.98906 4.56729 3.42117 4.55522 3.85218 4.03883][3.28981 -0.217535
4.63322 5.17798 4.88184 5.44859 4.4
Steps to reproduce your issue
Vulkan compile command:
iree-compile stable_diff/stable_diff_torch.mlir --iree-llvm-target-cpu-features=host -iree-vulkan-target-triple=ampere-rtx2070-linux --iree-stream-resource-index-bits=64 --iree-vm-target-index-bits=64 --iree-input-type=tm_tensor --iree-hal-target-backends=vulkan-spirv -o stable_diff/stable_diff.vmfb
iree-run-module --device=vulkan --entry_function=forward --function_input=2x4x64x64xf32 --function_input=1xf32 --function_input=2x77x768xf32 --module_file=stable_diff/stable_diff.vmfb
CPU compile command:
iree-compile stable_diff/stable_diff_torch.mlir --iree-llvm-target-cpu-features=host --iree-stream-resource-index-bits=64 --iree-vm-target-index-bits=64 --iree-input-type=tm_tensor --iree-hal-target-backends=llvm-cpu -o stable_diff/stable_diff_cpu.vmfb
iree-run-module --device=local-task --entry_function=forward --function_input=2x4x64x64xf32 --function_input=1xf32 --function_input=2x77x768xf32 --module_file=stable_diff/stable_diff_cpu.vmfb
What component(s) does this issue relate to?
Compiler, Runtime
Version information
This was with SHARK-Runtime with most recent upstream iree commit 2f0f4254d5d4ad6136c8fd335bf9a29c7c80ebd1 with an RTX2070
Additional context
Currently trying to repro full model results with the maxf changes, on 6900xt, and on ToM. Additionally, when using --iree-flow-enable-conv-nchw-to-nhwc in SHARK-Runtime the results seem to be correct, although I haven't looked through to find the corresponding dispatch yet.
$ ./stable_diff_converted.sh
EXEC @forward
result[0]: hal.buffer_view
2x4x64x64xf32=[[[-1.154 -0.181567 -0.0598249 -0.0309028 -0.0180597 0.0495675 0.0555883 0.0523811 0.0182862 0.00391532
Edit
I found that Stable Diffusion used to be working and these accuracy errors first appear with cb78faea7cdb392e2641967343b42455415a2c1a.
Yup I can repro this issue at the tip de86d64ce. Given you've already identified the problematic dispatch and it looks the issue is sensitive to the input, do you still have the full inputs for the second invocation handy? If so could you upload it somewhere? (The model is huge; it would take me a while to redo what you have there..)
I uploaded the inputs/outputs here as .npy files: https://console.cloud.google.com/storage/browser/shark_tank/quinn/sd_problem_dispatch_values;tab=objects?pageState=("StorageObjectListTable":("f":"%255B%255D"))&authuser=0&prefix=&forceOnObjectsSortingFiltering=false
Let me know if you'd like this in a different format. The files are labelled dispatch<1/2>_input<arg>_cpu/vulkan.npy so the inputs map to the same order as the arguments of the dispatch, and there are inputs from both dispatches and both cpu and vulkan.
Okay this is a fun one.. I tried to feed the same set of inputs for dispatch 1/2 cpu/vulkan to the problematic dispatch, compiled to both cpu and vulkan, the result is always the same. However if I just disable the SPIRVVectorizePass entirely in the pipeline the the stable diffusion result is correct. It indicates that there is an issue in some combination of vector patterns maybe. This is gonna be hard to figure out without a repro that shows different results on the dispatch standalone..
Closing as the issue is fixed by recent changes :)
| gharchive/issue | 2022-10-09T17:39:48 | 2025-04-01T06:39:06.434608 | {
"authors": [
"antiagainst",
"qedawkins"
],
"repo": "iree-org/iree",
"url": "https://github.com/iree-org/iree/issues/10712",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
499342610 | changelog: added changelog for 0.8.
NOTE: Please read the Contributing.md guidelines before submitting your patch:
https://github.com/iresty/apisix/blob/master/Contributing.md#how-to-add-a-new-feature-or-change-an-existing-one
Summary
SUMMARY_HERE
Full changelog
[Implement ...]
[Add related tests]
...
Issues resolved
Fix #XXX
We can add a new chapter about doc.
We should also check the commit log of the dependent libraries, which will include some new features.
We should also check the commit log of the dependent libraries, which will include some new features.
lua-resty-ipmatcher:
support IPv6: IP white/black list, route.
resty-radixtree:
allow to specify multiple host, remote_addr and uri.
allow to define user-function to filter request.
use lua-resty-ipmatcher instead of lua-resty-iputils, lua-resty-ipmatcher matches fast and support IPv6.
| gharchive/pull-request | 2019-09-27T09:37:34 | 2025-04-01T06:39:06.442116 | {
"authors": [
"membphis",
"moonming"
],
"repo": "iresty/apisix",
"url": "https://github.com/iresty/apisix/pull/619",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
196454714 | Handle Rate Limits
When a rate limit is exceeded, a status of 429 Too Many Requests will be returned.
not implemented this! will have to take a look at adding it for the get/post/delete methods in the library
I believe you addressed this. Just assigning it to myself so I can confirm.
| gharchive/issue | 2016-12-19T16:18:33 | 2025-04-01T06:39:06.519057 | {
"authors": [
"irufus",
"robevansuk"
],
"repo": "irufus/gdax-java",
"url": "https://github.com/irufus/gdax-java/issues/4",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2205543174 | no output
Describe the bug
I followed the tutorial, but unfortunately, I'm not getting any output in PyCharm. What could be the issue?
Expected Behaviour
...
Actual Behaviour
If applicable, include screenshots!
from TikTokLive import TikTokLiveClient
from TikTokLive.events import ConnectEvent, CommentEvent
# Create the client
client: TikTokLiveClient = TikTokLiveClient(unique_id="@isaackogz")
# Listen to an event with a decorator!
@client.on(ConnectEvent)
async def on_connect(event: ConnectEvent):
print(f"Connected to @{event.unique_id} (Room ID: {client.room_id}")
# Or, add it manually via "client.add_listener()"
async def on_comment(event: CommentEvent) -> None:
print(f"{event.user.nickname} -> {event.comment}")
client.add_listener(CommentEvent, on_comment)
if __name__ == '__main__':
# Run the client and block the main thread
# await client.start() to run non-blocking
client.run()
Package Version
My version of TikTokLive is v6.0.3.
Operating System
[ ] Windows
[ ] Linux
[x] MacOS
[ ] Other (Specifically, ...)
Anything Else
The same problem as(https://github.com/isaackogan/TikTokLive/issues/193#issue-2177314885)
For one, @isaackogz is my TikTok, and I don't go live...
您好，邮件已收到。
For one, @isaackogz is my TikTok, and I don't go live...
Of course, this must be known. I changed the anchor id.
Could you enable debug by setting the loglevel of to DEBUG, and print your debug?
Could you enable debug by setting the loglevel of to DEBUG, and print your debug? It may be too large, in which case upload a file to pastebin and send the link.
client.logger.setLevel("DEBUG")
After setting the log level, the execution prompt timed out.
client._logger = TikTokLiveLogHandler.get_logger(
level=LogLevel.DEBUG
)
After setting the log level, the execution prompt timed out.
TikTokLive.client.web.routes.fetch_sign.SignAPIError: [EMPTY_PAYLOAD] Sign API returned an empty request. Are you being detected by TikTok?
Do you need to log in?
Are you from a country where TikTok is banned?
Closing in 48h if stale
Are you from a country where TikTok is banned?
P.S. The timeout was a coincidence, not sure what causes it for you. Sign API returned an empty request. Are you being detected by TikTok? tells me your connection request was blocked.
Yes, but I have no problem on linux. The problem is only on mac. Of course, vpn enabled.
| gharchive/issue | 2024-03-25T11:39:58 | 2025-04-01T06:39:06.540939 | {
"authors": [
"JiehuiSun",
"isaackogan"
],
"repo": "isaackogan/TikTokLive",
"url": "https://github.com/isaackogan/TikTokLive/issues/199",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
645642516 | Repeated request for authentication
Each time I launch PresenceLight it re-authenticate via the web browser.
I have tried uninstalling and reinstalling. I have installed 2.0.69.0 using the appxbundle.
Where are the credentials stored so I can clear them completely and see if I can get it to save?
hmmm odd, here is the token area. If you have issues let me know
C:\Users\username\AppData\Local\Packages\37828IsaacLevin.197278F15330A_zfcjmmeb3zeaa\LocalState\token.json
Oh I get that also - I thought that was expected on restart (which is a pain but thought it was needed!)... I have the token file as noted but it does prompt on every restart.
I wiped that whole 37828IssacLevin directory and still get the same result. Could our organization disallow storage of cached credentials? I'll d/l the code later and trace the run.
All the code to do this is in SettingsService. I try to create the file where the exe is (program files) and if that fails I fall back to local storage. I can take a look and see what happens attaching to VS
2.0.75.0 - still prompts for auth on every start of the app.
I will need to wait to test as VS Attach to deployed WPF isn't working quite right with .NET 5
It might be the Azure AD permissions granted when the app is installed from the package / store. I wonder if the cause is the conditional policy setup by our org for MFA.
@warthurton any update?
The same happens for me. However, I've installed PresenceLight via chocolatey, so I guess it's not related to the Microsoft Store.
Installed the same way. @thoemmi have you looked at the token file mentioned above?
@warthurton any update?
I'm having problems getting it to work when I compile myself. I have been swamped lately so I haven't been able to spend as much time working on it as I wish.
@isaacrlevin Yes, there's a toke.json. However, it's a binary file, so I cannot read its content.
This is now fixed in Nightly. The token is moved to a location that PresenceLight has guaranteed write access to.
@thoemmi can you validate?
Unfortunately, 3.0.5 does not fix the issue. May I should give the Microsoft Store version a try?
3.0.13 is the one you want. Available by nightly install
I can confirm that 3.0.13 fixed the issue :+1:
Sorry for the delay. I also can confirm resolution of the error.
| gharchive/issue | 2020-06-25T15:10:37 | 2025-04-01T06:39:06.548218 | {
"authors": [
"isaacrlevin",
"sborg-ms",
"thoemmi",
"warthurton"
],
"repo": "isaacrlevin/PresenceLight",
"url": "https://github.com/isaacrlevin/PresenceLight/issues/76",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1694209486 | Reduce memory usage by only creating one timer
This reduces memory usage and also speeds up the .set calls by a factor of 2.6.
Thanks, this is a very elegant improvement. Published on 1.3.0, also went ahead and made cache.cancelTimer() a first-class public method.
| gharchive/pull-request | 2023-05-03T14:38:34 | 2025-04-01T06:39:06.551250 | {
"authors": [
"isaacs",
"marcbachmann"
],
"repo": "isaacs/ttlcache",
"url": "https://github.com/isaacs/ttlcache/pull/25",
"license": "ISC",
"license_type": "permissive",
"license_source": "github-api"
} |
2355734147 | [화면개발] 확인 버튼 동작 이상함
2번째 페이지에서 확인버튼 누르면 취소됨
수정 완료
| gharchive/issue | 2024-06-16T12:30:36 | 2025-04-01T06:39:06.615524 | {
"authors": [
"isliese"
],
"repo": "isliese/ParkingZoneManagementSystemForDisabled",
"url": "https://github.com/isliese/ParkingZoneManagementSystemForDisabled/issues/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
721291428 | Unable to set any other color other than white to denote a 0 value in a heatmap
I wish to have a heatmap with a 0 value corresponding to red and a 1 value corresponding to white in the Clustergrammer JS Module. However this seems unachievable by any parametric changes. The only option provided in Clustergrammer JS is changing the color of the positive and the negative end.
This Feature is especially needed for P-Value heat maps where a lower value denotes higher significance, hence a darker color corresponding to the 0 is preferred.
Thanks for the suggestion @cornhundred . It helped me indeed.
This issue is not pertaining to this repository. Hence I'm closing this issue here and would reopen it in the clustergrammer JS repository belonging to the MaayanLab.
Apologies.
| gharchive/issue | 2020-10-14T09:21:20 | 2025-04-01T06:39:06.617225 | {
"authors": [
"mayankmusaddi"
],
"repo": "ismms-himc/clustergrammer2",
"url": "https://github.com/ismms-himc/clustergrammer2/issues/83",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2224303223 | 🛑 naturacert.isolucion.co is down
In d0a9903, naturacert.isolucion.co (https://naturacert.isolucion.co) was down:
HTTP code: 0
Response time: 0 ms
Resolved: naturacert.isolucion.co is back up in 54539a7 after 11 minutes.
| gharchive/issue | 2024-04-04T02:20:15 | 2025-04-01T06:39:06.621349 | {
"authors": [
"isolucionco"
],
"repo": "isolucionco/EstadoIsolucionHosting",
"url": "https://github.com/isolucionco/EstadoIsolucionHosting/issues/2600",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2317218484 | 🛑 Cartama.isolucion.co is down
In 078d10d, Cartama.isolucion.co (https://Cartama.isolucion.co) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Cartama.isolucion.co is back up in e2ed26c after 1 hour, 16 minutes.
| gharchive/issue | 2024-05-25T20:25:28 | 2025-04-01T06:39:06.624329 | {
"authors": [
"isolucionco"
],
"repo": "isolucionco/EstadoIsolucionHosting",
"url": "https://github.com/isolucionco/EstadoIsolucionHosting/issues/2920",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1284404897 | 🛑 ApiIsoDtaConectorBancoOccidente.isolucion.co is down
In 1c20c2a, ApiIsoDtaConectorBancoOccidente.isolucion.co (https://ApiIsoDtaConectorBancoOccidente.isolucion.co) was down:
HTTP code: 0
Response time: 0 ms
ok
| gharchive/issue | 2022-06-25T01:52:00 | 2025-04-01T06:39:06.626773 | {
"authors": [
"isolucionco"
],
"repo": "isolucionco/EstadoIsolucionHosting",
"url": "https://github.com/isolucionco/EstadoIsolucionHosting/issues/314",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
225599922 | Right column index overlaps main body content.
The right column index on many pages overlaps the main body content. This is particular bad if the web browser isn't maximum on a large screen. The example below is half-screen width on 15" MBP (other half is terminal to run exercises) with a reasonably small font.
https://istio.io/docs/reference/contribute/style-guide.html.
Dup of #77.
Dave's got a fix for this coming up soon.
| gharchive/issue | 2017-05-02T06:16:51 | 2025-04-01T06:39:06.638110 | {
"authors": [
"ayj",
"geeknoid"
],
"repo": "istio/istio.github.io",
"url": "https://github.com/istio/istio.github.io/issues/90",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
413369810 | Auto envoy injection to nginx-ingress-controller not working.
Describe the bug
As with issue #4840, I am unable to get istio to auto-inject the envoy proxy as a sidecar to my nginx-ingress-controller. It does however inject the default-backend.
When I look in the logs for the sidecar-injector, I see:
2019-02-22T10:55:28.768549Z info AdmissionReview for Kind=/v1, Kind=Pod Namespace=ingress Name= (nginx-ingress-controller-544678595d-***** (actual name not yet known)) UID=5dc1655d-3690-11e9-bdf3-02c8c717b494 Rfc6902PatchOperation=CREATE UserInfo={system:serviceaccount:kube-system:replicaset-controller c486e3e6-35ec-11e9-a1d3-02c8c717b494 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]}
2019-02-22T10:55:28.768573Z info Skipping ingress/nginx-ingress-controller-544678595d-***** (actual name not yet known) due to policy check
for the default-backend I get:
2019-02-22T10:55:28.759514Z info AdmissionReview for Kind=/v1, Kind=Pod Namespace=ingress Name= (nginx-ingress-default-backend-56d99b86fb-***** (actual name not yet known)) UID=5dc0d3bb-3690-11e9-bdf3-02c8c717b494 Rfc6902PatchOperation=CREATE UserInfo={system:serviceaccount:kube-system:replicaset-controller c486e3e6-35ec-11e9-a1d3-02c8c717b494 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]}
2019-02-22T10:55:28.761243Z info AdmissionResponse: patch=[{"op":"add","path":"/spec/initContainers","value":[{"name":"istio-init","image":"docker.io/istio/proxy_init:1.1.0-rc.0","args":["-p","15001","-u","1337","-m","REDIRECT","-i","*","-x","","-b","8080","-d","15020"],"resources":{"limits":{"cpu":"100m","memory":"50Mi"},"requests":{"cpu":"10m","memory":"10Mi"}},"imagePullPolicy":"IfNotPresent","securityContext":{"capabilities":{"add":["NET_ADMIN"]}}}]},{"op":"add","path":"/spec/containers/-","value":{"name":"istio-proxy","image":"docker.io/istio/proxyv2:1.1.0-rc.0","args":["proxy","sidecar","--domain","$(POD_NAMESPACE).svc.cluster.local","--configPath","/etc/istio/proxy","--binaryPath","/usr/local/bin/envoy","--serviceCluster","nginx-ingress.$(POD_NAMESPACE)","--drainDuration","45s","--parentShutdownDuration","1m0s","--discoveryAddress","istio-pilot.istio-system:15010","--zipkinAddress","zipkin.istio-system:9411","--connectTimeout","10s","--proxyAdminPort","15000","--controlPlaneAuthPolicy","NONE","--statusPort","15020","--applicationPorts","8080","--concurrency","2"],"ports":[{"name":"http-envoy-prom","containerPort":15090,"protocol":"TCP"}],"env":[{"name":"POD_NAME","valueFrom":{"fieldRef":{"fieldPath":"metadata.name"}}},{"name":"POD_NAMESPACE","valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}},{"name":"INSTANCE_IP","valueFrom":{"fieldRef":{"fieldPath":"status.podIP"}}},{"name":"ISTIO_META_POD_NAME","valueFrom":{"fieldRef":{"fieldPath":"metadata.name"}}},{"name":"ISTIO_META_CONFIG_NAMESPACE","valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}},{"name":"ISTIO_META_INTERCEPTION_MODE","value":"REDIRECT"},{"name":"ISTIO_METAJSON_LABELS","value":"{\"app\":\"nginx-ingress\",\"component\":\"default-backend\",\"pod-template-hash\":\"56d99b86fb\",\"release\":\"nginx-ingress\"}\n"},{"name":"ISTIO_KUBE_APP_PROBERS","value":"{\"/app-health/nginx-ingress-default-backend/livez\":{\"path\":\"/healthz\",\"port\":8080,\"scheme\":\"HTTP\"}}"}],"resources":{"limits":{"cpu":"2","memory":"128Mi"},"requests":{"cpu":"100m","memory":"128Mi"}},"volumeMounts":[{"name":"istio-envoy","mountPath":"/etc/istio/proxy"},{"name":"istio-certs","readOnly":true,"mountPath":"/etc/certs/"},{"name":"default-token-rcs8d","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"readinessProbe":{"httpGet":{"path":"/healthz/ready","port":15020},"initialDelaySeconds":1,"periodSeconds":2,"failureThreshold":30},"imagePullPolicy":"IfNotPresent","securityContext":{"runAsUser":1337,"readOnlyRootFilesystem":true}}},{"op":"add","path":"/spec/volumes/-","value":{"name":"istio-envoy","emptyDir":{"medium":"Memory"}}},{"op":"add","path":"/spec/volumes/-","value":{"name":"istio-certs","secret":{"secretName":"istio.default","optional":true}}},{"op":"add","path":"/spec/securityContext","value":{}},{"op":"add","path":"/metadata/annotations","value":{"sidecar.istio.io/status":"{\"version\":\"08f55455e862c5191b88676351220e39413df4d226b5ac61aa20f18990316ebf\",\"initContainers\":[\"istio-init\"],\"containers\":[\"istio-proxy\"],\"volumes\":[\"istio-envoy\",\"istio-certs\"],\"imagePullSecrets\":null}"}},{"op":"replace","path":"/spec/containers/0/livenessProbe/httpGet","value":{"path":"/app-health/nginx-ingress-default-backend/livez","port":15020,"scheme":"HTTP"}}]
There is obviously some policy at play here that I don't know about. I just haven't been able to find it.
I've added
Expected behavior
I'd expect that after installing istio, and then the nginx-ingress-controller, that all the nginx-ingress-controller pods had the envoy proxy sidecar injected.
Steps to reproduce the bug
deploy cluster
install istio
install nginx-ingress-controller
Version
$ istioctl version
version.BuildInfo{Version:"1.1.0-rc.0", GitRevision:"3632361b439ae27962f0af472064d452fc63273b", User:"root", Host:"9efe8d69-34c2-11e9-b805-0a580a2c0506", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.0-snapshot.6-26-g3632361"}
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-13T23:15:13Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:00:57Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
$ helm version
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Installation
kubectl create ns istio-system
kubectl -n istio-system create secret generic kiali \
--from-literal=username=admin \
--from-literal=passphrase=supersecretpassword
helm upgrade --install --namespace istio-system \
--wait \
-f istio-1.1.0-rc.0/install/kubernetes/helm/istio-init/values.yaml \
istio-init istio-1.1.0-rc.0/install/kubernetes/helm/istio-init
helm upgrade --install --namespace istio-system \
--wait \
-f istio-1.1.0-rc.0/install/kubernetes/helm/istio/values.yaml \
istio istio-1.1.0-rc.0/install/kubernetes/helm/istio
values file for istio is:
gateways:
enabled: true
istio-ingressgateway:
type: ClusterIP
ports:
## You can add custom gateway ports
- port: 80
targetPort: 80
name: http2
# nodePort: 31380
- port: 443
name: https
# nodePort: 31390
# Example of a port to add. Remove if not needed
- port: 31400
name: tcp
# nodePort: 31400
### PORTS FOR UI/metrics #####
## Disable if not needed
- port: 15029
targetPort: 15029
name: https-kiali
- port: 15030
targetPort: 15030
name: https-prometheus
- port: 15031
targetPort: 15031
name: https-grafana
- port: 15032
targetPort: 15032
name: https-tracing
# This is the port where sni routing happens
- port: 15443
targetPort: 15443
name: tls
sidecarInjectorWebhook:
enabled: true
rewriteAppHTTPProbe: true
tracing:
enabled: true
Worth noting that I was having the same trouble with 1.0.5 before trying the 1.1.0 rc
Environment
AWS, CoreOS, Typhoon cluster
Cluster state
hand crafted istio dump attached. does not include the k8s_resources.yaml manifest. not entirely comfortable uploading that.
istio-dump.tar.gz
OK. So I tried injecting into the deployment manually, and got this:
$ kubectl -n ingress get deployment nginx-ingress-controller -o yaml | istioctl kube-inject -f - | kubectl apply -f -
Skipping injection because "" has host networking enabled
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
deployment.extensions/nginx-ingress-controller configured
A little digging later, and it turns out you can't do injection on host-network installs of nginx. Is there some way to work around that? We set up an NLB to port forward ports 80/443, and a few others, to the cluster on those ports. Changing to ClusterIP or Loadbalancer screws with the security groups. In the case of nginx, where it's being used as the inbound traffic controller, surely rewriting the ip-tables isn't required (because it's edge)?
Either way. How am I supposed to setup nginx so that it plays nicely with the NLB and Istio?
@ostromart is this something that you can help with?
It's also worth noting that CertManager is in the mix.
I've never attempted install with nginx - @costinm or @rshriram may be able to help.
I've made some progress. I've set the ingress-gateway to just pass thru ports 80 and ports443, like so:
kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: nginx-http-gateway
spec:
selector:
istio: ingressgateway # use Istio default gateway implementation
servers:
- port:
number: 80
name: http
protocol: HTTP
hosts:
- "*"
EOF
kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: nginx-https-gateway
spec:
selector:
istio: ingressgateway # use Istio default gateway implementation
servers:
- port:
number: 443
name: https
protocol: TCP
hosts:
- "*"
EOF
This works to the extent that istio routes traffic to nginx, so 👍 . The problem I have now, is that the one service I have running; concourse; is only secured on the tcp ssh port 2222. It isn't securing or even registering that it has port 8080 and ports 9391. So whenever I go to access port 8080 from an istio-proxy container, it works; unexpectedly. I was hoping that would fail, meaning that mtls was required.
istioctl authn tls-check concourse-web.dev-tools.svc.cluster.local
Warning! error execing into istio-pilot-7d954dccdd-vpdpw/istio-system discovery container: gc 1 @0.009s 6%: 0.007+0.68+0.65 ms clock, 0.057+0.064/0.92/0.84+5.2 ms cpu, 4->4->1 MB, 5 MB goal, 8 P
gc 2 @0.016s 9%: 0.006+0.65+0.75 ms clock, 0.051+0.22/0.80/1.4+6.0 ms cpu, 4->4->2 MB, 5 MB goal, 8 P
HOST:PORT STATUS SERVER CLIENT AUTHN POLICY DESTINATION RULE
concourse-web.dev-tools.svc.cluster.local:2222 OK mTLS mTLS default/dev-tools default/dev-tools
I've clearly not configured something correctly. Any ideas?
strangely, if I do:
istioctl authn tls-check
Warning! error execing into istio-pilot-7d954dccdd-vpdpw/istio-system discovery container: gc 1 @0.009s 5%: 0.007+0.59+0.48 ms clock, 0.056+0/0.66/1.1+3.8 ms cpu, 4->4->1 MB, 5 MB goal, 8 P
gc 2 @0.016s 8%: 0.006+0.71+0.77 ms clock, 0.051+0.26/0.91/1.1+6.2 ms cpu, 4->4->2 MB, 5 MB goal, 8 P
HOST:PORT STATUS SERVER CLIENT AUTHN POLICY DESTINATION RULE
<snip>
concourse-tsa.dev-tools.svc.cluster.local:2222 OK mTLS mTLS default/dev-tools default/dev-tools
concourse-web.dev-tools.svc.cluster.local:2222 OK mTLS mTLS default/dev-tools default/dev-tools
concourse-web.dev-tools.svc.cluster.local:8080 OK mTLS mTLS default/dev-tools default/dev-tools
concourse-web.dev-tools.svc.cluster.local:9391 OK mTLS mTLS default/dev-tools default/dev-tools
</snip>
I get all the ports.
Additionally, I have the following:
<snip>
istio-citadel.istio-system.svc.cluster.local:8060 OK mTLS mTLS default/ default/dev-tools
istio-citadel.istio-system.svc.cluster.local:15014 OK mTLS mTLS default/ default/dev-tools
istio-egressgateway.istio-system.svc.cluster.local:80 OK mTLS mTLS default/ default/dev-tools
istio-egressgateway.istio-system.svc.cluster.local:443 OK mTLS mTLS default/ default/dev-tools
istio-egressgateway.istio-system.svc.cluster.local:15443 OK mTLS mTLS default/ default/dev-tools
istio-galley.istio-system.svc.cluster.local:443 OK mTLS mTLS default/ default/dev-tools
istio-galley.istio-system.svc.cluster.local:9901 OK mTLS mTLS default/ default/dev-tools
istio-galley.istio-system.svc.cluster.local:15014 OK mTLS mTLS default/ default/dev-tools
istio-ingressgateway.istio-system.svc.cluster.local:80 OK mTLS mTLS default/ default/dev-tools
istio-ingressgateway.istio-system.svc.cluster.local:443 OK mTLS mTLS default/ default/dev-tools
istio-ingressgateway.istio-system.svc.cluster.local:2222 OK mTLS mTLS default/ default/dev-tools
istio-pilot.istio-system.svc.cluster.local:8080 OK mTLS mTLS default/ default/dev-tools
istio-pilot.istio-system.svc.cluster.local:15010 OK mTLS mTLS default/ default/dev-tools
istio-pilot.istio-system.svc.cluster.local:15011 OK mTLS mTLS default/ default/dev-tools
istio-pilot.istio-system.svc.cluster.local:15014 OK mTLS mTLS default/ default/dev-tools
istio-policy.istio-system.svc.cluster.local:9091 CONFLICT mTLS HTTP default/ istio-policy/istio-system
istio-policy.istio-system.svc.cluster.local:15004 CONFLICT mTLS HTTP default/ istio-policy/istio-system
istio-policy.istio-system.svc.cluster.local:15014 CONFLICT mTLS HTTP default/ istio-policy/istio-system
istio-sidecar-injector.istio-system.svc.cluster.local:443 OK mTLS mTLS default/ default/dev-tools
istio-telemetry.istio-system.svc.cluster.local:9091 CONFLICT mTLS HTTP default/ istio-telemetry/istio-system
istio-telemetry.istio-system.svc.cluster.local:15004 CONFLICT mTLS HTTP default/ istio-telemetry/istio-system
istio-telemetry.istio-system.svc.cluster.local:15014 CONFLICT mTLS HTTP default/ istio-telemetry/istio-system
istio-telemetry.istio-system.svc.cluster.local:42422 CONFLICT mTLS HTTP default/ istio-telemetry/istio-system
istiocoredns.istio-system.svc.cluster.local:53 OK mTLS mTLS default/ default/dev-tools
istiocoredns.istio-system.svc.cluster.local:53 OK mTLS mTLS default/ default/dev-tools
jaeger-agent.istio-system.svc.cluster.local:5775 OK mTLS mTLS default/ default/dev-tools
jaeger-agent.istio-system.svc.cluster.local:6831 OK mTLS mTLS default/ default/dev-tools
jaeger-agent.istio-system.svc.cluster.local:6832 OK mTLS mTLS default/ default/dev-tools
jaeger-collector.istio-system.svc.cluster.local:14267 OK mTLS mTLS default/ default/dev-tools
jaeger-collector.istio-system.svc.cluster.local:14268 OK mTLS mTLS default/ default/dev-tools
jaeger-query.istio-system.svc.cluster.local:16686 OK mTLS mTLS default/ default/dev-tools
kiali.istio-system.svc.cluster.local:20001 OK mTLS mTLS default/ default/dev-tools
kiam-agent.iam.svc.cluster.local:9620 OK mTLS mTLS default/ default/dev-tools
</snip>
Are those conflicts a misconfiguration? They are that way after I turn on a system-wide mesh policy.
Solved!. Set the gateway correctly (the docs have it... https://preliminary.istio.io/docs/examples/advanced-gateways/ingress-sni-passthrough/) .
I've solved the ingress problem now.
@pms1969 Hi, can you please describe in more details how did you solve the problem?
@Demonian I basically followed the setup here: https://istio.io/docs/examples/advanced-gateways/ingress-sni-passthrough/
Set a gateway passthrough for ports 80 and 443.
# needed for ingress into a hostport daemonset for nginx.
kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: nginx-http-gateway
spec:
selector:
istio: ingressgateway # use Istio default gateway implementation
servers:
- port:
number: 80
name: http
protocol: HTTP
hosts:
- "*"
EOF
# needed for ingress into a hostport daemonset for nginx.
kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: nginx-https-gateway
spec:
selector:
istio: ingressgateway # use Istio default gateway implementation
servers:
- port:
number: 443
name: https
protocol: HTTPS
tls:
mode: PASSTHROUGH
hosts:
- "*"
EOF
| gharchive/issue | 2019-02-22T11:49:18 | 2025-04-01T06:39:06.704006 | {
"authors": [
"Demonian",
"ostromart",
"ozevren",
"pms1969"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/11973",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
558232237 | Pilot configures proxy with wrong routes/listeners
Bug description
Pilot adds incorrect listeners/routes to envoy proxies, resulting in 503's. This is the output of proxy-config routes on 2 identical pods created from the same deployment:
This is the proxy that received the correct config:
$ istioctl pc routes pod1.our-namespace
NOTE: This output only contains routes loaded via RDS.
NAME VIRTUAL HOSTS
8080 4
9091 2
istio-telemetry.istio-system.svc.cluster.local:42422 1
15004 2
15014 2
inbound|8080|http|correct-service.our-namespace.svc.cluster.local 1
inbound|8080|http|correct-service.our-namespace.svc.cluster.local 1
inbound|8080|http|correct-service.our-namespace.svc.cluster.local 1
inbound|8080|http|correct-service.our-namespace.svc.cluster.local 1
Here is the output from an incorrectly configured proxy on the other pod from the same deployment as above:
$ istioctl pc routes pod2.our-namespace
NOTE: This output only contains routes loaded via RDS.
NAME VIRTUAL HOSTS
8080 4
istio-telemetry.istio-system.svc.cluster.local:42422 1
9091 2
15004 2
15014 2
inbound|8800|http|service-from-another-namespace.wrong-namespace.svc.cluster.local 1
inbound|8800|http|service-from-another-namespace.wrong-namespace.svc.cluster.local 1
inbound|8800|http|service-from-another-namespace.wrong-namespace.svc.cluster.local 1
inbound|8800|http|service-from-another-namespace.wrong-namespace.svc.cluster.local 1
Also notice the port number is not right either. Restarting the second pod will result in a proxy with the same config as the first, which is correct.
Expected behavior
Pilot configures proxy with correct routes/listeners for the service.
Steps to reproduce the bug
It seems to only happen on a deployment when new pods are created and not every time. Restarting the pods seems to yield correct listeners every time.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl version --remote
client version: 1.4.3
citadel version: 1.4.3
galley version: 1.4.3
galley version: 1.4.3
istio-ig-custom version:
istio-ig-custom version:
istio-ig-custom2 version:
istio-ig-custom2 version:
istio-ig-custom3 version:
istio-ig-custom3 version:
pilot version: 1.4.3
pilot version: 1.4.3
sidecar-injector version: 1.4.3
sidecar-injector version: 1.4.3
telemetry version: 1.4.3
telemetry version: 1.4.3
data plane version: 1.4.0 (1 proxies), 1.4.3 (229 proxies)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-14T04:24:34Z", GoVersion:"go1.12.13", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
Helm 2 with Tiller
Environment where bug was observed (cloud vendor, OS, etc)
On premise, centos
We are seeing the same or simular issue randomly in our pod after upgrading from Istio 1.3.3 to 1.4.3
Steps to reproduce the bug
It seems to only happen on a deployment when new pods are created and not every time. Restarting the pods seems to yield correct listeners every time.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl version --remote
client version: 1.4.3
citadel version: 1.4.3
egressgateway version: 1.4.3
egressgateway version: 1.4.3
egressgateway version: 1.4.3
egressgateway version: 1.4.3
egressgateway version: 1.4.3
galley version: 1.4.3
ilbgateway version: 1.4.3
ilbgateway version: 1.4.3
ingressgateway version: 1.4.3
ingressgateway version: 1.4.3
ingressgateway version: 1.4.3
ingressgateway version: 1.4.3
ingressgateway version: 1.4.3
nodeagent version:
[... nodeagent version ...]
nodeagent version:
pilot version: 1.4.3
pilot version: 1.4.3
policy version: 1.4.3
sidecar-injector version: 1.4.3
telemetry version: 1.4.3
telemetry version: 1.4.3
data plane version: 1.4.3 (838 proxies)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:30:10Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.7-gke.23", GitCommit:"81c87c699557fed991e292cd328b2129c2f242a2", GitTreeState:"clean", BuildDate:"2019-11-07T19:23:23Z", GoVersion:"go1.12.11b4", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
Helm 2 with Tiller
Environment where bug was observed (cloud vendor, OS, etc)
Google Cloud
GKE
$ gcloud container clusters list
NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS
a-cluster europe-west1 1.14.7-gke.23 x.x.x.x.x n1-standard-4 1.14.7-gke.23 108 RUNNING
Additional information about this issue:
These are the routes in a normal pod (edited the names, I can provide the output wihtout edits via a private channel):
$ istioctl pc routes a-deployment-794f446794-zzwvm.correct-namespace
NOTE: This output only contains routes loaded via RDS.
NAME VIRTUAL HOSTS
80 33
96 2
5556 2
8060 2
8080 10
8081 3
9090 3
9091 30
9901 2
10901 2
15004 3
15010 2
15014 7
15030 2
15031 2
jaeger-istio-collector.istio-system.svc.cluster.local:9411 1
jaeger-istio-collector.istio-system.svc.cluster.local:14267 1
inbound|9091|http-prom-a-deployment-correct-namespace|a-deployment.correct-namespace.svc.cluster.local 1
jaeger-istio-collector.istio-system.svc.cluster.local:14268 1
istio-telemetry.istio-system.svc.cluster.local:42422 1
inbound|9091|http-prom-a-deployment-correct-namespace|a-deployment.correct-namespace.svc.cluster.local 1
inbound|80|http-a-deployment-correct-namespace|a-deployment.correct-namespace.svc.cluster.local 1
inbound|80|http-a-deployment-correct-namespace|a-deployment.correct-namespace.svc.cluster.local 1
20001 2
1
This are the routes from a faulty pod
istioctl pc routes a-deployment-794f446794-clvbg.correct-namespace
NOTE: This output only contains routes loaded via RDS.
NAME VIRTUAL HOSTS
80 33
96 2
5556 2
8060 2
istio-telemetry.istio-system.svc.cluster.local:42422 1
jaeger-istio-collector.istio-system.svc.cluster.local:14268 1
inbound|80|http-other-deployment-wrong-namespace|other-deployment.wrong-namespace.svc.cluster.local 1
jaeger-istio-collector.istio-system.svc.cluster.local:9411 1
jaeger-istio-collector.istio-system.svc.cluster.local:14267 1
inbound|80|http-other-deployment-wrong-namespace|other-deployment.wrong-namespace.svc.cluster.local 1
8080 10
8081 3
9090 3
9091 30
9901 2
10901 2
15004 3
15010 2
15014 7
15030 2
15031 2
20001 2
1
When executing an http request to a POD with the correct configuration we can see the headerx-envoy-decorator-operation set to the correct POD name:
curl -I http://a-deployment-794f446794-zzwvm.correct-namespace:8080
< server: istio-envoy
< x-envoy-decorator-operation: a-deployment.correct-namespace:80/*
If we execute the same request to a POD with a wrong configuration we see:
curl -I http://a-deployment-794f446794-clvbg.correct-namespace:8080
< server: istio-envoy
< x-envoy-decorator-operation: other-deployment.wrong-namespace:80/*
where you can notice the x-envoy-decorator-operation header indicates other-deployment.wrong-namespace:80 but we expected to see a-deployment-794f446794-clvbg.correct-namespace:80
Additionally, we have detected that the content response is correct, it is provided by a-deployment-794f446794-clvbg.correct-namespace but Policies are wrong (in our case, JWT Policy).
Kubernetes and Istio resources for a-deployment in correct-namespace:
VirtualService:
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
creationTimestamp: "2019-08-07T06:15:32Z"
generation: 3
labels:
app: a-deployment
chart: base-v1.2.17
fullapp: correct-namespace
heritage: Tiller
release: a-deployment-correct-namespace
version: v1.2.17
name: a-deployment
namespace: correct-namespace
resourceVersion: "281486396"
selfLink: /apis/networking.istio.io/v1alpha3/namespaces/correct-namespace/virtualservices/a-deployment
uid: c3360aef-b8da-11e9-b4e4-42010ac50709
spec:
gateways:
- default/ingressgateway
hosts:
- correct-namespace.dev-01.my.domain.com
- other.dev.my.domain.com
http:
- corsPolicy:
allowCredentials: false
allowHeaders:
- origin
- x-requested-with
- accept
- content-type
- x-application-id
- x-correlation-id
- x-request-id
- authorization
- x-authorization
- X-Customer-ID
- X-SFID
- X-MSISDN
- x-front-client
- scoring-token
- x-target
- cache-control
allowOrigin:
- '*'
maxAge: 600s
match:
- uri:
prefix: /v1/a-deployment/
rewrite:
uri: /
route:
- destination:
host: a-deployment.correct-namespace.svc.cluster.local
port:
number: 80
Service:
piVersion: v1
kind: Service
metadata:
annotations:
prometheus.io/path: /metrics
prometheus.io/port: "9091"
prometheus.io/probe: "true"
creationTimestamp: "2019-08-07T06:15:32Z"
labels:
app: a-deployment
chart: base-v1.2.17
fullapp: correct-namespace
heritage: Tiller
release: a-deployment-correct-namespace
version: v1.2.17
name: a-deployment
namespace: correct-namespace
resourceVersion: "435659168"
selfLink: /api/v1/namespaces/correct-namespace/services/a-deployment
uid: c3314118-b8da-11e9-b4e4-42010ac50709
spec:
clusterIP: 10.197.12.204
ports:
- name: http-a-deployment-correct-namespace
port: 80
protocol: TCP
targetPort: 8080
- name: http-prom-a-deployment-correct-namespace
port: 9091
protocol: TCP
targetPort: 9091
selector:
app: a-deployment
release: a-deployment-correct-namespace
sessionAffinity: None
type: ClusterIP
Policy
apiVersion: authentication.istio.io/v1alpha1
kind: Policy
metadata:
creationTimestamp: "2019-10-21T14:11:59Z"
generation: 1
labels:
app: a-deployment
chart: base-v1.2.17
fullapp: correct-namespace
heritage: Tiller
release: a-deployment-correct-namespace
tier: backend
version: v1.2.17
name: a-deployment-authn
namespace: correct-namespace
resourceVersion: "281486392"
selfLink: /apis/authentication.istio.io/v1alpha1/namespaces/correct-namespace/policies/a-deployment-authn
uid: bf1eaa37-f40c-11e9-8d86-42010ac50709
spec:
origins:
- jwt:
issuer: issuer1
jwksUri: https://auth-provider-jwks.example.com/.well-known/jwks.json
trigger_rules:
- excluded_paths:
- exact: /health
- prefix: /docs
- exact: /health
- exact: /metrics
included_paths:
- prefix: /
- jwt:
issuer: issuer2
jwksUri: https://auth-provider-jwks.example.com/.well-known/jwks.json
trigger_rules:
- excluded_paths:
- exact: /health
- prefix: /docs
- exact: /health
- exact: /metrics
included_paths:
- prefix: /
principalBinding: USE_ORIGIN
targets:
- name: a-deployment
Kubernetes and Istio resources for other-deployment in wrong-namespace:
VirtualService
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
creationTimestamp: "2019-08-14T10:09:51Z"
generation: 3
labels:
app: other-deployment
chart: base-v1.2.17
fullapp: wrong-namespace
heritage: Tiller
release: other-deployment-wrong-namespace
version: v1.2.17
name: other-deployment
namespace: wrong-namespace
resourceVersion: "294862447"
selfLink: /apis/networking.istio.io/v1alpha3/namespaces/wrong-namespace/virtualservices/other-deployment
uid: a7b23296-be7b-11e9-bf65-42010ac5070b
spec:
gateways:
- default/ingressgateway
hosts:
- wrong-namespace.dev.my.domain.com
- other-url.dev.my.domain.com
http:
- corsPolicy:
allowCredentials: false
allowHeaders:
- origin
- x-requested-with
- accept
- content-type
- x-requestId
- x-requestSessionId
- authorization
- cache-control
allowOrigin:
- '*'
maxAge: 600s
match:
- uri:
prefix: /other-deployment/
rewrite:
uri: /
route:
- destination:
host: other-deployment.wrong-namespace.svc.cluster.local
port:
number: 80
Service
apiVersion: v1
kind: Service
metadata:
annotations:
creationTimestamp: "2019-08-14T10:09:51Z"
labels:
app: other-deployment
chart: base-v1.2.17
fullapp: wrong-namespace
heritage: Tiller
release: other-deployment-wrong-namespace
version: v1.2.17
name: other-deployment
namespace: wrong-namespace
resourceVersion: "435658730"
selfLink: /api/v1/namespaces/wrong-namespace/services/other-deployment
uid: a7afea06-be7b-11e9-bf65-42010ac5070b
spec:
clusterIP: 10.197.10.227
ports:
- name: http-other-deployment-wrong-namespace
port: 80
protocol: TCP
targetPort: 8080
selector:
app: other-deployment
release: other-deployment-wrong-namespace
sessionAffinity: None
type: ClusterIP
Policy
apiVersion: authentication.istio.io/v1alpha1
kind: Policy
metadata:
creationTimestamp: "2019-09-11T10:26:43Z"
generation: 1
labels:
app: other-deployment
chart: base-v1.2.17
fullapp: wrong-namespace
heritage: Tiller
release: other-deployment-wrong-namespace
tier: backend
version: v1.2.17
name: other-deployment-authn
namespace: wrong-namespace
resourceVersion: "294862440"
selfLink: /apis/authentication.istio.io/v1alpha1/namespaces/wrong-namespace/policies/other-deployment-authn
uid: a64ba2ce-d47e-11e9-bf65-42010ac5070b
spec:
origins:
- jwt:
issuer: issuer3
jwksUri: https://auth-provider-jwks.example.com/.well-known/jwks.json
trigger_rules:
- excluded_paths:
- exact: /monitoring/health
- prefix: /doc/
principalBinding: USE_ORIGIN
targets:
- name: other-deployment
As for the config dump file, it is attached.
istio-config-dump-edited.json.gz
I hope this information is useful.
Thanks!
This may just be some recency bias, but this feels a lot like https://github.com/istio/istio/issues/20676. tl;dr is a pod IP gets re-used, causing pilot to generate config for the old pod instead of the new pod. So presumably, if this was the case, there was a pod with some ip 1.2.3.4 in service-from-another-namespace.wrong-namespace, then later your new pod in service correct-service.our-namespace comes up with pod ip 1.2.3.4 and gets the wrong config. I think this can only happen with pre-emptible nodes though, are you using those?
The tell-tale sign of this is if you see this pattern in the logs:
Handling event update for pod pod1-sha123 in namespace foo -> 1.2.3.4
Handling event update for pod pod1-sha123 in namespace foo -> 1.2.3.5 # same pod name, new IP
Handling event update for pod new-pod-sha345 in namespace foo -> 1.2.3.4 # re-use the old pod
@howardjohn In our case the nodes are long-living, they are on-prem and have been running for nearly a year.
Hi @howardjohn , we are indeed using preemtible nodes (and not preemtible).
I've search for "Handling event update for pod" in Stackdriver logs (whole cluster) and I couldn't find a single match. (Also tested substrings)
@pmoncadaisla if you are using pre-emptible nodes it seems likely the root cause. Thats weird it doesn't match, that log happens any time a pod is changed at all, do you not have info level logging enabled?
@howardjohn I can see this in the istio-proxy container of any POD: --proxyLogLevel="warning" and --log_output_level="default:info"
Pre-emptible notes seems to me the root cause, but, why is this happening after the upgrade from 1.3.3 to 1.4.3 and not before? We've seem this exact behaviour in 2 different Kubernetes clusters, upgraded from and to the same Istio version.
My understand was that this code path is entirely unchanged, so I am surprised it change during upgrade - very possible its a different root cause. The logs I am referring to are on pilot not the proxy.
You are right @howardjohn , I was looking for logs in a cluster were logs from pilot are excluded from ingestion at Stackdriver.
I've checked for the same one I reported before, and I can see what you described:
2020-02-05T12:10:59.408811Z info Handling event update for pod other-deployment-6d94d5f9db-8mt4d in namespace wrong-namespace -> 10.196.0.20
2020-02-05T12:12:50.781199Z info Handling event update for pod other-deploymenti-6d94d5f9db-8mt4d in namespace wrong-namespace -> 10.196.0.9
2020-02-05T15:24:21.009595Z info Handling event update for pod a-deployment-794f446794-clvbg in namespace correct-namespace -> 10.196.0.20
In this case IP address 10.196.0.20 is being reused as you described.
I guess our options if we are affected by this issue are:
Shutdown preemtible nodes
Wait for 1.5 and expect #20676 to be included
@pmoncadaisla this will be backported to 1.4 as well. If you want, you can run the dev builds that include this commit: https://github.com/istio/istio/wiki/Dev Builds. You can see all commits at https://github.com/istio/istio/commits/release-1.4. Note that we don't validate these much, so it would be at your own risk
Hi @howardjohn , we have removed our preemptible nodes until the fix is included in a release.
We will be monitoring and we will keep you informed if we see the same behaviour after removing preemptible nodes.
If we don't have problems, then our issue is not related to @jasonwoodman-ascend 's
Its possible @jasonwoodman-ascend is the same issue without pre-emptible nodes. The symptom here is a running pod has its IP address changed. I've only seen it on node restarts, but perhaps it could happen in other cases?
@howardjohn @pmoncadaisla I think my issue can be explained by the same root cause. In our case, though the nodes are long living, we do restart them for patching. I am guessing our issue started in our last patching cycle, the timing seems about right.
At this point I am waiting for the fix to be released and will re-evaluate then as I think it will most likely fix it.
I think, we have same or very similar issue, so that's why I'm not filing a new bug. In our case as well istio pickups listeners from completely different namespace (kube-system) instead of namespace where service is deployed. However, it's intermittent issue, we have to run delete-create loop for deployment/service to reproduce it. The only thing that helped as is to manually define Sidecar object and repeat all the ports defined in Service object.
This should be fixed in 1.4+ now. If you still see this issue on these versions, please reopen/open another issue. Thanks!
| gharchive/issue | 2020-01-31T16:25:57 | 2025-04-01T06:39:06.732010 | {
"authors": [
"howardjohn",
"infa-rbliznet",
"jasonwoodman-ascend",
"pmoncadaisla"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/20733",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
611775848 | Istio CNI plugin install with SELinux enabled not documented
Describe the feature request
Istio CNI plugin install and repair when SELinux is enabled and docker daemon is running with --selinux-enabled flag aren't documented.
install-cni container fails when it runs with SELinux enabled but SELinux requirements aren't documented to get Istio CNI plugin running without issues.
Describe alternatives you've considered
Add to Istio CNI plugin install documentation SELinux requirements to get Istio CNI plugin running without issues.
Additional context
Closing as a duplicate of https://github.com/istio/istio/issues/23605. Still valid though. Thanks!
| gharchive/issue | 2020-05-04T10:44:19 | 2025-04-01T06:39:06.736335 | {
"authors": [
"howardjohn",
"jsalgado78"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/23493",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
814187220 | when VirtualService Status Error，istiod can not start
istio version: 1.18.3
kubernetes:1.18.10
Bug description
when VirtualService config error, istiod can not started
istiod error log:
{"level":"error","time":"2021-02-23T06:40:18.954868Z","scope":"klog","msg":"k8s.io/client-go@v0.19.3/tools/cache/reflector.go:156: Failed to watch *v1alpha3.VirtualService: failed to list *v1alpha3.VirtualService: v1alpha3.VirtualServiceList.Items: []v1alpha3.VirtualService: v1alpha3.VirtualService.v1alpha3.VirtualService.Status: unmarshalerDecoder: unknown value \"Error\" for enum istio.analysis.v1alpha1.AnalysisMessageBase_Level, error found in #10 byte of ...|l+v1\\\"\"}]}},{\"apiVer|..., bigger context ...|\"map-nginx.project-1925.svc.cluster.local+v1\\\"\"}]}},{\"apiVersion\":\"networking.istio.io/v1alpha3\",\"ki|...[]"}
error VirtualService config
spec:
exportTo:
- .
gateways:
- gateway-122-71
hosts:
- nginx-map.gw-wso2t-sy-in.earth.xcloud.lenovo.com
http:
- match:
- uri:
prefix: /
rewrite:
uri: /
route:
- destination:
host: map-nginx.project-1925.svc.cluster.local
port:
number: 80
subset: v1
weight: 100
status:
validationMessages:
- code: IST0101
documentation_url: https://istio.io/docs/reference/config/analysis/ist0101/?ref=status-controller
level: Error
message: 'Referenced host+subset in destinationrule not found: "map-nginx.project-1925.svc.cluster.local+v1"'
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
@zhengqisong can u provide a complete well indented vs to help us understand what happened?
+1
yikes. We need to fix this. One issue - I don't know how :slightly_smiling_face:
Just ran into this exact problem when upgrading istio - had to delete the offending resources for the upgrade to work correctly
@jasonwzm do you know if its possible to discard bad configs instead of block?
I removed the strict deserialization from CLI things and expect it will be easy to fix for istiod.
@howardjohn To test any fixes, I need to be able to reproduce. Two years ago it was easy to put bogus stuff in status using commands like kubectl patch vs bookinfo --type=json --patch='[{"op": "replace", "path": "/status", "value": {"startTime": "2019-06-05T17:52:46Z", "state": "ACTIVE"}}]'. Kubernetes no longer allows it. I made two guesses as to how to enable adding bogus stuff to /status and failed:
// Doesn't work, schema required
kubectl patch crd virtualservices.networking.istio.io --type='json' -p='[{"op": "remove", "path": "/spec/versions/0/schema"}]'
// Doesn't work "no change"
kubectl patch crd virtualservices.networking.istio.io --type='json' -p='[{"op": "remove", "path": "/metadata/managedFields"}]'
@therealmitchconnors
Any idea what protects /status? I know it is something in the API server, because if I do --dry-run=client I can set the status, but if I do --dry-run=server the status does not get patched.
You might need a raw api call. when you do patch it probably sends a PUT
call to /crds/virtualservices/foo or similar - we need it to go to
/crds/virtualservices/foo/status. You might be able to add -v9 to the
kubectl command to get the API its calling, add /status, then call it with
kubectl patch --raw?
On Thu, Mar 18, 2021 at 7:09 AM Ed Snible @.***> wrote:
I removed the strict deserialization from CLI things and expect it will be
easy to fix for istiod.
@howardjohn https://github.com/howardjohn To test any fixes, I need to
be able to reproduce. Two years ago it was easy to put bogus stuff in
status using commands like kubectl patch vs bookinfo --type=json
--patch='[{"op": "replace", "path": "/status", "value": {"startTime":
"2019-06-05T17:52:46Z", "state": "ACTIVE"}}]'. Kubernetes no longer
allows it. I made two guesses as to how to enable adding bogus stuff to
/status and failed:
// Doesn't work, schema required
kubectl patch crd virtualservices.networking.istio.io --type='json' -p='[{"op": "remove", "path": "/spec/versions/0/schema"}]'
// Doesn't work "no change"
kubectl patch crd virtualservices.networking.istio.io --type='json' -p='[{"op": "remove", "path": "/metadata/managedFields"}]'
@therealmitchconnors https://github.com/therealmitchconnors
Any idea what protects /status? I know it is something in the API server,
because if I do --dry-run=client I can set the status, but if I do
--dry-run=server the status does not get patched.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31014#issuecomment-801959404, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXN2G2H4NTGOUM4MSU3TEICTNANCNFSM4YB6FBNQ
.
There is no patch --raw in kubectl (I checked 1.19 and 1.20).
I tried
MYAPISERVER=c7.us-south.containers.cloud.ibm.com:28514
echo '{"status": "banana"}' | kubectl create --raw https://${MYAPISERVER}/apis/networking.istio.io/v1beta1/namespaces/default/virtualservices/httpbin/status -f -
... but it fails with 'create is not supported on resources of kind "virtualservices.networking.istio.io"'
https://github.com/kubernetes/kubectl/issues/564
On Thu, Mar 18, 2021 at 10:21 AM Ed Snible @.***> wrote:
There is no patch --raw in kubectl (I checked 1.19 and 1.20).
I tried
MYAPISERVER:28514=c7.us-south.containers.cloud.ibm.com
echo '{"status": "banana"}' | kubectl create --raw https://${MYAPISERVER}/apis/networking.istio.io/v1beta1/namespaces/default/virtualservices/httpbin/status -f -
... but it fails with 'create is not supported on resources of kind "
virtualservices.networking.istio.io"'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31014#issuecomment-802141282, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXNETDAT275QKNDCPB3TEIZB7ANCNFSM4YB6FBNQ
.
It seems to be an issue when analysis is enabled during startup and the unmarshaller encountered an issue. I vaguely remember that we changed the format of message level we put in status in CRDs?
To manually put garbage into status, first install Istio with WITHOUT values.global.istiod.enableAnalysis=true and WITHOUT values.pilot.env.PILOT_ENABLE_STATUS=true. Then
kubectl proxy &
curl -k -s -X PATCH -H "Accept: application/json, */*" \
-H "Content-Type: application/merge-patch+json" \
127.0.0.1:8001/apis/networking.istio.io/v1beta1/namespaces/default/virtualservices/httpbin/status \
--data '{"status":{"monkey":"banana"}}'
At this point, for master, I have no problem restarting or re-installing Istio with or without analysis. It is possible this was fixed in an earlier version. Checking...
I have a backtrace. istio.io/istio is not in the path. istio.io/api is generated code. Not sure what to do.
A user with authority to do kubectl proxy and modify any VirtualService can use the technique in https://github.com/istio/istio/issues/31014#issuecomment-802810868 to cause trouble for the control plane.
istio.io/api/meta/v1alpha1.(*IstioStatus).UnmarshalJSON(0xc000df93c8, 0xc002c300f0, 0x45, 0x50, 0xc000df93c8, 0x6a48b38)
/Users/snible/go/pkg/mod/istio.io/api@v0.0.0-20210318104759-fbefbc937cef/meta/v1alpha1/status_json.gen.go:35 +0x18d
github.com/json-iterator/go.(*unmarshalerDecoder).Decode(0xc001f6dc40, 0xc002abf1b0, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_marshaler.go:200 +0xdb
github.com/json-iterator/go.(*referenceDecoder).Decode(0xc001f6dc50, 0xc000df93c8, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_optional.go:128 +0x68
github.com/json-iterator/go.(*structFieldDecoder).Decode(0xc001f958e0, 0xc000df9200, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_struct_decoder.go:1054 +0x78
github.com/json-iterator/go.(*fiveFieldsStructDecoder).Decode(0xc000b38e40, 0xc000df9200, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_struct_decoder.go:739 +0x311
github.com/json-iterator/go.(*sliceDecoder).doDecode(0xc00106bd70, 0xc0002547c8, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_slice.go:86 +0xdd
github.com/json-iterator/go.(*sliceDecoder).Decode(0xc00106bd70, 0xc0002547c8, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_slice.go:60 +0x45
github.com/json-iterator/go.(*structFieldDecoder).Decode(0xc001f95c20, 0xc000254770, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_struct_decoder.go:1054 +0x78
github.com/json-iterator/go.(*fourFieldsStructDecoder).Decode(0xc0010587d0, 0xc000254770, 0xc000f03050)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect_struct_decoder.go:697 +0xbf
github.com/json-iterator/go.(*Iterator).ReadVal(0xc000f03050, 0x3ae97c0, 0xc000254770)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/reflect.go:79 +0xc2
github.com/json-iterator/go.(*frozenConfig).Unmarshal(0xc000374c80, 0xc002b57000, 0xc49, 0x1000, 0x3ae97c0, 0xc000254770, 0x0, 0x0)
/Users/snible/go/pkg/mod/github.com/json-iterator/go@v1.1.10/config.go:348 +0xb7
k8s.io/apimachinery/pkg/runtime/serializer/json.(*Serializer).Decode(0xc000226550, 0xc002b57000, 0xc49, 0x1000, 0x0, 0x4033d98, 0xc000254770, 0xc00d5a63302ad750, 0xc059add2, 0x5cdda00, ...)
/Users/snible/go/pkg/mod/k8s.io/apimachinery@v0.20.4/pkg/runtime/serializer/json/json.go:264 +0x5be
k8s.io/apimachinery/pkg/runtime.WithoutVersionDecoder.Decode(0x3ffcc00, 0xc000226550, 0xc002b57000, 0xc49, 0x1000, 0x0, 0x4033d98, 0xc000254770, 0xc002c24160, 0xc000bc5770, ...)
/Users/snible/go/pkg/mod/k8s.io/apimachinery@v0.20.4/pkg/runtime/helper.go:252 +0x97
k8s.io/client-go/rest.Result.Into(0xc002b57000, 0xc49, 0x1000, 0x0, 0x0, 0x0, 0xc001337c90, 0x10, 0x0, 0x0, ...)
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/rest/request.go:1273 +0xb4
istio.io/client-go/pkg/clientset/versioned/typed/networking/v1alpha3.(*virtualServices).List(0xc002c181c0, 0x407ce28, 0xc000076098, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/Users/snible/go/pkg/mod/istio.io/client-go@v0.0.0-20210218000043-b598dd019200/pkg/clientset/versioned/typed/networking/v1alpha3/virtualservice.gen.go:93 +0x29d
istio.io/client-go/pkg/informers/externalversions/networking/v1alpha3.NewFilteredVirtualServiceInformer.func1(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x3c28a4f, ...)
/Users/snible/go/pkg/mod/istio.io/client-go@v0.0.0-20210218000043-b598dd019200/pkg/informers/externalversions/networking/v1alpha3/virtualservice.gen.go:63 +0x1bc
k8s.io/client-go/tools/cache.(*ListWatch).List(0xc000e16888, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/tools/cache/listwatch.go:106 +0x75
k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1.1.2(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x3c28a4f, ...)
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/tools/cache/reflector.go:283 +0x75
k8s.io/client-go/tools/pager.SimplePageFunc.func1(0x407ce28, 0xc000076090, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/tools/pager/pager.go:40 +0x75
k8s.io/client-go/tools/pager.(*ListPager).List(0xc002c39e60, 0x407ce28, 0xc000076090, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/tools/pager/pager.go:91 +0x175
k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1.1(0xc002b7f4a0, 0xc000dfe1c0, 0xc002260870, 0xc002c06860, 0xc002c1a009, 0xc002c06870, 0xc001b83bc0)
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/tools/cache/reflector.go:309 +0x1e5
created by k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1
/Users/snible/go/pkg/mod/k8s.io/client-go@v0.20.4/tools/cache/reflector.go:271 +0x298
I am test in istio 1.6.8,1.6.13 1.7.4 ,1.7.6,1.8.3
public-system(the namespace publish service to outward) has gateway, virtualservice(exportTo: .)
project-1925(the namespace publish service to namespace`s service) has service, deploy, destinationrule, virtualservice(exportTo: .)
In <=1.7.4 public-system`s virtualservice has under error, but istod can restart
validationMessages:
- code: IST0101
documentation_url: https://istio.io/docs/reference/config/analysis/ist0101/?ref=status-controller
level: Error
message: 'Referenced host+subset in destinationrule not found: "map-nginx.project-1925.svc.cluster.local+v1"'
in 1.7.6 public-system`s virtualservice no error
upgrade from 1.7.4 to 1.8.3, istiod(1.8.3) canot not start
upgrade from 1.7.4 to 1.7.6, the public-system`s virtualservice error remain, but istiod(1.7.6) can started, and service can be connected.
upgrade from 1.7.4 to 1.7.6, then upgrade from 1.7.6 to 1.8.3, the public-system`s virtualservice error remain, but istiod(1.8.3) can not started,
{"level":"error","time":"2021-03-22T10:39:08.252656Z","scope":"klog","msg":"k8s.io/client-go@v0.19.3/tools/cache/reflector.go:156: Failed to watch *v1alpha3.VirtualService: failed to list
*v1alpha3.VirtualService: v1alpha3.VirtualServiceList.Items: []v1alpha3.VirtualService: v1alpha3.VirtualService.v1alpha3.VirtualService.Status: unmarshalerDecoder: unknown value \"Error\"
for enum istio.analysis.v1alpha1.AnalysisMessageBase_Level, error found in #10 byte of ...|l+v1\\\"\"}]}},{\"apiVer|..., bigger context ...|esh-b.project-1896.svc.frankfurtinp.local+v1\\\"
\"}]}},{\"apiVersion\":\"networking.istio.io/v1alpha3\",\"ki|...[]"}
install 1.7.6, then upgrade upgrade from 1.7.6 to 1.8.3 the public-system`s virtualservice no error, istiod(1.8.3) can started
I think This issues has two bug:
vs check has a bug, destination no support other namespaces destinationrule .
vs in public-system
http:
- match:
- uri:
prefix: /
rewrite:
uri: /
route:
- destination:
host: map-nginx.project-1896.svc.cluster.local
port:
number: 80
subset: v1
weight: 10
istiod(1.8.3) has a bug for parse VirtualService that has Error(level: Error)
status:
validationMessages:
- code: IST0101
documentation_url: https://istio.io/docs/reference/config/analysis/ist0101/?ref=status-controller
level: Error #this line parse Error
message: 'Referenced host+subset in destinationrule not found: "map-nginx.project-1896.svc.cluster.local+v1"
@zhengqisong Sorry for the late reply. Thank you for providing many details on reproducing the issue.
This is caused by https://github.com/istio/istio/pull/25960 where we were updating the validation output message to align with our status API. This changed the API output from 1.7 to 1.8 and therefore you see the unmarshalling error during istiod startup.
We are working on a refactoring of analysis and hoping to move it (including the API) out of alpha before 1.11. Before that, the upgrade experience may not be ideal when you have analysis enabled.
Does the current behavior cause additional trouble using Istio?
Jason, I think the problem extends beyond that? There is a potential DOS
vector by generating invalid configuration in etcd/api-server. istiod
should be resilient to bad configs
On Mon, Mar 29, 2021 at 10:25 AM Jason Wang @.***>
wrote:
@zhengqisong https://github.com/zhengqisong Sorry for the late reply.
Thank you for providing many details on reproducing the issue.
This is caused by #25960 https://github.com/istio/istio/pull/25960
where we were updating the validation output message to align with our
status API. This changed the API output from 1.7 to 1.8 and therefore you
see the unmarshalling error during istiod startup.
We are working on a refactoring of analysis and hoping to move it
(including the API) out of alpha before 1.11. Before that, the upgrade
experience may not be ideal when you have analysis enabled.
Does the current behavior cause additional trouble using Istio?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31014#issuecomment-809562694, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXL32XQZO3XGSY2KF3TTGCZWZANCNFSM4YB6FBNQ
.
@howardjohn Yes, that is the bigger concern here. This applies to any istio config that can be patched by users in etcd, though patching etcd is a highly privileged action. We should look into a more general way of handling that.
In this particular case, it is our code that output differently than expected in an enum field.
I modify etcd data success upgrade istiod
first get virtualservice-63-66 json in etcd
ETCDCTL_API=3 ./etcdctl --endpoints="https://127.0.0.1:2379" put /registry/networking.istio.io/virtualservices/mesh-system/virtualservice-63-66
scal deploy istiod --replicas=0
update virtualservice-63-66 drop status info in etcd
ETCDCTL_API=3 ./etcdctl --endpoints="https://127.0.0.1:2379" put /registry/networking.istio.io/virtualservices/mesh-system/virtualservice-152-75 '{"apiVersion":"networking.istio.io/v1alpha3","kind":"VirtualService","metadata":{"creationTimestamp":"2021-04-06T03:28:39Z","generation":1,"labels":{"application":"applicatiion-4089","project":"project-1927"},"managedFields":[{"apiVersion":"networking.istio.io/v1alpha3","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:labels":{".":{},"f:application":{},"f:project":{}}},"f:spec":{".":{},"f:exportTo":{},"f:gateways":{},"f:hosts":{},"f:http":{}}},"manager":"okhttp","operation":"Update","time":"2021-04-06T03:28:39Z"},{"apiVersion":"networking.istio.io/v1alpha3","fieldsType":"FieldsV1","fieldsV1":{"f:status":{".":{},"f:validationMessages":{}}},"manager":"pilot-discovery","operation":"Update","time":"2021-04-06T03:28:39Z"}],"name":"virtualservice-152-75","namespace":"mesh-system","uid":"899e3b64-fe55-4b4f-825b-d5e058842281"},"spec":{"exportTo":["."],"gateways":["gateway-152-75"],"hosts":["sdf4gdsfg.demo.com"],"http":[{"match":[{"uri":{"prefix":"/"}}],"rewrite":{"uri":"/"},"route":[{"destination":{"host":"mesh-01-nginx.project-1927.svc.cluster.local","port":{"number":80},"subset":"v1"},"weight":100}]}]}}'
scal deploy istiod --replicas=2
istiod only started new version
Hi everyone! First at all, thanks for your work and contribution!
I ran with the same problem upgrading Istio control plane, from v1.7.4 to v1.8.5 and from v1.6.14 to v1.8.5.
We have a lot of Istio's resources so we cannot patch them all to remove the status. There is any workaround to fix this?
Also the problem is not only in VirtualService CRD, seems the Sidecar is affected too:
{"level":"error","time":"2021-05-04T16:03:13.205337Z","scope":"klog","msg":"k8s.io/client-go@v0.19.3/tools/cache/reflector.go:156: Failed to watch *v1alpha3.Sidecar: failed to list *v1alpha3.Sidecar: v1alpha3.SidecarList.Items: []v1alpha3.Sidecar: v1alpha3.Sidecar.v1alpha3.Sidecar.Status: unmarshalerDecoder: unknown value \"Error\" for enum istio.analysis.v1alpha1.AnalysisMessageBase_Level, error found in #10 byte of ...|avior.\"}]}},{\"apiVer|..., bigger context ...|elector, which can lead to undefined behavior.\"}]}},{\"apiVersion\":\"networking.istio.io/v1alpha3\",\"ki|...[]"}
Thanks in advance, regards!
| gharchive/issue | 2021-02-23T07:14:59 | 2025-04-01T06:39:06.775417 | {
"authors": [
"esnible",
"howardjohn",
"hzxuzhonghu",
"jasonwzm",
"psanzm",
"samirmajen",
"xichengliudui",
"zhengqisong"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/31014",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1012435670 | service with externalname overrides istio-proxy 443 rules
Bug Description
I have some services without selector pointing to endpoints for external services to the cluster in order to monitor them.
At the moment I create the following object:
apiVersion: v1
kind: Service
metadata:
name: nexus-metrics-monitoring
namespace: external-monitoring
labels:
app: nexus-metrics-monitoring
spec:
externalName: nexus.internal
ports:
- name: nexus
port: 4443
protocol: TCP
targetPort: 443
- name: node
port: 9100
protocol: TCP
targetPort: 9100
- name: containers
port: 8080
protocol: TCP
targetPort: 8080
type: ExternalName
The TLS connections originated from inside the cluster in a pod with the istio-proxy sidecar starts to fail returning me 404 errors.
This is the istioctl proxy-config listeners toolkit-68754d4d6b-d7hm5 | grep 443 output:
0.0.0.0 443 Trans: raw_buffer; App: HTTP Route: 443
0.0.0.0 443 ALL Cluster: outbound|443||nexus-metrics-monitoring.external-monitoring.svc.cluster.local
10.100.107.185 443 ALL Cluster: outbound|443||istiod.istio-system.svc.cluster.local
10.107.150.172 443 ALL Cluster: outbound|443||istio-ingressgateway.istio-system.svc.cluster.local
10.107.212.31 443 ALL Cluster: outbound|443||keycloak.keycloak.svc.cluster.local
10.108.30.165 443 ALL Cluster: outbound|443||istio-egressgateway.istio-system.svc.cluster.local
10.96.0.1 443 ALL Cluster: outbound|443||kubernetes.default.svc.cluster.local
10.97.216.209 443 ALL Cluster: outbound|443||step-certificates.step-certificates.svc.cluster.local
10.97.92.163 443 ALL Cluster: outbound|443||monitoring-operator.monitoring.svc.cluster.local
And this is the output of the same command when the service is deleted and all works fine:
0.0.0.0 443 ALL PassthroughCluster
10.100.107.185 443 ALL Cluster: outbound|443||istiod.istio-system.svc.cluster.local
10.107.150.172 443 ALL Cluster: outbound|443||istio-ingressgateway.istio-system.svc.cluster.local
10.107.212.31 443 ALL Cluster: outbound|443||keycloak.keycloak.svc.cluster.local
10.108.30.165 443 ALL Cluster: outbound|443||istio-egressgateway.istio-system.svc.cluster.local
10.96.0.1 443 ALL Cluster: outbound|443||kubernetes.default.svc.cluster.local
10.97.216.209 443 ALL Cluster: outbound|443||step-certificates.step-certificates.svc.cluster.local
10.97.92.163 443 ALL Cluster: outbound|443||monitoring-operator.monitoring.svc.cluster.local
Version
istioctl version --remote
client version: 1.10.0
control plane version: 1.10.0
data plane version: 1.10.0 (47 proxies)
kubectl version --short
Client Version: v1.22.1
Server Version: v1.22.1
helm version --short
v3.4.1+gc4e7485
Additional Information
No response
See https://istio.io/latest/docs/ops/configuration/traffic-management/traffic-routing/#externalname-services you can name your 443 port with https prefix (https-nexus) to use SNI based routing.
@bianpengyuan it worked thank you.
One more thing, shouldn't this be awared somehow?
I mean, when you run "istioctl analyze --all-namespaces" this errors are being shown as an INFO [IST0118], but exactly this case an https port changed completely the behavior of all the connections from inside.
Yeah good point. It is an INFO because we have protocol sniffing and it is not necessary to name port. But in the case of externalname service, unnamed port can be disruptive. We probably should add a bit more warn message when service is externalname type.
@bianpengyuan I'd like to work on this issue. Can you assign it to me please?
@eliavem done. thanks for taking this!
Hi @bianpengyuan, I can see there are two possibilities for making users aware about this issue.
We can extend the diag.MessageType for message "PortNameIsNotUnderNamingConvention" - Info [IST0118]. We can add something like "Warning: unnamed port can affect [block] routing to external services for ExternalName service type"
If we want to display this warning only when we have an ExternalName service type, then we could create a separate diag.MessageType of type WARNING. In PortNameAnalyzer, we can add a check for ExternalName service type and display this message instead of [IST0118].
I would like to understand if your suggestion above - "We probably should add a bit more warn message when service is externalname type" can be covered with point #1
Hi @eliavem thank you for picking up this WI. I'd vote for only display this warning (perhaps even an error?) for service that has ExternalName. Because in normal services (not having ExternalName), it should be fine without causing users any issue with auto protocol detection.
I agree we should create a separated warning message for service of externalName.
@bianpengyuan I close this as you already fixed and merged it.
Thank you.
| gharchive/issue | 2021-09-30T17:25:08 | 2025-04-01T06:39:06.786249 | {
"authors": [
"bianpengyuan",
"eliavem",
"linsun",
"ricosega"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/35429",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1073789025 | Tracing: Istio HTTP->gRPC span doesn't appear in trace.
Inspired by investigations done in https://github.com/istio/istio/issues/11696
Environment:
IstioGateway->Service-A(http)->Service-B(gRPC)
Ports in services are named properly.
Service A Takes headers from incoming HTTP request and adds them to the outdoing gRPC requests to Service B:
XRequestID: requestID,
XB3TraceID: getHeader(xB3TraceID),
XB3SpanID: getHeader(xB3SpanID),
XB3ParentSpanID: getHeader(xB3ParentSpanID),
XB3Sampled: getHeader(xB3Sampled),
XB3Flag: getHeader(xB3Flags),
B3: getHeader(b3),
In Jaeger, I only see the trace from IstioGateway to Service A but no span for ServiceA to ServiceB.
Proxy log format is:
accessLogFormat: "[%START_TIME%] \"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%\" %RESPONSE_CODE% %RESPONSE_FLAGS% %RESPONSE_CODE_DETAILS% %CONNECTION_TERMINATION_DETAILS% \"%UPSTREAM_TRANSPORT_FAILURE_REASON%\" %BYTES_RECEIVED% %BYTES_SENT% %DURATION% %RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% \"%REQ(X-FORWARDED-FOR)%\" \"%REQ(USER-AGENT)%\" \"%REQ(X-B3-SAMPLED)%\" \"%REQ(X-REQUEST-ID)%\" \"%REQ(X-B3-TRACEID)%\" \"%REQ(X-B3-SPANID)%\" \"%REQ(X-B3-PARENTSPANID)%\" \"%REQ(:AUTHORITY)%\" \"%UPSTREAM_HOST%\" %UPSTREAM_CLUSTER% %UPSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_REMOTE_ADDRESS% %REQUESTED_SERVER_NAME% %ROUTE_NAME%\n"
The logs from the proxies:
InressGateway:
[2021-12-07T21:26:50.090Z] "POST /init HTTP/1.1" 200 - via_upstream - "-" 828 755 47 47 "78.133.70.82, 34.102.217.248,35.191.10.246" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36" "1" "303cef67-e3cb-9ff9-80aa-614c19d502b3" "b8b2896792ea92498a84596ac59bb845" "8a84596ac59bb845" "-" "gs1-gs-x.domain.tld" "10.100.32.24:8005" outbound|80||gs1-api-game-server.d01.svc.cluster.local 10.100.37.6:46938 10.100.37.6:80 35.191.10.246:49843 - play-for-real
ServiceA Incoming
[2021-12-07T21:26:50.091Z] "POST /init HTTP/1.1" 200 - via_upstream - "-" 828 755 46 45 "78.133.70.82, 34.102.217.248,35.191.10.246" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36" "1" "303cef67-e3cb-9ff9-80aa-614c19d502b3" "b8b2896792ea92498a84596ac59bb845" "7845ffbbf6266607" "8a84596ac59bb845" "gs1-gs-x.domain.tld" "10.100.32.24:8005" inbound|8005|| 127.0.0.6:52327 10.100.32.24:8005 35.191.10.246:0 outbound_.80_._.gs1-api-game-server.d01.svc.cluster.local default
ServiceA Outgoing
[2021-12-07T21:26:50.095Z] "POST /core_service_v1.CoreService/GetBalance HTTP/2" 200 - via_upstream - "-" 55 17 18 18 "-" "grpc-go/1.36.1" "1" "303cef67-e3cb-9ff9-80aa-614c19d502b3" "b8b2896792ea92498a84596ac59bb845" "7845ffbbf6266607" "8a84596ac59bb845" "gs1-api-core:50101" "10.100.37.2:8007" outbound|50101||gs1-api-core.d01.svc.cluster.local 10.100.32.24:49578 10.100.66.69:50101 10.100.32.24:45616 - default
ServiceB Incoming
[2021-12-07T21:26:50.096Z] "POST /core_service_v1.CoreService/GetBalance HTTP/2" 200 - via_upstream - "-" 55 17 15 14 "-" "grpc-go/1.36.1" "1" "303cef67-e3cb-9ff9-80aa-614c19d502b3" "b8b2896792ea92498a84596ac59bb845" "7845ffbbf6266607" "8a84596ac59bb845" "gs1-api-core:50101" "10.100.37.2:8007" inbound|8007|| 127.0.0.6:53567 10.100.37.2:8007 10.100.32.24:49578 outbound_.50101_._.gs1-api-core.d01.svc.cluster.local default
Based on that proxy logs it seems that spainId and parrentSpanId are not replaced by the envoy and propagated "as is" down to the ServiceB.
As an alternative experiment I called Service B via grpcCurl from the pod of ServiceA:
./grpcurl -rpc-header 'x-b3-sampled: 1' -rpc-header 'x-b3-traceid: ebf7561051ac6433952010cd9cac40d3' -rpc-header 'x-b3-parentspanid: 297e3236182ca725' -rpc-header 'x-b3-spanid: 952010cd9cacdddd' -rpc-header 'x-request-id: a48ace99-0d2f-9fa9-9aad-83d5fe03c579' -plaintext -proto core_service_v1.proto gs1-api-core:50101 core_service_v1.CoreService/GetBalance
ServiceA outgoing:
[2021-12-07T21:37:57.691Z] "POST /core_service_v1.CoreService/GetBalance HTTP/2" 200 - via_upstream - "-" 63 17 29 29 "-" "grpcurl/v1.8.5 grpc-go/1.37.0" "1" "a48ace99-0d2f-9fa9-9aad-83d5fe03c579" "ebf7561051ac6433952010cd9cac40d3" "7fc4a980a41d3edf" "952010cd9cacdddd" "gs1-api-core:50101" "10.100.37.2:8007" outbound|50101||gs1-api-core.d01.svc.cluster.local 10.100.32.24:54452 10.100.66.69:50101 10.100.32.24:38614 - default
ServiceB Incoming:
[2021-12-07T21:37:57.692Z] "POST /core_service_v1.CoreService/GetBalance HTTP/2" 200 - via_upstream - "-" 63 17 28 27 "-" "grpcurl/v1.8.5 grpc-go/1.37.0" "1" "a48ace99-0d2f-9fa9-9aad-83d5fe03c579" "ebf7561051ac6433952010cd9cac40d3" "cbc05a179e71686a" "7fc4a980a41d3edf" "gs1-api-core:50101" "10.100.37.2:8007" inbound|8007|| 127.0.0.6:42243 10.100.37.2:8007 10.100.32.24:54452 outbound_.50101_._.gs1-api-core.d01.svc.cluster.local default
As you can see, in this case, spans were replaced properly.
Debug log with grpc metadata from the application ServiceB when called by ServiceA:
2021/12/07 21:57:25 gRPC server metadata x-b3-flags:[];x-forwarded-proto:[http];:authority:[gs1-api-core:50101];user-agent:[grpc-go/1.36.1];x-b3-traceid:[3ffc9fb9cb04232b3a0ec68e6cc286ff];x-b3-spanid:[ffa5bc3f75abc782];x-b3-parentspanid:[3a0ec68e6cc286ff];x-forwarded-client-cert:[By=spiffe://cluster.local/ns/d01/sa/gs1-api-core;Hash=c0306f7205d9ac84e9e5b312c942b9a3465da206292ff0c7c6a4f635ce15ae91;Subject="";URI=spiffe://cluster.local/ns/d01/sa/gs1-api-game-server];content-type:[application/grpc];x-request-id:[d9d13ed6-bb8b-9123-a75a-fe0e456a350c];x-b3-sampled:[1];b3:[];x-envoy-attempt-count:[1];
Debug log with grpc metadata from the application ServiceB when called by GRPCcurl:
2021/12/07 21:58:40 gRPC server metadata content-type:[application/grpc];x-envoy-attempt-count:[1];x-b3-traceid:[ebf7561051ac6433952010cd9cac40d3];x-b3-parentspanid:[c846478c2b88b686];x-b3-sampled:[1];:authority:[gs1-api-core:50101];user-agent:[grpcurl/v1.8.5 grpc-go/1.37.0];x-request-id:[a48ace99-0d2f-9fa9-9aad-83d5fe03c579];x-forwarded-proto:[http];x-forwarded-client-cert:[By=spiffe://cluster.local/ns/d01/sa/gs1-api-core;Hash=c0306f7205d9ac84e9e5b312c942b9a3465da206292ff0c7c6a4f635ce15ae91;Subject="";URI=spiffe://cluster.local/ns/d01/sa/gs1-api-game-server];x-b3-spanid:[817e1c7f84e7f9ec];
Istio installed via helm version 1.12.0 with the following settings:
global:
tracer:
zipkin:
address: jaeger-collector.istio-system:9411
meshConfig:
accessLogFile: /dev/stdout
accessLogFormat: |
[%START_TIME%] "%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%" %RESPONSE_CODE% %RESPONSE_FLAGS% %RESPONSE_CODE_DETAILS% %CONNECTION_TERMINATION_DETAILS% "%UPSTREAM_TRANSPORT_FAILURE_REASON%" %BYTES_RECEIVED% %BYTES_SENT% %DURATION% %RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% "%REQ(X-FORWARDED-FOR)%" "%REQ(USER-AGENT)%" "%REQ(X-B3-SAMPLED)%" "%REQ(X-REQUEST-ID)%" "%REQ(X-B3-TRACEID)%" "%REQ(X-B3-SPANID)%" "%REQ(X-B3-PARENTSPANID)%" "%REQ(:AUTHORITY)%" "%UPSTREAM_HOST%" %UPSTREAM_CLUSTER% %UPSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_REMOTE_ADDRESS% %REQUESTED_SERVER_NAME% %ROUTE_NAME%
pilot:
traceSampling: 100
docker.io/istio/proxyv2:1.12.0
docker.io/istio/pilot:1.12.0
jaegertracing/all-in-one:1.28.0
At this point, I am lost and I am not sure why istio is not taking care of gRPC part of the trace and don't replace headers.
This looks weird.. Can you enable service B proxy trace log with istioctl proxy-config log POD --level=trace, Capture the log of the request from ingress and grpc curl directly from service A. Want to compare what is difference between those two request, which might attribute to why service B proxy does not initiate a span.
@bianpengyuan thanks for a quick response. Here we go:
Ingress Log:
[2021-12-08T08:53:58.386Z] "POST /init HTTP/1.1" 200 - via_upstream - "-" 828 754 4185 97 "78.133.70.82, 34.102.217.248,35.191.16.180" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36" "1" "b5c688cd-0846-9cab-9432-fe6704aa7a3c" "29639b27a30880e5ff53863e6d6b6bab" "ff53863e6d6b6bab" "-" "gs1-gs-x.domain.tld" "10.100.33.12:8005" outbound|80||gs1-api-game-server.d01.svc.cluster.local 10.100.36.3:59276 10.100.36.3:80 35.191.16.180:51409 - play-for-real
ServiceA:
[2021-12-08T08:51:12.838Z] "POST /init HTTP/1.1" 200 - via_upstream - "-" 828 754 708 694 "78.133.70.82, 34.102.217.248,35.191.18.0" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36" "1" "86dbe583-64d9-982f-abdf-90ea5b0411fa" "e70ae8c0491b8e46cb7909086c8a732a" "369bafcd44cd96f7" "cb7909086c8a732a" "gs1-gs-x.domain.tld" "10.100.36.8:8005" inbound|8005|| 127.0.0.6:36657 10.100.36.8:8005 35.191.18.0:0 outbound_.80_._.gs1-api-game-server.d01.svc.cluster.local default
[2021-12-08T08:51:13.036Z] "POST /core_service_v1.CoreService/GetBalance HTTP/2" 200 - via_upstream - "-" 55 17 58 58 "-" "grpc-go/1.36.1" "1" "86dbe583-64d9-982f-abdf-90ea5b0411fa" "e70ae8c0491b8e46cb7909086c8a732a" "369bafcd44cd96f7" "cb7909086c8a732a" "gs1-api-core:50101" "10.100.32.2:8007" outbound|50101||gs1-api-core.d01.svc.cluster.local 10.100.36.8:37150 10.100.66.69:50101 10.100.36.8:50170 - default
ServiceB log attached.
ServiceB-proxy.log
Same with CurlgRPC:
ServiceA log:
[2021-12-08T09:07:21.369Z] "POST /core_service_v1.CoreService/GetBalance HTTP/2" 200 - via_upstream - "-" 63 17 34 30 "-" "grpcurl/v1.8.5 grpc-go/1.37.0" "1" "a48ace99-0d2f-9fa9-9aad-83d5fe03c579" "ebf7561051ac6433952010cd9cac40d3" "222d8415b7cc1280" "952010cd9cacdddd" "gs1-api-core:50101" "10.100.32.2:8007" outbound|50101||gs1-api-core.d01.svc.cluster.local 10.100.36.8:36550 10.100.66.69:50101 10.100.36.8:53974 - default
Service B log attached.
ServiceB-curlgrpc.log
It seems it is fixed by removing b3 and b3flags empty headers. If I don't propogate them from ServiceA to ServiceB trace works and glues togather. Any ideas why? I remember advice from #11696 not to propagate empty headers.
Ah b3 and b3-flags actually implies sample decision: https://github.com/openzipkin/b3-propagation#debug-flag and envoy doc: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#config-http-conn-man-headers-x-b3-flags
Ah b3 and b3-flags actually implies sample decision: https://github.com/openzipkin/b3-propagation#debug-flag and envoy doc: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#config-http-conn-man-headers-x-b3-flags
so the root reason is empty b3 headers broken trace context?
Yes, it seems so. Is it expected behaviour?
so the root reason is empty b3 headers broken trace context?
Yes.
Yes, it seems so. Is it expected behaviour?
Yes. Close since this is expected. Thanks!
| gharchive/issue | 2021-12-07T22:00:42 | 2025-04-01T06:39:06.802961 | {
"authors": [
"bianpengyuan",
"movergan",
"zirain"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/36419",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1761202322 | [release-1.17] improve accesslog mode e2e tests
Manual cherrypick required.
#45504 failed to apply on top of branch "release-1.17":
Applying: improve accesslog mode e2e tests
Applying: retry
Using index info to reconstruct a base tree...
M tests/integration/telemetry/api/accesslogs_test.go
Falling back to patching base and 3-way merge...
Auto-merging tests/integration/telemetry/api/accesslogs_test.go
CONFLICT (content): Merge conflict in tests/integration/telemetry/api/accesslogs_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 retry
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
https://github.com/istio/istio/pull/45532 fixes this issue.
duplicated
| gharchive/issue | 2023-06-16T19:26:28 | 2025-04-01T06:39:06.805724 | {
"authors": [
"istio-testing",
"lei-tang",
"zirain"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/45527",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1985522629 | VM Sidecar drop connections on large number of them
Is this the right place to submit this?
[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio
Bug Description
We installed sidecar on a virtual machine with MySQL. Our architecture requires a large number of connections to the database (up to 10,000)
But when we reach 1700-2000 connections, we can no longer connect and get errors like this
2023-11-03T10:23:44.119694Z critical envoy backtrace external/envoy/source/server/backtrace.h:104 Caught Aborted, suspect faulting address 0x3dd000368cc thread=223451
2023-11-03T10:23:44.119762Z critical envoy backtrace external/envoy/source/server/backtrace.h:91 Backtrace (use tools/stack_decode.py to get line numbers): thread=223451
2023-11-03T10:23:44.119802Z critical envoy backtrace external/envoy/source/server/backtrace.h:92 Envoy version: a1ff538a63890e27dd2add4b2680ba8dc49293ca/1.27.1-dev/Clean/RELEASE/BoringSSL thread=223451
2023-11-03T10:23:44.119551Z critical envoy assert external/envoy/source/common/network/socket_interface_impl.cc:72 assert failure: SOCKET_VALID(result.return_value_). Details: socket(2) failed, got error: Too many open filesthread=223446
ulimit -n
40000
Version
version 1.19.3
OS rocky linux 9
Additional Information
No response
There is a limit in your os, try to check ulimit -a
open files (-n) 40000
4000 limits all the process in the os
increase limit, error disappeared but problem not
ulimit -a
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 58746
max locked memory (kbytes, -l) 8192
max memory size (kbytes, -m) unlimited
open files (-n) 524288
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 58746
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
[root@db1-test ~]# lsof | wc -l
347505
[root@db1-test ~]# netstat -atn|wc -l
1613
IIRC, in istio we set connection pool max connections to MAXUint32, so there is not connection number limit. But there is a max idle time per idle connection. So check if this idle timeout cause connection close or there is a connection number limit on MySQL setting
| gharchive/issue | 2023-11-09T12:29:22 | 2025-04-01T06:39:06.810266 | {
"authors": [
"Killgore87",
"hzxuzhonghu"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/47802",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
273994091 | Add api key
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
First add the api attributs into install/kubernetes/templates/istio-mixer.yaml.tmpl, then run ./install/updateVersion.sh
Release note:
NONE
@apicl: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-presubmit.sh
43671b10b3e54f9d9647af6959a728331856dabc
link
/test istio-presubmit
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
I don't know the purpose of any of these files, so I'll pass on reviewing this :-)
/lgtm
PTAL
/lgtm
@apicl: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-presubmit.sh
65b5d1e2c32e830151e0cdf3af46d1adb189f445
link
/test istio-presubmit
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
I'd like someone familiar with all these files to comment first before approving...
/assign @costinm
/lgtm
/retest
/lgtm
@apicl: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-presubmit.sh
e6a10b2acad1c99a847b07c04c8fdab92e699266
link
/test istio-presubmit
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/retest
@apicl: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-presubmit.sh
e6a10b2acad1c99a847b07c04c8fdab92e699266
link
/test istio-presubmit
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/retest
@apicl: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-presubmit.sh
e6a10b2acad1c99a847b07c04c8fdab92e699266
link
/test istio-presubmit
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/lgtm
| gharchive/pull-request | 2017-11-15T00:38:24 | 2025-04-01T06:39:06.831144 | {
"authors": [
"apicl",
"douglas-reid",
"geeknoid",
"istio-testing",
"manlinl"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/1726",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
608707848 | [release-1.6] unit tests for ServiceEntry update fix
This is an automated cherry-pick of #23354
@googlebot I consent
@istio-testing: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
unit-tests_istio_release-1.6
b2da85f3a9f1f16e78a094331c4f4af008b1e474
link
/test unit-tests_istio_release-1.6
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/retest
@istio-testing: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
unit-tests_istio_release-1.6
b2da85f3a9f1f16e78a094331c4f4af008b1e474
link
/test unit-tests_istio_release-1.6
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/retest
| gharchive/pull-request | 2020-04-29T01:01:14 | 2025-04-01T06:39:06.838797 | {
"authors": [
"brian-avery",
"istio-testing",
"jacob-delgado",
"rshriram"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/23361",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
615239652 | [kiali] pilot version endpoint is gone, use the new istiod replacement
fixes: https://github.com/istio/istio/issues/23677
pilot service version endpoint is gone in 1.6 - replaced with analogous version endpoint in the istiod service. Kiali needs to switch to using the new istiod endpoint.
In response to a cherrypick label: new pull request created: #23679
| gharchive/pull-request | 2020-05-09T18:57:56 | 2025-04-01T06:39:06.840566 | {
"authors": [
"istio-testing",
"jmazzitelli"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/23678",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
708532760 | multicluster registries respect endpointmode
Currently only the "main" registry has the endpoint mode set. This adds that for multicluster remote registries.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.
@stevenctl: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
release-notes_istio
88e9071cedfa2e10ef923be70372e21abe041875
link
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/retest
@howardjohn I actually don't want this to merge yet. I have a strong feeling the endpointslice tests will fail. I saw that happening in https://github.com/istio/istio/pull/27493 even with this change. That PR is just to get the pilot/mc tests green so we get to the point where that's blocking. I've had it passing a few times now consistently to have it break later when incompatible thing are added.
Looks like ingress gateways in remote clusters fail to get discovery:
https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/27531/integ-pilot-multicluster-tests_istio/1605
@stevenctl: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
gencheck_istio
8d64296bee64befb70fdd4366186d8aa470ac273
link
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
| gharchive/pull-request | 2020-09-24T23:23:45 | 2025-04-01T06:39:06.850487 | {
"authors": [
"howardjohn",
"istio-testing",
"stevenctl"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/27531",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
809788022 | ext-authz: return error for invalid extension provider only when it is being used
Fixes #30824
If some extension provider is not used by any authz policy, it should not cause errors even if it might be invalid.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any changes that may affect Istio users.
@yangminzhu: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
integ-pilot-k8s-tests_istio
b19a0db87b840a6e6b4e590eaddd346d079a26c9
link
/test integ-pilot-k8s-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test integ-pilot-k8s-tests_istio
is the error in the original issue coming from the validation webhook when applying the meshconfig updaets? I didn't see other unit test updates other than validation-test.go
is the error in the original issue coming from the validation webhook when applying the meshconfig updaets? I didn't see other unit test updates other than validation-test.go
@incfly not from validation webhook but directly from the authz plugin in pilot, it emits the error every time it is called when pushing xDS configs to proxy.
In response to a cherrypick label: new pull request created: #30959
| gharchive/pull-request | 2021-02-17T01:59:26 | 2025-04-01T06:39:06.858666 | {
"authors": [
"incfly",
"istio-testing",
"yangminzhu"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/30878",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
963036833 | Fuzzing: Add bootstrap fuzzer
Adds fuzzer that creates a fuzzed bootstrap.PilotArgs{} and passes it on to bootstrap.NewServer()
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Please check any characteristics that apply to this pull request.
[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.
Hi @AdamKorcz. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/ok-to-test
@AdamKorcz: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
| gharchive/pull-request | 2021-08-06T20:48:29 | 2025-04-01T06:39:06.866245 | {
"authors": [
"AdamKorcz",
"hzxuzhonghu",
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/34567",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1266144518 | Add new well known pilot dns TLS cert loading - making it zero config for istio-csr installation
This approach takes an alternative approach to loading pilot DNS certs from secrets for pilot on initialisation proposed by @costinm here.
We had previously opted for trying to load these through the existing tls arguments mechanism in Pilot, demonstrated in PRs (#38845 and #37264 ),
the previous approach required some extra volume mounts in the helm manifest, it made the UX more difficult for installing istio-csr.
The current approach is to load the TLS certs from known locations if args are not set, and mount those volumes in anyways as optional: true volumes.
Well known path locations:
PilotWellKnownDNSCertPath = "/etc/pilot/tls/"
PilotWellKnownDNSCaCertPath = "/etc/pilot/ca/"
DefaultPilotTLSCert = PilotWellKnownDNSCertPath + "tls.crt"
DefaultPilotTLSKey = PilotWellKnownDNSCertPath + "tls.key"
DefaultPilotTLSCaCert = PilotWellKnownDNSCaCertPath + "root-cert.pem"
These match how istio-csr for example (custom plugin CA solution) mounts volumes to those paths (it loads the tls secret from an istiod-tls secret and trust anchor from istio-ca-root-configmap)
Hi @SpectralHiss. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/ok-to-test
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test release-notes_istio
lint_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test release-notes_istio
lint_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test lint_istio
gencheck_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test gencheck_istio
integ-security-multicluster_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
If you are using VS code as an editor, you can add gofumpt as the format tool and that will help with most lint errors:
"go.formatFlags": [
"[\"-ed\", \"-local\", \"istio.io\"]"
],
"go.formatTool": "gofumpt",
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test lint_istio
gencheck_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test gencheck_istio
integ-security-multicluster_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test integ-security-multicluster_istio
release-notes_istio
ae03d7567d677718661f4ae4d3f340a03cfa9fce
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test lint_istio
integ-security-multicluster_istio
bbe3e2314d1afc7fe64869a0f7e97a2acf6438cd
link
true
/test integ-security-multicluster_istio
release-notes_istio
ae03d7567d677718661f4ae4d3f340a03cfa9fce
link
true
/test release-notes_istio
gencheck_istio
ae03d7567d677718661f4ae4d3f340a03cfa9fce
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
ae03d7567d677718661f4ae4d3f340a03cfa9fce
link
true
/test gencheck_istio
release-notes_istio
0da2d1784b2f564e389cefa194eda2687e050451
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
ae03d7567d677718661f4ae4d3f340a03cfa9fce
link
true
/test gencheck_istio
release-notes_istio
0da2d1784b2f564e389cefa194eda2687e050451
link
true
/test release-notes_istio
unit-tests_istio
0da2d1784b2f564e389cefa194eda2687e050451
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
0da2d1784b2f564e389cefa194eda2687e050451
link
true
/test unit-tests_istio
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
0da2d1784b2f564e389cefa194eda2687e050451
link
true
/test unit-tests_istio
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-notes_istio
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
unit-tests_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test unit-tests_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test release-test_istio
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-ipv6_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-ipv6_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-distroless_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-cni_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-cni_istio
integ-operator-controller_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-operator-controller_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-security_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-multicluster_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-helm_istio
integ-telemetry_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry_istio
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-telemetry-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-telemetry-mc_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-multicluster_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
lint_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote-mc_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test integ-pilot-istiodremote-mc_istio
gencheck_istio
2f3d311d08a70f1f41ec19546001c53f0cb79f93
link
true
/test gencheck_istio
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
lint_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-notes_istio
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
lint_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test lint_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test unit-tests_istio
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
release-notes_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test release-notes_istio
lint_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-helm_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-helm_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
release-notes_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test release-notes_istio
lint_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test lint_istio
unit-tests_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test release-test_istio
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-pilot-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
release-notes_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test release-notes_istio
lint_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test lint_istio
unit-tests_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test unit-tests_istio
integ-helm_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test integ-helm_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-ipv6_istio
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-operator-controller_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-operator-controller_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
release-notes_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test release-notes_istio
lint_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test lint_istio
unit-tests_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test unit-tests_istio
integ-helm_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test integ-pilot-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot_istio
integ-distroless_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-distroless_istio
integ-telemetry-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-istiodremote_istio
integ-cni_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-cni_istio
integ-pilot-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-multicluster_istio
integ-telemetry_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry_istio
integ-telemetry-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
unit-tests_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test unit-tests_istio
integ-helm_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
68f0393cb391d8e6a285bd83d3e6951acc81c4ef
link
true
/test integ-pilot-istiodremote_istio
release-notes_istio
08b2fd429d88be1a22ca67f1414c63fd0d85361a
link
true
/test release-notes_istio
lint_istio
08b2fd429d88be1a22ca67f1414c63fd0d85361a
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
lint_istio
08b2fd429d88be1a22ca67f1414c63fd0d85361a
link
true
/test lint_istio
release-notes_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
lint_istio
08b2fd429d88be1a22ca67f1414c63fd0d85361a
link
true
/test lint_istio
release-notes_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test release-notes_istio
unit-tests_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-multicluster_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
88a3e7259149e27c61cc5a1b955c71e558419240
link
true
/test integ-security-istiodremote_istio
release-notes_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test release-notes_istio
unit-tests_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test unit-tests_istio
lint_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test release-notes_istio
unit-tests_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test unit-tests_istio
lint_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test lint_istio
integ-security-multicluster_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test release-notes_istio
unit-tests_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test unit-tests_istio
lint_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test lint_istio
integ-security-multicluster_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test integ-security-multicluster_istio
integ-security_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test integ-security_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test lint_istio
integ-security-multicluster_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test integ-security-multicluster_istio
integ-security_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test integ-security_istio
release-notes_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test release-notes_istio
unit-tests_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-multicluster_istio
57ade70b985b40a58eb02b023d403b2f97ced355
link
true
/test integ-security-multicluster_istio
release-notes_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test release-notes_istio
unit-tests_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test unit-tests_istio
integ-security_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test integ-security_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test unit-tests_istio
integ-security_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test integ-security_istio
release-notes_istio
dc209ba3f7a9ac6c5a016446ffe2cfa9692e48c7
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test integ-security_istio
release-notes_istio
dc209ba3f7a9ac6c5a016446ffe2cfa9692e48c7
link
true
/test release-notes_istio
unit-tests_istio
dc209ba3f7a9ac6c5a016446ffe2cfa9692e48c7
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security_istio
b8022124716c5959ac88117d5233c7ea8621c51c
link
true
/test integ-security_istio
unit-tests_istio
dc209ba3f7a9ac6c5a016446ffe2cfa9692e48c7
link
true
/test unit-tests_istio
release-notes_istio
66966f9d2ba3dd6abe3a38afb3283faf593fe46d
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
66966f9d2ba3dd6abe3a38afb3283faf593fe46d
link
true
/test unit-tests_istio
release-notes_istio
66966f9d2ba3dd6abe3a38afb3283faf593fe46d
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
66966f9d2ba3dd6abe3a38afb3283faf593fe46d
link
true
/test unit-tests_istio
release-notes_istio
17e1297b99f28d6bef4a5aec984622ebb525f03a
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
17e1297b99f28d6bef4a5aec984622ebb525f03a
link
true
/test release-notes_istio
unit-tests_istio
17e1297b99f28d6bef4a5aec984622ebb525f03a
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
17e1297b99f28d6bef4a5aec984622ebb525f03a
link
true
/test unit-tests_istio
release-notes_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test release-notes_istio
unit-tests_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test release-notes_istio
unit-tests_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test unit-tests_istio
lint_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test unit-tests_istio
lint_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test lint_istio
release-notes_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
4d43197d3112ec66713f59b77d1002069c73e343
link
true
/test lint_istio
release-notes_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test release-notes_istio
unit-tests_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test release-notes_istio
unit-tests_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test unit-tests_istio
lint_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test unit-tests_istio
lint_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test lint_istio
release-notes_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
7b91628d090fffb12cdcae27e3f8898a9b70d6c9
link
true
/test lint_istio
release-notes_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test release-notes_istio
unit-tests_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test release-notes_istio
unit-tests_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test unit-tests_istio
lint_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test unit-tests_istio
lint_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test lint_istio
release-notes_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
e07800a2b8b1f1ad0575bab1c3a0374838bf1191
link
true
/test unit-tests_istio
release-notes_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test release-notes_istio
lint_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test release-notes_istio
lint_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test lint_istio
unit-tests_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test lint_istio
unit-tests_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test unit-tests_istio
release-notes_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
441ed575659aa126cceb3b6ff83ce1c59f24d597
link
true
/test unit-tests_istio
release-notes_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test release-notes_istio
lint_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test release-notes_istio
lint_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test lint_istio
unit-tests_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test lint_istio
unit-tests_istio
8c5832b8efae028b7e5cd64b2e0d3a4987680ca2
link
true
/test unit-tests_istio
release-notes_istio
e10356006b09591147b9069442b026ec07de73c1
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
e10356006b09591147b9069442b026ec07de73c1
link
true
/test release-notes_istio
unit-tests_istio
e10356006b09591147b9069442b026ec07de73c1
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
e10356006b09591147b9069442b026ec07de73c1
link
true
/test unit-tests_istio
release-notes_istio
d0c38f9ec30e091bc0f3b0717c322d462aae5ec9
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test release-notes_istio
lint_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test lint_istio
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
On the 'well known paths' - I think the current practice is to use /var/run/secrets/istiod instead of /etc/... - one good reason is that some backup apps skip this directory ( or so I heard ). I would also avoid using the old name 'pilot' - we now use Istiod. Sorry I missed this in the original review.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test lint_istio
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
unit-tests_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test unit-tests_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test lint_istio
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test lint_istio
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
8a06c74ab44ce3847d1bbb664b7db93ec19beb4b
link
true
/test gencheck_istio
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
integ-helm_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-helm_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-notes_istio
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
integ-helm_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-helm_istio
gencheck_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test unit-tests_istio
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
lint_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test lint_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
integ-helm_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-helm_istio
gencheck_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test gencheck_istio
release-notes_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
integ-helm_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-helm_istio
gencheck_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test gencheck_istio
release-notes_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test release-notes_istio
lint_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test lint_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-operator-controller_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-operator-controller_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-security_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security_istio
integ-security-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-istiodremote_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-distroless_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-distroless_istio
integ-pilot-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-istiodremote-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-security-multicluster_istio
integ-ipv6_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
integ-helm_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-helm_istio
release-notes_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test release-notes_istio
lint_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test lint_istio
gencheck_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-test_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test release-test_istio
integ-cni_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-cni_istio
integ-pilot_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-istiodremote_istio
integ-telemetry_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-pilot-multicluster_istio
integ-telemetry-mc_istio
b25a7b12589cd9578d7591845255de245841d81d
link
true
/test integ-telemetry-mc_istio
lint_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test lint_istio
gencheck_istio
664854fb7fe62dbd0cbdff57ba5233399ac0f3ed
link
true
/test gencheck_istio
release-notes_istio
528a40575a908b760d7dc42b2e252f131c96ed9b
link
true
/test release-notes_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/retest-required
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-multicluster_istio
59e312261446efc895a356049a0983189f26e046
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test integ-security-multicluster_istio
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
af0e095dccade2b1a3f98bd04ab3476ffae74795
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
ef7672cc67e372136339e5a1231e738bb146c444
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test integ-security-multicluster_istio
Thanks for kicking this @GregHanson , I think i fixed all them pesky CLA violation, it was different emails setup on different machines.. once all tests pass again i will change WIP status on PR and await a final review. I will update this issue and perhaps close this PR if this PR is accepted.
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
45e2d8fd4fc9d69d2d2bdf6a83ed6262071a0b57
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test integ-security-multicluster_istio
Thanks for kicking this @GregHanson , I think i fixed all them pesky CLA violation, it was different emails setup on different machines.. once all tests pass again i will change WIP status on PR and await a final review. I will update this issue and perhaps close this PR if this PR is accepted.
Oh and one more thing left, need to change the istio manifest to actually load the known volumes :)
@SpectralHiss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-istiodremote_istio
integ-helm_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-helm_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test gencheck_istio
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-istiodremote-mc_istio
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-istiodremote_istio
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-ipv6_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot-multicluster_istio
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-pilot_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-pilot_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-operator-controller_istio
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-cni_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-cni_istio
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-security-multicluster_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security-multicluster_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry-mc_istio
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-security_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-security_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry_istio
0cf14e0798a363a192c74bf95b27f780c67b1c2e
link
true
/test integ-telemetry_istio
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
gencheck_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test gencheck_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-istiodremote-mc_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
integ-telemetry-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-istiodremote_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-security-istiodremote_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-istiodremote_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-helm_istio
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-basic-arm64_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-basic-arm64_istio
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-distroless_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-ipv6_istio
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot-multicluster_istio
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-operator-controller_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-operator-controller_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-pilot_istio
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-cni_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-cni_istio
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-multicluster_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry-mc_istio
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-security-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-multicluster
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-security_istio
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-security-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-multicluster
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry_istio
7e66165d73a1a17cded695bc4036cb55c8259c38
link
true
/test integ-telemetry_istio
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-security-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-multicluster
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test gencheck
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-security-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-multicluster
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote
integ-pilot-istiodremote-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-istiodremote-mc
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-istiodremote
integ-helm_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-helm
integ-basic-arm64_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-basic-arm64
integ-distroless_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-distroless
integ-ipv6_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-security-multicluster_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security-multicluster
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
gencheck_istio
2037f0589d00e50ead46a15673c0dbc293a91f3f
link
true
/test gencheck
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
gencheck_istio
2037f0589d00e50ead46a15673c0dbc293a91f3f
link
true
/test gencheck
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-istiodremote_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-istiodremote
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-operator-controller
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-cni_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-cni
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-pilot
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
integ-pilot_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-security_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-security
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
integ-pilot_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot
integ-security-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-multicluster
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-telemetry_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
integ-pilot_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot
integ-security-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-multicluster
integ-security_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry-mc_istio
e42112acc7dbf68c49005243e43e257c279052d6
link
true
/test integ-telemetry-mc
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
integ-pilot_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot
integ-security-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-multicluster
integ-security_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security
integ-telemetry_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-basic-arm64_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-basic-arm64
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
integ-pilot_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot
integ-security-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-multicluster
integ-security_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security
integ-telemetry_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry
integ-telemetry-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-mc
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@SpectralHiss: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-helm
integ-pilot-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote
integ-telemetry-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-istiodremote
integ-security-istiodremote_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-istiodremote
integ-pilot-istiodremote-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-istiodremote-mc
integ-distroless_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-distroless
integ-ipv6_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-ipv6
integ-pilot-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot-multicluster
integ-operator-controller_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-operator-controller
integ-cni_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-cni
integ-pilot_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-pilot
integ-security-multicluster_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security-multicluster
integ-security_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-security
integ-telemetry_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry
integ-telemetry-mc_istio
c7351852da01a56323a3e306aa5eb2b902e5447d
link
true
/test integ-telemetry-mc
gencheck_istio
c4949f39c1e7a0e24fe60faf0fc7d2aded8df5f2
link
true
/test gencheck
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
still seems to require root to run
Sorry, i just missed a dot for the PilotWellKnownDNSCaCertPath , can you try again because i still have the other problem that i can't run locally without hanging and maxing out my disk: https://github.com/istio/istio/issues/39303
| gharchive/pull-request | 2022-06-09T13:36:29 | 2025-04-01T06:39:08.995922 | {
"authors": [
"GregHanson",
"SpectralHiss",
"costinm",
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/39375",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1829733284 | Automator: update proxy@master in istio/istio@master
Generated by Automator - 2023-07-31T17:20:18+00:00
@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests_istio
79bcba59f9e34055746917337b9ab69ffce4b646
link
true
/test unit-tests
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test unit-tests
| gharchive/pull-request | 2023-07-31T17:45:43 | 2025-04-01T06:39:09.007335 | {
"authors": [
"ericvn",
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/46248",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1945635275 | move stateful set filter to per route filter
This PR
Moves the Statefulsession filter to per route instead of per virtual host
Decides based on route destination i.e. if the route destination service has labels attached this filter will be added. Without this, the stateful session filter wont be generated for virtual hosts that are generated based on virtual service hosts.
Added tests to cover these flows
[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test release-notes
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test release-notes
unit-tests-arm64_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test unit-tests-arm64
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
release-notes_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test release-notes
unit-tests-arm64_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test unit-tests-arm64
unit-tests_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test unit-tests
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
unit-tests-arm64_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test unit-tests-arm64
unit-tests_istio
511ef4384c927680edce24053bd559a8cc2b9f61
link
true
/test unit-tests
release-notes_istio
96acff9e07bd4bfbbced0a4fb3f1dcfefdf33ad3
link
true
/test release-notes
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/test release-notes
Ok to approve it after we clarify the semantics and backward compat impact, may be best to review alongside release notes.
@costinm retained the old behaviour for BC and added comments. PTAL
@costinm Can you PTAL?
@costinm @hzxuzhonghu @howardjohn Can you PTAL when you get chance?
While setting all route filters with same stateful session, and also same statefulset in virtualHost level. Isn't it equal to the VirtualHost level config before?
Earlier solution does not add stateful session filter for all "hosts" defined on virtual service - and hence it does not apply to all routes. This fixes that. Please see the test case
I know that, what I mean is when vs hosts equals the service hostname, then it will apply same filter to both virtualHost and per route level. Is that redundant?
I know that, what I mean is when vs hosts equals the service hostname, then it will apply same filter to both virtualHost and per route level. Is that redundant?
It is but does not make any behavioural difference. Long term, for us it would be better to move to per route.
@hzxuzhonghu Can you PTAL when you get chance?
Last question will per route filter take precedence over virtualhost one?
I am aksing because i think if user setup simiar case like different matching to apply different headers, but all route to one same service, then maybe he only need to apply the filter to per virtualHost
yes. per route takes precedence over per virtual host. I think those are cases which can not easily solved with simple env var. We need proper API
@hzxuzhonghu @costinm gentle ping Can you PTAL?
I am concerned that this may not be the eventual ideal prototype.
SVC A ->Detination with SVCB
->Detination with SVCC
->Detination with SVCD, here we would choose oneof B or C Or D's affinity policy to apply.
here we would choose oneof B or C Or D's affinity policy to apply.
Not exactly. It is based on your destination. If your destination is B - we use B's affinity policy for that route which makes sense to me.
SVC A's Route matching xxx -> SVCB (40%)
-> SVCC (30%)
-> SVCD(30%)
In this example, it may choose B or C Or D's affinity policy to apply.
In this example, it may choose B or C Or D's affinity policy to apply.
Correct. It is tricky to configure for weighted destinations pointing to different destinations. As I said most common use case is to use same destination but different versions
Yes, it is not common. One case probably split some traffic to canary release.
@hzxuzhonghu What do you suggest? IMO this is a decent fix that would solve some important use cases for us(except the weighted confusion which we agree that it is rare use case)
@hzxuzhonghu Ok. Changed. PTAL
Thanks
/lgtm
| gharchive/pull-request | 2023-10-16T16:24:05 | 2025-04-01T06:39:09.036383 | {
"authors": [
"costinm",
"hzxuzhonghu",
"istio-testing",
"ramaraochavali"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/47376",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2761407658 | removed unused const
Please provide a description of this PR:
Removed some unused const
@my-git9: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
fc127385cd3575f022432c5264299b8e094e1c4e
link
true
/test lint
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
@my-git9: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
fc127385cd3575f022432c5264299b8e094e1c4e
link
true
/test lint
unit-tests-arm64_istio
1cb15980e1d58fbb829da0594ed612444ba3f3d5
link
true
/test unit-tests-arm64
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
| gharchive/pull-request | 2024-12-28T02:57:09 | 2025-04-01T06:39:09.044814 | {
"authors": [
"istio-testing",
"my-git9"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/54489",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
247781298 | Port the existing e2e smoke test (may be others) to the new mixer adapter 0.2 model
Before we can delete code existing code, we need to port the existing e2e tests (inside and outside mixer repo) to use the new adapter model.
This can be closed. We should track the move of APAs in a 0.3 issue.
| gharchive/issue | 2017-08-03T17:35:58 | 2025-04-01T06:39:09.046094 | {
"authors": [
"douglas-reid",
"guptasu"
],
"repo": "istio/mixer",
"url": "https://github.com/istio/mixer/issues/1002",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
242223365 | File system config adapter
Provide an alternative file system based backend as a temporary solution for VM work.
This work will likely be superseded by one Galley adaptor to replace both FS and TPR adapters.
File system store.
Implement route rule representation as files in a directory hierarchy.
inotify watcher.
Implement config change watcher using inotify.
cc @gnirodi @costinm @rshriram @mandarjog
subscribe
closing as we're focusing on CRD backend first.
| gharchive/issue | 2017-07-12T00:35:21 | 2025-04-01T06:39:09.048090 | {
"authors": [
"kyessenov",
"ldemailly"
],
"repo": "istio/pilot",
"url": "https://github.com/istio/pilot/issues/924",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2465089112 | [Documentation] Add README
Relevant documentation
Other
Problem description (optional)
Currently this project has no useful content in its README file
Desired solution
Add a README file with useful information.
Keep in mind our central documentation tool will be Vitepress, this means the README should only contain the most important information and link to the Vitepress documentation where useful.
Additional context (optional)
No response
No duplicate
[X] I confirm that this issue is not a duplicate
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Maybe https://readme.so can help here? However we need to discuss what parts of documentation only should be part of docs/ and which are also worth mentioning in the README.
I'm e.g. thinking about things like LICENSE, Contribution information, ...
| gharchive/issue | 2024-08-14T07:20:47 | 2025-04-01T06:39:09.079863 | {
"authors": [
"devtobi"
],
"repo": "it-at-m/refarch-templates",
"url": "https://github.com/it-at-m/refarch-templates/issues/190",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2381539413 | [UBS AutoNotification] Links in autonotifications are not clickable in 'Messages' tab
Environment: Chrome 126.0.6478.127 (64-bit)
Reproducible: always
Build found: 29.06.24
Preconditions
Go to https://www.pick-up.city/ as client
Open 'My profile'
Click on 'Messages' tab
Client has notifications with links (such as The courier route formed, Violation of the rules, Pay for the change in the order, Unpaid Order) in 'Messages' tab
Steps to reproduce
Expand notification (by clicking on the up arrow)
Pay attention to the links in the message
Actual result
Links in notifications are not clickable in 'Messages' tab
Expected result
Links in notifications are clickable and active in 'Messages' tab
User story #2796
The link to the messenger is not clickable
https://github.com/user-attachments/assets/8a6697be-8a1a-4e7e-b229-074c2ff75d0c
https://github.com/user-attachments/assets/8a6697be-8a1a-4e7e-b229-074c2ff75d0c
| gharchive/issue | 2024-06-29T06:50:48 | 2025-04-01T06:39:09.086263 | {
"authors": [
"borntoshine1",
"liliaruda"
],
"repo": "ita-social-projects/GreenCity",
"url": "https://github.com/ita-social-projects/GreenCity/issues/7238",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1793746420 | Admin [Interesting facts block] Verify if Admin can add a new fact via "+" button
Priority: high
Description:
Test case verifies if the Admin can add a new fact via the "+" button
Preconditions
The website is already open, and a user is logged in as Admin
Steps to reproduce
Navigate to the "Interesting facts" section "Wow - факти"
Click on the "+" button
Add an image , title ( Премія Романа Ратушного) and text ( Український журналіст, публіцист і письменник Вахтанг Кіпіані від імені «Історичної правди» ініціював заснування іменної премії Романа Ратушного для молодих авторів за публікації, що стосуються історії Києва. Гроші на започаткування премії дали батьки Романа.)
Click on the "Зберегти" button
Expected result
The new fact is successfully added
Postcondition
Delete the newly created fact
User story:
#123
Related bug:
The precondition was edited, and a postcondition was added to the test case.
| gharchive/issue | 2023-07-07T15:32:48 | 2025-04-01T06:39:09.090435 | {
"authors": [
"DariaAntonenko",
"arisssha"
],
"repo": "ita-social-projects/StreetCode",
"url": "https://github.com/ita-social-projects/StreetCode/issues/356",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
821149389 | As an Admin I want to see Edit button on Material page so that I could change material
As an Admin I want to see Edit button on Material page so that I could change material
Preconditions:
Registered User is logged in
Registered User has Admin role
Admin opened Material page
Button is displayed on every Material Page (Article, Post, Video etc.)
Pressing the button opens the Editing page with prefilled Material content.
Editing page contains all elements of the Creation page and the button «Відмінити редагування».
Instead of «Опублікувати» the user sees «Зберегти і опублікувати». The button functionality does not change.
For Article use page from US #122
For Note use page from US #123
For Video use page from US #124
After pressing the button «Зберегти» user should confirm his decision in modal window. Pressing "Так" saves changes and displays Material page. Pressing "Ні" closes modal window, user stays at the edition page.
After pressing the button «Відмінити редагування» user should confirm his decision in modal window. Pressing "Так" cancels edition and displays original Material page. Pressing "Ні" closes modal window, user stays at the edition page.
Assumption:
The Author and the creating date stay unchanged after saving.
AC:
The User has Admin role
Pressed button opens prefilled Editing Page
The Admin can edit fields «Теми» (Напрямки), «Заголовок», «Текст статті», «Текст картки матеріалу».
Not accepted.
Editing page doesn't have «Зберегти і опублікувати» button.
UI of the editing page is outdated.
A modal window doesn't pop up after pressing the button «Зберегти» , user is redirected to his Material page immediately.
The design of modal window is outdated.
21/07/21
BA check.
Not accepted.
Editing page doesn't have «Зберегти і опублікувати» button.
A modal window doesn't pop up after pressing the button «Зберегти» , user is redirected to his Material page immediately.
UI of the editing page and of modal window are designed from own mockups so some visual details can be changed/polished or are changing/being polished.
| gharchive/issue | 2021-03-03T14:15:34 | 2025-04-01T06:39:09.097802 | {
"authors": [
"go-ann",
"vitaliyhere"
],
"repo": "ita-social-projects/dokazovi-be",
"url": "https://github.com/ita-social-projects/dokazovi-be/issues/193",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1963289980 | Project carousel#71
Description
Created the Carousel section of the home page
Fixes #71
Worked on this issue with @Schola-droid and @https://github.com/AzharAhmed-bot
Type of change
Please delete options that are not relevant.
[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
Screenshot (optional)
Desktop
Tablet
Phone
Checklist
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
Closing the branch as it is already done. This is really good work.
| gharchive/pull-request | 2023-10-26T11:18:09 | 2025-04-01T06:39:09.110201 | {
"authors": [
"JAPHETHNYARANGA",
"paul-nadola"
],
"repo": "italanta/elewa-website-html",
"url": "https://github.com/italanta/elewa-website-html/pull/332",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
275669215 | [6001] descrizioneEsenzioneBollo
buongiorno.
in presenza di motivi di esenzione non codificati, passiamo il <codiceEsenzioneBollo> valorizzato a 99 ed inseriamo nell'xml anche la <descrizioneEsenzioneBollo>, passando quella del gestionale.
è ipotizzabile l'estensione del numero dei caratteri del campo "descrizione"?
attualmente il limite è 256, ma il cliente, in alcuni casi, usa delle modalità che superano i 300 caratteri...
grazie.
Alessandro Monopoli ADS
Possiamo farlo ma non è immediato: faccio presente che il contenuto di questo campo non viene riportato in stampa quindi sono possibili anche abbreviazioni compatibili con il numero di caratteri attualmente previsto
ok. grazie.
allora ricordavo male e mi sembrava che la descrizione venisse poi stampata anche sul certificato.
allora nell'immediato procedo sicuramente con il troncamento della descrizione.
| gharchive/issue | 2017-11-21T11:00:01 | 2025-04-01T06:39:09.112622 | {
"authors": [
"AMonopoliADS",
"gcarbonin"
],
"repo": "italia/anpr",
"url": "https://github.com/italia/anpr/issues/420",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1759499442 | Issuance Chapter (solo PID) (Marino)
https://github.com/italia/eidas-it-wallet-docs/blob/0a918c452512f9b77887b2748b75cffb98579558/docs/en/issuance.rst?plain=1#L1
Done here https://github.com/italia/eidas-it-wallet-docs/pull/28
| gharchive/issue | 2023-06-15T20:23:07 | 2025-04-01T06:39:09.116934 | {
"authors": [
"misillet",
"peppelinux"
],
"repo": "italia/eidas-it-wallet-docs",
"url": "https://github.com/italia/eidas-it-wallet-docs/issues/21",
"license": "CC0-1.0",
"license_type": "permissive",
"license_source": "github-api"
} |
947043400 | adding support for php 8.0 and php-saml 4.0
Salve.
Da quel che ho visto php-saml 3.4.1 è l'unica dipendenza che imponga di utilizzare php 7, ma è già disponibile la versione 4.0 di php-saml che introduce il supporto a php 8.0.
Ho provato ad adattare la patch per nuova versione di php-saml ma al momento del login quando seleziono un identity provider da solo un errore 419 page expired.
Per caso c'è un modo con cui possa ottenere qualche ulteriore informazione riguardo all'erroe per fare debug?
Grazie mille,
Riccardo.
Ciao @Rickrk4,
innanzitutto grazie per il tuo contributo.
Rispetto all'errore non saprei darti molte indicazioni se non un sospetto relativo a qualcosa che non va nel recupero della sessione dopo la request. Se magari metti la patch e le modifiche che hai fatto in una PR, possiamo dare un'occhiata insieme.
In alternativa, anziché continuare con le patch a php-saml, si potrebbe andare nella direzione di integrare https://github.com/italia/spid-php che è un progetto molto più maturo e aggiornato. In questo caso lo sforzo sarebbe quello di sostituire php-saml con spid-php in modo trasparente mantenendo la stessa API attuale di spid-laravel (possiamo valutare poi anche eventuali breaking changes).
Ciao @pdavide, grazie per l'aiuto.
Sto lavorando su un fork del repository https://github.com/Rickrk4/spid-laravel, ho inserito le modifiche nella branch testing, e questa è la patch che ho adattato io https://github.com/Rickrk4/spid-laravel/blob/testing/patches/php-saml-4.0.0-spid.patch .
Se non ho capito male per adesso il progetto più mantenuto sarebbe spid-php, e quindi anche in vista del futuro converrebbe integrarlo nell'api per laravel al posto di php-saml come da te proposto, giusto?
Grazie per
Ciao @Rickrk4, si corretto. Converrebbe passare a spid-php al posto di php-saml.
Ciao @cod3rshotout,
forse @Rickrk4 potrebbe esserti d'aiuto con la soluzione che aveva iniziato a predisporre.
Se poi la soluzione trovata è stabile e testata si potrebbe anche integrarla qui con una PR.
@pdavide Come mai questo progetto non è più aggiornato? È l'unico package spid per laravel ma sembra essere abbandonato
Ciao @cod3rshotout, il progetto non è abbandonato. Semplicemente non ci sono stati molti contributi da parte della community se non la #81 di un paio di settimane fa.
Oggi ho smanettato per un upgrade a Laravel 9 (che richiede PHP 8) e non mi risulta che onelogin/php-saml 3.4.1 abbia una dipendenza stretta a PHP 7.
L'ho provato empiricamente e faccio il login SPID senza particolari problemi.
Certo, l'adozione a spid-php sarebbe ulteriormente preferibile.
Laravel 9/PHP 8 supportati a partire dalla versione 2.0.0-beta.
| gharchive/issue | 2021-07-18T14:10:44 | 2025-04-01T06:39:09.124727 | {
"authors": [
"Rickrk4",
"cod3rshotout",
"madbob",
"pdavide"
],
"repo": "italia/spid-laravel",
"url": "https://github.com/italia/spid-laravel/issues/76",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
309742264 | Validazione Metadata Comune di San Benedetto Pò
Richiesta proveniente dal Comune di San Benedetto Pò
Il Metadata è stato deployato presso gli IdP e da essi caricato.
| gharchive/issue | 2018-03-29T12:51:37 | 2025-04-01T06:39:09.127830 | {
"authors": [
"AntonioGiovanniSchiavone"
],
"repo": "italia/spid",
"url": "https://github.com/italia/spid/issues/151",
"license": "CC0-1.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1136214477 | Add Refactory
Refactory is also full remote, so here's my PR to add it. Thank you!
Thank you for this project!
| gharchive/pull-request | 2022-02-13T17:58:20 | 2025-04-01T06:39:09.128607 | {
"authors": [
"zanardigit"
],
"repo": "italiaremote/awesome-italia-remote",
"url": "https://github.com/italiaremote/awesome-italia-remote/pull/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
836917688 | Ubisys S2 (also applies to S1)
Device description
I'd like to have the Ubisys S2 switch supported. It is a mains-powered, wall mounted, two-channel switch for loads, e.g. lights. Same goes for the S1 (difference: s2 is two channel, s1 is one channel, they produce the same error message)
Manufacturer website
Supported in Zigbee2MQTT?
The device is supported in Zigbee2MQTT. Same goes for S1. Interestingly the Ubisys D1 works flawlessly.
I am on the latest dev version, but I assume support for these has been around a while.
Device model / Exposes information
{
"date_code": "20191127-DE-FB0",
"definition": {
"description": "Power switch S2",
"exposes": [
{
"endpoint": "l1",
"features": [
{
"access": 7,
"description": "On/off state of the switch",
"endpoint": "l1",
"name": "state",
"property": "state_l1",
"type": "binary",
"value_off": "OFF",
"value_on": "ON",
"value_toggle": "TOGGLE"
}
],
"type": "switch"
},
{
"endpoint": "l2",
"features": [
{
"access": 7,
"description": "On/off state of the switch",
"endpoint": "l2",
"name": "state",
"property": "state_l2",
"type": "binary",
"value_off": "OFF",
"value_on": "ON",
"value_toggle": "TOGGLE"
}
],
"type": "switch"
},
{
"access": 5,
"description": "Instantaneous measured power",
"endpoint": "meter",
"name": "power",
"property": "power",
"type": "numeric",
"unit": "W"
},
{
"access": 1,
"description": "Triggered action (e.g. a button click)",
"name": "action",
"property": "action",
"type": "enum",
"values": [
"toggle_s1",
"toggle_s2",
"on_s1",
"on_s2",
"off_s1",
"off_s2",
"recall_*_s1",
"recal_*_s2",
"brightness_move_up_s1",
"brightness_move_up_s2",
"brightness_move_down_s1",
"brightness_move_down_s2",
"brightness_stop_s1",
"brightness_stop_s2"
]
},
{
"access": 1,
"description": "Link quality (signal strength)",
"name": "linkquality",
"property": "linkquality",
"type": "numeric",
"unit": "lqi",
"value_max": 255,
"value_min": 0
}
],
"model": "S2",
"supports_ota": true,
"vendor": "Ubisys"
},
"endpoints": {
"1": {
"bindings": [
{
"cluster": "genOnOff",
"target": {
"endpoint": 1,
"ieee_address": "0x00124b0021b7788c",
"type": "endpoint"
}
}
],
"clusters": {
"input": [
"genBasic",
"genIdentify",
"genGroups",
"genScenes",
"genOnOff"
],
"output": []
},
"configured_reportings": [
{
"attribute": "onOff",
"cluster": "genOnOff",
"maximum_report_interval": 300,
"minimum_report_interval": 0,
"reportable_change": 0
}
]
},
"2": {
"bindings": [
{
"cluster": "genOnOff",
"target": {
"endpoint": 1,
"ieee_address": "0x00124b0021b7788c",
"type": "endpoint"
}
}
],
"clusters": {
"input": [
"genBasic",
"genIdentify",
"genGroups",
"genScenes",
"genOnOff"
],
"output": []
},
"configured_reportings": [
{
"attribute": "onOff",
"cluster": "genOnOff",
"maximum_report_interval": 300,
"minimum_report_interval": 0,
"reportable_change": 0
}
]
},
"3": {
"bindings": [
{
"cluster": "genOnOff",
"target": {
"endpoint": 1,
"ieee_address": "0x001fee00000058d9",
"type": "endpoint"
}
}
],
"clusters": {
"input": [
"genBasic",
"genIdentify"
],
"output": [
"genScenes",
"genOnOff",
"genLevelCtrl"
]
},
"configured_reportings": []
},
"4": {
"bindings": [
{
"cluster": "genOnOff",
"target": {
"endpoint": 2,
"ieee_address": "0x001fee00000058d9",
"type": "endpoint"
}
}
],
"clusters": {
"input": [
"genBasic",
"genIdentify"
],
"output": [
"genScenes",
"genOnOff",
"genLevelCtrl"
]
},
"configured_reportings": []
},
"5": {
"bindings": [
{
"cluster": "seMetering",
"target": {
"endpoint": 1,
"ieee_address": "0x00124b0021b7788c",
"type": "endpoint"
}
}
],
"clusters": {
"input": [
"genBasic",
"seMetering",
"haElectricalMeasurement"
],
"output": []
},
"configured_reportings": [
{
"attribute": "instantaneousDemand",
"cluster": "seMetering",
"maximum_report_interval": 3600,
"minimum_report_interval": 5,
"reportable_change": 1
}
]
},
"200": {
"bindings": [],
"clusters": {
"input": [],
"output": []
},
"configured_reportings": []
},
"232": {
"bindings": [],
"clusters": {
"input": [
"genBasic",
"genCommissioning",
"manuSpecificUbisysDeviceSetup"
],
"output": [
"genIdentify",
"genOta"
]
},
"configured_reportings": []
},
"242": {
"bindings": [],
"clusters": {
"input": [
"greenPower"
],
"output": [
"greenPower"
]
},
"configured_reportings": []
}
},
"friendly_name": "KuecheWand",
"ieee_address": "0x001fee00000058d9",
"interview_completed": true,
"interviewing": false,
"model_id": "S2 (5502)",
"network_address": 38227,
"power_source": "Mains (single phase)",
"supported": true,
"type": "Router"
}
Missing features/functionality
This device is currently not exposed at all, as it throws an error at start up
[3/20/2021, 10:17:03 PM] [zigbee2mqtt] Failed to setup stateless programmable switch for accessory KuecheWand from expose "{"access":1,"description":"Triggered action (e.g. a button click)","name":"action","property":"action","type":"enum","values":["toggle_s1","toggle_s2","on_s1","on_s2","off_s1","off_s2","recall_*_s1","recal_*_s2","brightness_move_up_s1","brightness_move_up_s2","brightness_move_down_s1","brightness_move_down_s2","brightness_stop_s1","brightness_stop_s2"]}", error: Error: Device found with a wildcard in the exposed possible values for the action, which cannot be mapped: recall_*_s1
Expected functionality: a simple lamp on/off (homekit Lightbulb)
I guess the problem stems from the "recall_*_s1" attribute, which I dont think is needed and can be ignored
Suggested services and characteristics
For end points l1 and l2, I would expect a homekit Lightbulb
As it's a switch, it should show up as a Switch in HomeKit (which is also what the plugin website indicates).
This Switch service can be configured in HomeKit to be interpreted as a light, if that is what you have connected to it.
The error you are seeing is because it also exposes an action, but it contains wildcard values which the plugin can't handle.
This should however not influence the creation of the Switch service, but only means that it will not have a Stateless Programmable Switch service to expose the action enum to HomeKit.
If you also want to stateless programmable switch to be present you can either add the wildcard values to the ignore list in the of the homebridge-z2m plugin (see this page for some more info), or you can figure out all the valid values and open a PR for Koenkk/zigbee-herdsman-converters to improve the exposes information.
I'll try to create a unit test from the information you've provided, if you are sure that the Switch services are not being exposed.
I've just added some automated tests and as far as I can tell, two Switch services are being created for this device, as I would expect based on the exposes information you've shared.
Can you please provide the entire log of the startup of Homebridge (with the debug option) enabled?
Thanks a lot!
I have now deleted all services in HomeKit and set it up again ... and now it shows the switch!
(I dont know what happened -- I don't think overlooked it the first time -- but no guarantee).
Thanks anyways ... it now works!
| gharchive/issue | 2021-03-20T21:45:46 | 2025-04-01T06:39:09.142685 | {
"authors": [
"itavero",
"jhm47"
],
"repo": "itavero/homebridge-z2m",
"url": "https://github.com/itavero/homebridge-z2m/issues/117",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2485601969 | PDF example - out of Index
We need safeguards, like we had in the pdf-datachain-demo (can be done in a cleaner way though).
Otherwise we are getting this on CI:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.5/x64/lib/python3.12/site-packages/datachain/lib/udf.py", line 257, in <genexpr>
res = (
^
File "/home/runner/work/datachain-examples/datachain-examples/llm/pdf-processing/pdf-processing.py", line 39, in process_pdf
chunks_embedded = embedding_encoder.embed_documents(chunks)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.5/x64/lib/python3.12/site-packages/unstructured/embed/huggingface.py", line 57, in embed_documents
embeddings = self.client.embed_documents([str(e) for e in elements])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.5/x64/lib/python3.12/site-packages/langchain_huggingface/embeddings/huggingface.py", line 87, in embed_documents
embeddings = self.client.encode(
^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.5/x64/lib/python3.12/site-packages/sentence_transformers/SentenceTransformer.py", line 565, in encode
if all_embeddings[0].dtype == torch.bfloat16:
~~~~~~~~~~~~~~^^^
IndexError: list index out of range
(keep this in mind when we are consolidating this with datachain example)
Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."
Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."
Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."
@tibor-mach are you looking into this? before publishing the blog post- I think we need this to be addressed, wdyt?
| gharchive/issue | 2024-08-26T00:51:46 | 2025-04-01T06:39:09.156137 | {
"authors": [
"GendiAstaNugraha",
"Wanderx13",
"llowvxe",
"shcheklein"
],
"repo": "iterative/datachain-examples",
"url": "https://github.com/iterative/datachain-examples/issues/11",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1476597358 | Adds missing word in to metrics get started tutorial
You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.
❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏
thanks @JulianoLagana !
| gharchive/pull-request | 2022-12-05T13:43:02 | 2025-04-01T06:39:09.162543 | {
"authors": [
"JulianoLagana",
"shcheklein"
],
"repo": "iterative/dvc.org",
"url": "https://github.com/iterative/dvc.org/pull/4160",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1663729487 | Error with relative imports during saving model with mlem
I'm trying to save wav2vec2 model from fairseq, but it seems that there's a bug in handling requirements with relative imports.
Versions
mlem==0.4.10
fairseq==0.12.2
Followings are the codes and the error log.
# Clone and install fairseq
git clone git@github.com:facebookresearch/fairseq.git
cd fairseq
pip install -e .
You can download checkpoints from here
Python script for saving wav2vec2
from mlem.api import load, save
import fairseq
if __name__ == "__main__":
wav2vec_ckpt_path = (
"/Downloads/ckpts/wav2vec/xlsr2_300m.pt"
)
# Load Wav2Vec
wav2vec, _, _ = fairseq.checkpoint_utils.load_model_ensemble_and_task(
[wav2vec_ckpt_path]
)
wav2vec = wav2vec[0]
# Save
save(wav2vec, "wav2vec")
Error log
Traceback (most recent call last):
File "debug.py", line 18, in <module>
save(wav2vec, "wav2vec")
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/telemetry.py", line 50, in inner
return f(*args, **kwargs)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/core/metadata.py", line 122, in save
meta = get_object_metadata(
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/core/metadata.py", line 53, in get_object_metadata
return MlemModel.from_obj(
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/core/objects.py", line 792, in from_obj
mlem_model.add_processor(MAIN_PROCESSOR_NAME, mt)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/core/objects.py", line 816, in add_processor
self.requirements += model_type.get_requirements().expanded
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/contrib/torch.py", line 229, in get_requirements
return super().get_requirements() + InstallableRequirement.from_module(
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/core/model.py", line 341, in get_requirements
) + get_object_requirements(self.model)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 643, in get_object_requirements
a.dump(obj)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/dill/_dill.py", line 394, in dump
StockPickler.dump(self, obj)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/pickle.py", line 487, in dump
self.save(obj)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 612, in save
self.add_requirement(obj)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 591, in add_requirement
self.add_requirement(local_req)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 591, in add_requirement
self.add_requirement(local_req)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 591, in add_requirement
self.add_requirement(local_req)
[Previous line repeated 1 more time]
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 599, in add_requirement
self.add_requirement(parent_package)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 591, in add_requirement
self.add_requirement(local_req)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 588, in add_requirement
for local_req in get_local_module_reqs(module):
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 355, in get_local_module_reqs
result = [importing.import_module(i, p) for i, p in imports]
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/utils/module.py", line 355, in <listcomp>
result = [importing.import_module(i, p) for i, p in imports]
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 655, in _load_unlocked
File "<frozen importlib._bootstrap>", line 618, in _load_backward_compatible
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/site-packages/mlem/ext.py", line 265, in load_module
module = importlib.import_module(fullname)
File "/home/wis/anaconda3/envs/superhub_debug/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'fairseq.data.audio.data_utils'
As shown in the error log, mlem tries to find fairseq.data.audio.data_utils. But as you can see here there's no data_utils under fairseq.data.audio.
I'm assuming that mlem is not handling properly with relative imports from this part.
It should import module fairseq.data.data_utils not the fairseq.data.audio.data_utils.
Nice catch @wiswisbus! Would you like to investigate this and make a PR fixing this issue? I can help with reviewing and merging :)
I also wonder if this happens with pip install -e . only, or pip install github.com:facebookresearch/fairseq.git (or whatever is the correct way to install it right from git) would work correctly.
I was taking a look into this and there are two points:
Doing pip install . (removing -e editable) or pip install git+https or pip install fairseq solves the issues.
I have prepared a fix, but specifically for fairseq it won't solve the issue because the project is using a vendored submodule megatron: https://github.com/facebookresearch/fairseq/tree/main/fairseq/model_parallel.
So is it worth the fix?
@aminalaee I think the fix always worth it, don't hesitate to make a PR - especially if you already implemented it!
Re megatron - I hope we can resolve that as well, since the version (commit) is pinned there. Once you make a PR I think I can TAL and see if I have any good ideas.
@aminalaee, I'm having problems with reproducing issue with megatron. Could you please post a traceback so I could see what fails exactly?
@aguschin
Here it is:
Traceback (most recent call last):
File "/path//mlem/example.py", line 18, in <module>
save(wav2vec, "wav2vec")
File "/path//mlem/mlem/telemetry.py", line 50, in inner
return f(*args, **kwargs)
File "/path//mlem/mlem/core/metadata.py", line 122, in save
meta = get_object_metadata(
File "/path//mlem/mlem/core/metadata.py", line 53, in get_object_metadata
return MlemModel.from_obj(
File "/path//mlem/mlem/core/objects.py", line 792, in from_obj
mlem_model.add_processor(MAIN_PROCESSOR_NAME, mt)
File "/path//mlem/mlem/core/objects.py", line 816, in add_processor
self.requirements += model_type.get_requirements().expanded
File "/path//mlem/mlem/contrib/torch.py", line 229, in get_requirements
return super().get_requirements() + InstallableRequirement.from_module(
File "/path//mlem/mlem/core/model.py", line 341, in get_requirements
) + get_object_requirements(self.model)
File "/path//mlem/mlem/utils/module.py", line 648, in get_object_requirements
return a.to_requirements()
File "/path//mlem/mlem/utils/module.py", line 553, in to_requirements
r.add(CustomRequirement.from_module(mod))
File "/path//mlem/mlem/core/requirements.py", line 236, in from_module
raise ValueError(f"{mod} does not have __file__ attr")
ValueError: <module 'fairseq.model_parallel.megatron' (<_frozen_importlib_external._NamespaceLoader object at 0x7f3695152830>)> does not have __file__ attr
This was result of installing fairseq with pip install -e . and then running the save method in the issue example.
Hmm. I assume this doesn't happen when doing pip install fairseq?
Yeah, it works well with pip install fairseq
Ok, not sure how this can be fixed right now. @aminalaee, do you have any workaround in mind?
I also have 2 questions:
@wiswisbus is this something that blocks your workflow? Do you absolutely need to install it with -e?
@aminalaee would you like to contribute to this particular issue? Or you're just looking for something to contribute? There are a lot of good issues we can check out.
Yeah @aguschin I'll be happy to contribute to any issue that can help the project. Nothing specific really.
Thank you! @aguschin @aminalaee
I can work without installing package as editable mode. It might be better if it works with editable mode but it's not mandatory. Just didn't know that it only happens with editable mode. Thank you all again for the rapid response!
Good to hear! Thank you @wiswisbus :)
| gharchive/issue | 2023-04-12T04:27:38 | 2025-04-01T06:39:09.198492 | {
"authors": [
"aguschin",
"aminalaee",
"wiswisbus"
],
"repo": "iterative/mlem",
"url": "https://github.com/iterative/mlem/issues/650",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
924219814 | Create a common internal abstraction over every vendor
Follow-up of https://github.com/iterative/terraform-provider-iterative/pull/143#discussion_r653823205
Ideally we should write something like:
var provider Provider
switch cloud {
case "aws":
provider = aws
case "azure":
provider = azure
}
regions := provider.ImageRegions
cloudRegion := provider.GetRegion(region)
for _, item := range regions {
if item == cloudRegion {
return true
}
}
return false
The actionable requirement would be creating an interface over vendors.
Closed with #237
| gharchive/issue | 2021-06-17T18:32:06 | 2025-04-01T06:39:09.201493 | {
"authors": [
"0x2b3bfa0"
],
"repo": "iterative/terraform-provider-iterative",
"url": "https://github.com/iterative/terraform-provider-iterative/issues/147",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1428999404 | Share experiment fails if no remote specified in repo
If remote storage is not specified:
[version: 0.5.7, 2022-10-30T19:57:04.192Z, pid: 65281] > /Users/ivan/Projects/ensemble-dvc-template/.venv/bin/python -m dvc push - FAILED with code 1 (236ms)
[31mERROR[39m: failed to push data to the cloud - config file error: no remote specified. Create a default remote with
dvc remote add -d <remote name> <remote url>
while trying to "Share as Branch"
Extension: v0.5.7
DVC:
DVC version: 2.32.0 (pip)
---------------------------------
Platform: Python 3.9.13 on macOS-12.6-arm64-arm-64bit
Subprojects:
dvc_data = 0.22.0
dvc_objects = 0.11.0
dvc_render = 0.0.12
dvc_task = 0.1.4
dvclive = 0.12.1.dev8+g243ae28.d20221030
scmrepo = 0.1.2
Supports:
http (aiohttp = 3.8.3, aiohttp-retry = 2.8.3),
https (aiohttp = 3.8.3, aiohttp-retry = 2.8.3)
Cache types: reflink, hardlink, symlink
Cache directory: apfs on /dev/disk3s1s1
Caches: local
Remotes: None
Workspace directory: apfs on /dev/disk3s1s1
Repo: dvc, git
We can include also better handing of any remote / Git errors during the process. Dmitry's feedback was about this as well.
| gharchive/issue | 2022-10-30T20:00:37 | 2025-04-01T06:39:09.203374 | {
"authors": [
"shcheklein"
],
"repo": "iterative/vscode-dvc",
"url": "https://github.com/iterative/vscode-dvc/issues/2700",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
928026975 | metadata v14
https://github.com/paritytech/substrate/pull/8615
https://github.com/polkadot-js/api/pull/3827/files
https://github.com/polkadot-js/api/pull/3899
https://github.com/polkadot-js/api/pull/3920/files
https://github.com/polkadot-js/api/pull/3987#issuecomment-926489040
| gharchive/issue | 2021-06-23T09:02:27 | 2025-04-01T06:39:09.205747 | {
"authors": [
"freehere107"
],
"repo": "itering/scale.go",
"url": "https://github.com/itering/scale.go/issues/32",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
351444010 | The index out of range exception has been thrown when I try to build the whole US router db.
Hi,
I'm working on building the whole US router db. I try to get the router db file with two approaches but it works fail:
Use the whole US data with one North America .pbf (7.8G).
I have download the North America data from https://download.geofabrik.de/ . I try to build the router db with following statements:
`var usPbfFile = @"C:\Test\north-america-latest.osm.pbf";
using (var stream = File.OpenRead(usPbfFile))
{
var osmStream = new OsmSharp.Streams.PBFOsmStreamSource(stream);
var routerDb = new RouterDb();
routerDb.LoadOsmData(osmStream);
if (!routerDb.HasContractedFor(vehicle.Fastest()))
{
Itinero.Logging.Logger.Log("RouterDbBuilder", Itinero.Logging.TraceEventType.Information, "No contracted graph found for the 'car' profile, building now...");
routerDb.AddContracted(vehicle.Fastest(), true);
}
using (var writeStream = File.Open(routerDbFileName, FileMode.Create))
{
routerDb.Serialize(writeStream);
}
}
`
It works failed and throws an index out of range exception when the router db calculating progress is 97% as the attached
Use the divided state .pbf files.
I have downloaded all of .pbf files in America, and build them into one router db file as following statements:
`
public static RouterDb Build(string sourceDbFolder, string targetDbFilename, Vehicle vehicle)
{
RouterDb routerDb = null;
var routerDbFileName = targetDbFilename;
if (File.Exists(routerDbFileName))
{
try
{
using (var stream = File.OpenRead(routerDbFileName))
{
routerDb = RouterDb.Deserialize(stream);
}
}
catch
{
routerDb = null;
}
}
if (routerDb == null)
{
// check if OSM pbf file is there.
var files = Directory.GetFiles(sourceDbFolder);
if (files == null || files.Length <= 0)
{ // check if OSM file is there, otherwise attempt to download from overpass.
throw new Exception("The .pbf file is not exist.");
}
// build routerdb.
Itinero.Logging.Logger.Log("RouterDbBuilder", Itinero.Logging.TraceEventType.Information, "No existing RouterDb file found, creating now.");
var osmFiles = new List<OsmStreamSource>();
var fileStreams = new List<Stream>();
foreach (var file in files)
{
OsmStreamSource osmStream = null;
var stream = File.OpenRead(file);
fileStreams.Add(stream);
if (file.EndsWith(".osm.pbf"))
{
osmStream = new OsmSharp.Streams.PBFOsmStreamSource(stream);
}
else
{
osmStream = new OsmSharp.Streams.XmlOsmStreamSource(stream);
}
osmFiles.Add(osmStream);
}
routerDb = new RouterDb();
routerDb.LoadOsmData(osmFiles.ToArray(), vehicle);
foreach (var stream in fileStreams)
{
stream.Close();
stream.Dispose();
}
Itinero.Logging.Logger.Log("RouterDbBuilder", Itinero.Logging.TraceEventType.Information, "RouterDb file created.");
if (!routerDb.HasContractedFor(vehicle.Fastest()))
{
Itinero.Logging.Logger.Log("RouterDbBuilder", Itinero.Logging.TraceEventType.Information, "No contracted graph found for the 'car' profile, building now...");
routerDb.AddContracted(vehicle.Fastest(), true);
}
using (var stream = File.Open(routerDbFileName, FileMode.Create))
{
routerDb.Serialize(stream);
}
}
return routerDb;
}
`
It works failed and throws an index out of range exception when the router db is being written with a result data as the attached file:
I don't know how to fix this issue. I'm very appreciate for your any help.
My computer configuration:
RAM: 32G,
CPU: Core i7 4790
OS: Win10 X64
Application: 64 bit.
Did you try this using the latest prerelease? We're focusing on getting that released.
I tested building the north-america routerdb and that worked, now testing the contraction...
Hi xivk,
Thanks for your help, I'm working on the version v1.4.0-pre67. As the above statements, a "Car fastest" contraction has been added to RouterDb:
routerDb.AddContracted(vehicle.Fastest(), true);
This exception has been thrown when the router db is written to file with the "Car fastest" contraction. The thrown point is located on the "Compress" method in "DirectedGraph.cs".
If you have any updates, please tell me know. I'm very appreciate for your help.
Hi xivk,
I'm testing routing contraction with the latest development branch source code. As above issue, I have tried to build the whole US routing data with all of states .pbf data. It seems the out of range exception was thrown by Router db serialize progress. You can see the exception is thrown when the percent of the progress is 99%, the router db is being written to the disk.
| gharchive/issue | 2018-08-17T03:23:20 | 2025-04-01T06:39:09.285044 | {
"authors": [
"Casper-ThinkGeo",
"xivk"
],
"repo": "itinero/routing",
"url": "https://github.com/itinero/routing/issues/214",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
2177768519 | TFLite converter effecientnet-b0 error
Пытаюсь конвертировать TF модель efficientnet-b0 из OpenModelZoo. tflite_converter.py выдает ошибку с неподдерживаемым слоем __inference_swish_f32_730.
Пробовал с разными tensorflow, последний раз с tensorflow==2.12.0 и tensorflow-addons==0.19 tensorflow-estimator==2.12.0 tensorflow-probability==0.19
Строка конвертации:
python tflite_converter.py --model-path /home/vasiliev/_dev/itlab/public/efficientnet-b0/efficientnet-b0/saved_model --input-names sub --input-shapes [1,224,224,3] --source-framework tf --output-names logits
Вывод скрипта с ошибкой (часть, полный вывод по ссылке: https://gist.github.com/FenixFly/3c523abc679934a7df6b67ad006c7ad6 ):
[ INFO ] Loading TF model
[ INFO ] Loading saved model from /home/vasiliev/_dev/itlab/public/efficientnet-b0/efficientnet-b0/saved_model
2024-03-10 12:27:35.194661: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:996] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-03-10 12:27:35.194910: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1956] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
INFO:tensorflow:Saver not created because there are no variables in the graph to restore
[ INFO ] Saver not created because there are no variables in the graph to restore
[ INFO ] Setting input shapes to ([1, 224, 224, 3],)
[ INFO ] Converting to tflite
[ WARNING ] Please consider providing the trackable_obj argument in the from_concrete_functions. Providing without the trackable_obj argument is deprecated and it will use the deprecated conversion path.
2024-03-10 12:27:35.778469: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:996] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2024-03-10 12:27:35.778594: I tensorflow/core/grappler/devices.cc:66] Number of eligible GPUs (core count >= 8, compute capability >= 0.0): 1
loc(fused["__inference_swish_f32_73:", callsite("efficientnet-b0/model/blocks_4/se/swish_f32"("/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py":985:0) at callsite("/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py":836:0 at callsite("/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py":12:0 at callsite("/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py":142:0 at callsite("/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py":164:0 at "/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py":176:0)))))]): error: 'tf.LegacyCall' op is neither a custom op nor a flex op
loc(fused["__inference_swish_f32_73:", callsite("efficientnet-b0/model/head/swish_f32"("/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py":985:0) at callsite("/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py":836:0 at callsite("/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py":12:0 at callsite("/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py":142:0 at callsite("/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py":164:0 at "/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py":176:0)))))]): error: 'tf.LegacyCall' op is neither a custom op nor a flex op
2024-03-10 12:27:36.605790: W tensorflow/compiler/mlir/lite/flatbuffer_export.cc:2051] TFLite interpreter needs to link Flex delegate in order to run the model since it contains the following Select TFop(s):
Flex ops: FlexConv2D, FlexDepthwiseConv2dNative
Details:
tf.Conv2D(tensor<*xf32>, tensor<1x1x10x240xf32>) -> (tensor<?x?x?x240xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x1152x192xf32>) -> (tensor<?x?x?x192xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x1152x320xf32>) -> (tensor<?x?x?x320xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x1152x48xf32>) -> (tensor<?x?x?x48xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x144x24xf32>) -> (tensor<?x?x?x24xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x144x40xf32>) -> (tensor<?x?x?x40xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x144x6xf32>) -> (tensor<?x?x?x6xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x20x480xf32>) -> (tensor<?x?x?x480xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x240x10xf32>) -> (tensor<?x?x?x10xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x240x40xf32>) -> (tensor<?x?x?x40xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x240x80xf32>) -> (tensor<?x?x?x80xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x28x672xf32>) -> (tensor<?x?x?x672xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x32x16xf32>) -> (tensor<?x?x?x16xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x32x8xf32>) -> (tensor<?x?x?x8xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x480x112xf32>) -> (tensor<?x?x?x112xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x480x20xf32>) -> (tensor<?x?x?x20xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x480x80xf32>) -> (tensor<?x?x?x80xf32>) : {data_format = "NHWC", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.Conv2D(tensor<*xf32>, tensor<1x1x48x1152xf32>) -> (tensor<?x?x?x1152xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1], use_cudnn_on_gpu = true}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<3x3x96x1xf32>) -> (tensor<?x?x?x96xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 2, 2, 1]}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<5x5x1152x1xf32>) -> (tensor<?x?x?x1152xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1]}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<5x5x144x1xf32>) -> (tensor<?x?x?x144xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 2, 2, 1]}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<5x5x240x1xf32>) -> (tensor<?x?x?x240xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1]}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<5x5x480x1xf32>) -> (tensor<?x?x?x480xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1]}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<5x5x672x1xf32>) -> (tensor<?x?x?x672xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 1, 1, 1]}
tf.DepthwiseConv2dNative(tensor<*xf32>, tensor<5x5x672x1xf32>) -> (tensor<?x?x?x672xf32>) : {data_format = "NHWC", device = "", dilations = [1, 1, 1, 1], explicit_paddings = [], padding = "SAME", strides = [1, 2, 2, 1]}
See instructions: https://www.tensorflow.org/lite/guide/ops_select
error: failed while converting: 'main':
Some ops in the model are custom ops, See instructions to implement custom ops: https://www.tensorflow.org/lite/guide/ops_custom
Custom ops: __inference_swish_f32_730
Details:
tf.LegacyCall(tensor<1x112x112x32xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x10xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x1152xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x1280xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x144xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x20xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x240xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x28xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x32xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x480xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x48xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x4xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x672xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x6xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x8xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x96xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
Traceback (most recent call last):
File "/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py", line 176, in <module>
main()
File "/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py", line 172, in main
convert_to_tflite(model, output_file)
File "/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py", line 85, in convert_to_tflite
tflite_model = converter.convert()
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/lite.py", line 1897, in convert
return super(TFLiteConverterV2, self).convert()
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/lite.py", line 962, in wrapper
return self._convert_and_export_metrics(convert_func, *args, **kwargs)
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/lite.py", line 940, in _convert_and_export_metrics
result = convert_func(self, *args, **kwargs)
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/lite.py", line 1546, in convert
return super(TFLiteFrozenGraphConverterV2,
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/lite.py", line 1166, in convert
result = _convert_graphdef(
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/convert_phase.py", line 212, in wrapper
raise converter_error from None # Re-throws the exception.
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/convert_phase.py", line 205, in wrapper
return func(*args, **kwargs)
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/convert.py", line 817, in convert_graphdef
data = convert(
File "/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/lite/python/convert.py", line 322, in convert
raise converter_error
tensorflow.lite.python.convert_phase.ConverterError: /home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: error: 'tf.LegacyCall' op is neither a custom op nor a flex op
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:836:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:12:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tensorflow_common.py:142:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:164:0: note: called from
/home/vasiliev/_dev/itlab/dl-benchmark-vasilev/src/model_converters/tf2tflite/tflite_converter.py:176:0: note: called from
/home/vasiliev/miniconda3/envs/vino/lib/python3.9/site-packages/tensorflow/python/saved_model/load.py:985:0: note: Error code: ERROR_NEEDS_CUSTOM_OPS
<unknown>:0: error: failed while converting: 'main':
Some ops in the model are custom ops, See instructions to implement custom ops: https://www.tensorflow.org/lite/guide/ops_custom
Custom ops: __inference_swish_f32_730
Details:
tf.LegacyCall(tensor<1x112x112x32xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x10xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x1152xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x1280xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x144xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x20xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x240xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x28xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x32xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x480xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x48xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x4xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x672xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x6xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x8xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
tf.LegacyCall(tensor<?x?x?x96xf32>) -> (tensor<*xf32>) : {_disable_call_shape_inference = true, device = "", tfg.legacy_call = @__inference_swish_f32_730}
@n-berezina-nn Наталья, не могли бы вы помочь разобраться почему модель efficientnet-b0 из OpenModelZoo не конвертируется в формат tflite?
@n-berezina-nn, @FenixFly, сконвертировала модель с использованием следующего скрипта:
import tensorflow as tf
converter = tf.lite.TFLiteConverter.from_saved_model('./efficientnet-b0/saved_model/')
converter.target_spec.supported_ops = [
tf.lite.OpsSet.TFLITE_BUILTINS, tf.lite.OpsSet.SELECT_TF_OPS
]
converter.allow_custom_ops=True
tflite_model = converter.convert()
with open('model.tflite', 'wb') as f:
f.write(tflite_model)
Запускаю вывод средствами вот такой командной строки:
python3 ./inference_tensorflowlite.py -m ./efficientnet-b0/model.tflite -i ./data/ -b 1 -t classification --output_names logits -l ./labels/image_net_synset.txt --input_names sub[1,224,224,3]
Получаю следующий вывод:
2024-03-20 22:07:52.309100: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-03-20 22:07:52.309335: I external/local_tsl/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-03-20 22:07:52.311233: I external/local_tsl/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-03-20 22:07:52.334658: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-03-20 22:07:52.738092: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
[ INFO ] Loading network files:
/home/itmm/Documents/kustikova_v/public/efficientnet-b0/efficientnet-b0/model.tflite
INFO: Created TensorFlow Lite delegate for select TF ops.
INFO: TfLiteFlexDelegate delegate: 64 nodes delegated out of 270 nodes with 64 partitions.
2024-03-20 22:07:52.998300: E tensorflow/core/framework/node_def_util.cc:676] NodeDef mentions attribute use_inter_op_parallelism which is not in the op definition: Op<name=DepthwiseConv2dNative; signature=input:T, filter:T -> output:T; attr=T:type,allowed=[DT_HALF, DT_BFLOAT16, DT_FLOAT, DT_DOUBLE]; attr=strides:list(int); attr=padding:string,allowed=["SAME", "VALID", "EXPLICIT"]; attr=explicit_paddings:list(int),default=[]; attr=data_format:string,default="NHWC",allowed=["NHWC", "NCHW"]; attr=dilations:list(int),default=[1, 1, 1, 1]> This may be expected if your graph generating binary is newer than this binary. Unknown attributes will be ignored. NodeDef: {{node DepthwiseConv2dNative}}
[ INFO ] Shape for input layer sub:0: 1x224x224x3
[ INFO ] Preparing input data: ['/home/itmm/Documents/kustikova_v/data/']
[ INFO ] Starting inference (1 iterations)
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
[ ERROR ] Traceback (most recent call last):
File "/home/itmm/Documents/kustikova_v/upstream/dl-benchmark/src/inference/./inference_tensorflowlite.py", line 286, in main
result, inference_time = inference_tflite(interpreter, args.number_iter, io.get_slice_input, args.time)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/itmm/Documents/kustikova_v/upstream/dl-benchmark/src/inference/./inference_tensorflowlite.py", line 191, in inference_tflite
interpreter.allocate_tensors()
File "/home/itmm/miniconda/envs/tflite_converter_env/lib/python3.11/site-packages/tensorflow/lite/python/interpreter.py", line 531, in allocate_tensors
return self._interpreter.AllocateTensors()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Encountered unresolved custom op: swish_f320.
See instructions: https://www.tensorflow.org/lite/guide/ops_custom Node number 2 (swish_f320) failed to prepare.Encountered unresolved custom op: swish_f320.
See instructions: https://www.tensorflow.org/lite/guide/ops_custom Node number 2 (swish_f320) failed to prepare.
Если все правильно понимаю, то это означает, что конвертер посчитал, что оператор swich_f320 относится к числу кастомных, и реализация должна быть передана через делегат при запуске инференса, но стандартные делегаты не содержат его реализации.
@FenixFly, @n-berezina-nn, сравнила через netron модель из OMZ в формате saved_model, которую мы хотим сконвертировать, и присланную модель в формате tflite. В модели OMZ есть явный слой swish_f32 (схема ниже), в присланной модели таких преобразований вообще нет. Это означает, что либо для конвертации использована другая модель, либо эту модель как-то преобразовывали перед тем, как сконвертировать.
| gharchive/issue | 2024-03-10T15:23:23 | 2025-04-01T06:39:09.319588 | {
"authors": [
"FenixFly",
"valentina-kustikova"
],
"repo": "itlab-vision/dl-benchmark",
"url": "https://github.com/itlab-vision/dl-benchmark/issues/511",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1338295874 | Helper script detected by AMSI when building
When building the script, the file src\02_Helpers.ps1 is blocked by AMSI.
C:\PATH\TO\PrivescCheck>powershell -ep bypass -c ".\Build.ps1"
[OK] Loaded module file 00_Main.ps1
[OK] Loaded module file 01_Win32.ps1
[KO] Failed to load module file 02_Helpers.ps1
[ERROR] At C:\_WORKSPACE\PrivescCheck\src\02_Helpers.ps1:1 char:1
+ function Test-IsRunningInConsole {
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This script contains malicious content and has been blocked by your antivirus software.
[OK] Loaded module file 03_User.ps1
[OK] Loaded module file 04_Services.ps1
[OK] Loaded module file 05_Applications.ps1
[OK] Loaded module file 06_ScheduledTasks.ps1
[OK] Loaded module file 07_Hardening.ps1
[OK] Loaded module file 08_Config.ps1
[OK] Loaded module file 09_Network.ps1
[OK] Loaded module file 10_Updates.ps1
[OK] Loaded module file 11_Credentials.ps1
[OK] Loaded module file 99_Misc.ps1
This can be worked around by disabling "Windows Security" during build, but it would be nice to improve the Builder script in order to bypass detection earlier in the process.
Slightly modified the Builder script.
Instead of trying to load each script, and then removing the comments, I remove the comments first, and then I try to load the resulting code block.
In addition to the comment blocks, I also remove comment lines. Another benefit is that this reduces the size of the final file even more.
That's it. Apparently, this does the trick because the script is no longer caught by AMSI. :partying_face:
| gharchive/issue | 2022-08-14T16:42:58 | 2025-04-01T06:39:09.324552 | {
"authors": [
"itm4n"
],
"repo": "itm4n/PrivescCheck",
"url": "https://github.com/itm4n/PrivescCheck/issues/37",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
1059485512 | minecraft-server:java8 tag no longer starts with forge modpack
Describe the problem
Haven't started this server up in few weeks, today I pulled latest :java8 image and it won't extract the modpack. It prints out 1 error on 1st launch, and then more on 2nd launch. The modpack .zip nor docker-compose.yml have not changed since last successful run of the server.
edit: For what it's worth a similarly set up fabric modpack running on latest itzg/minecraft-server tag runs ok.
Container definition
version: '3'
services:
mc_rlcraft:
ports:
- "25565:25565"
environment:
EULA: "true"
TZ: "Europe/London"
MAX_MEMORY: "8G"
VERSION: "1.12.2"
TYPE: "FORGE"
FORGEVERSION: "14.23.5.2855"
OPS: ${OPLIST}
WHITELIST: ${WLIST}
GENERIC_PACK: "/modpacks/RLCraft_Server_Pack_Beta_v2.8.2.zip"
USE_MODPACK_START_SCRIPT: "false"
ALLOW_FLIGHT: "true"
MAX_TICK_TIME: "-1"
VIEW_DISTANCE: 10
MAX_PLAYERS: 5
PVP: "false"
OVERRIDE_SERVER_PROPERTIES: "true"
LEVEL_TYPE: "BIOMESOP"
ENABLE_ROLLING_LOGS: "true"
USE_AIKAR_FLAGS: "true"
DIFFICULTY: "normal"
image: itzg/minecraft-server:java8
container_name: mc-rlcraft
restart: unless-stopped
volumes:
- ./data:/data
- ./modpacks:/modpacks
Container logs
1st launch
mc-rlcraft | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | find: unrecognized: -printf
mc-rlcraft | BusyBox v1.29.3 (2019-01-24 07:45:07 UTC) multi-call binary.
mc-rlcraft |
mc-rlcraft | Usage: find [-HL] [PATH]... [OPTIONS] [ACTIONS]
mc-rlcraft |
mc-rlcraft | Search for files and perform actions on them.
mc-rlcraft | First failed action stops processing of current file.
mc-rlcraft | Defaults: PATH is current directory, action is '-print'
mc-rlcraft |
mc-rlcraft | -L,-follow Follow symlinks
mc-rlcraft | -H ...on command line only
mc-rlcraft | -xdev Don't descend directories on other filesystems
mc-rlcraft | -maxdepth N Descend at most N levels. -maxdepth 0 applies
mc-rlcraft | actions to command line arguments only
mc-rlcraft | -mindepth N Don't act on first N levels
mc-rlcraft | -depth Act on directory *after* traversing it
mc-rlcraft |
mc-rlcraft | Actions:
mc-rlcraft | ( ACTIONS ) Group actions for -o / -a
mc-rlcraft | ! ACT Invert ACT's success/failure
mc-rlcraft | ACT1 [-a] ACT2 If ACT1 fails, stop, else do ACT2
mc-rlcraft | ACT1 -o ACT2 If ACT1 succeeds, stop, else do ACT2
mc-rlcraft | Note: -a has higher priority than -o
mc-rlcraft | -name PATTERN Match file name (w/o directory name) to PATTERN
mc-rlcraft | -iname PATTERN Case insensitive -name
mc-rlcraft | -path PATTERN Match path to PATTERN
mc-rlcraft | -ipath PATTERN Case insensitive -path
mc-rlcraft | -regex PATTERN Match path to regex PATTERN
mc-rlcraft | -type X File type is X (one of: f,d,l,b,c,s,p)
mc-rlcraft | -perm MASK At least one mask bit (+MASK), all bits (-MASK),
mc-rlcraft | or exactly MASK bits are set in file's mode
mc-rlcraft | -mtime DAYS mtime is greater than (+N), less than (-N),
mc-rlcraft | or exactly N days in the past
mc-rlcraft | -mmin MINS mtime is greater than (+N), less than (-N),
mc-rlcraft | or exactly N minutes in the past
mc-rlcraft | -newer FILE mtime is more recent than FILE's
mc-rlcraft | -inum N File has inode number N
mc-rlcraft | -user NAME/ID File is owned by given user
mc-rlcraft | -group NAME/ID File is owned by given group
mc-rlcraft | -size N[bck] File size is N (c:bytes,k:kbytes,b:512 bytes(def.))
mc-rlcraft | +/-N: file size is bigger/smaller than N
mc-rlcraft | -links N Number of links is greater than (+N), less than (-N),
mc-rlcraft | or exactly N
mc-rlcraft | -prune If current file is directory, don't descend into it
mc-rlcraft | If none of the following actions is specified, -print is assumed
mc-rlcraft | -print Print file name
mc-rlcraft | -print0 Print file name, NUL terminated
mc-rlcraft | -exec CMD ARG ; Run CMD with all instances of {} replaced by
mc-rlcraft | file name. Fails if CMD exits with nonzero
mc-rlcraft | -exec CMD ARG + Run CMD with {} replaced by list of file names
mc-rlcraft | -delete Delete current file/directory. Turns on -depth option
2nd launch
mc-rlcraft | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
mc-rlcraft | replace config/adhooks/adhooks.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 12 1000 1000 4096 Nov 21 20:53 /data'
mc-rlcraft | [init] Resolved version given 1.12.2 into 1.12.2
mc-rlcraft | [init] Resolving type given FORGE
mc-rlcraft | [init] Checking Forge version information.
mc-rlcraft | unzip: can't read standard input
Please switch to itzg/minecraft-server:java8-multiarch.
Many thanks that solved it!
I found a compatibility package that will resolve the original issue.
itzg/minecraft-server:java8 image is now fixed.
| gharchive/issue | 2021-11-21T21:00:04 | 2025-04-01T06:39:09.375937 | {
"authors": [
"hugalafutro",
"itzg"
],
"repo": "itzg/docker-minecraft-server",
"url": "https://github.com/itzg/docker-minecraft-server/issues/1127",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1091792375 | Forge and Packwiz
Enhancement Type
Improve an existing feature
Describe the enhancement
Allow forge to also implement packwiz, instead of just fabric.
Just figured out the issue, I thought I could just git clone and point the url to the file instead.
PS: Should add in the readme that it does works with forge and fabric, instead of just fabric.
Just figured out the issue, I thought I could just git clone and point the url to the file instead.
PS: Should add in the readme that it does works with forge and fabric, instead of just fabric.
I don't see where it says only Fabric. Or was it the example that implied that?
I don't see where it says only Fabric. Or was it the example that implied that?
Pretty much, plus I was still kinda new to packwiz and was trying to get used to it. Some completely my bad.
| gharchive/issue | 2022-01-01T10:55:03 | 2025-04-01T06:39:09.379201 | {
"authors": [
"Extensivity",
"itzg"
],
"repo": "itzg/docker-minecraft-server",
"url": "https://github.com/itzg/docker-minecraft-server/issues/1238",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1567880487 | Minimal Setup with Kickstart.nvim & VimTeX
Minimal Setup
❯ tree ~/.config/nvim
/Users/kiryph/.config/nvim
├── after
│ └── plugin
│ └── defaults.lua
├── init.lua
└── lua
└── custom
└── plugins.lua
5 directories, 3 files
Minimal init.lua
Kickstart.nvim provides a minimal init.lua using Packer.nvim and installing by default luasnip, nvim-treesitter and few others:
init.lua
-- Install packer
local install_path = vim.fn.stdpath 'data' .. '/site/pack/packer/start/packer.nvim'
local is_bootstrap = false
if vim.fn.empty(vim.fn.glob(install_path)) > 0 then
is_bootstrap = true
vim.fn.system { 'git', 'clone', '--depth', '1', 'https://github.com/wbthomason/packer.nvim', install_path }
vim.cmd [[packadd packer.nvim]]
end
require('packer').startup(function(use)
-- Package manager
use 'wbthomason/packer.nvim'
use { -- LSP Configuration & Plugins
'neovim/nvim-lspconfig',
requires = {
-- Automatically install LSPs to stdpath for neovim
'williamboman/mason.nvim',
'williamboman/mason-lspconfig.nvim',
-- Useful status updates for LSP
'j-hui/fidget.nvim',
-- Additional lua configuration, makes nvim stuff amazing
'folke/neodev.nvim',
},
}
use { -- Autocompletion
'hrsh7th/nvim-cmp',
requires = { 'hrsh7th/cmp-nvim-lsp', 'L3MON4D3/LuaSnip', 'saadparwaiz1/cmp_luasnip' },
}
use { -- Highlight, edit, and navigate code
'nvim-treesitter/nvim-treesitter',
run = function()
pcall(require('nvim-treesitter.install').update { with_sync = true })
end,
}
use { -- Additional text objects via treesitter
'nvim-treesitter/nvim-treesitter-textobjects',
after = 'nvim-treesitter',
}
-- Git related plugins
use 'tpope/vim-fugitive'
use 'tpope/vim-rhubarb'
use 'lewis6991/gitsigns.nvim'
use 'navarasu/onedark.nvim' -- Theme inspired by Atom
use 'nvim-lualine/lualine.nvim' -- Fancier statusline
use 'lukas-reineke/indent-blankline.nvim' -- Add indentation guides even on blank lines
use 'numToStr/Comment.nvim' -- "gc" to comment visual regions/lines
use 'tpope/vim-sleuth' -- Detect tabstop and shiftwidth automatically
-- Fuzzy Finder (files, lsp, etc)
use { 'nvim-telescope/telescope.nvim', branch = '0.1.x', requires = { 'nvim-lua/plenary.nvim' } }
-- Fuzzy Finder Algorithm which requires local dependencies to be built. Only load if `make` is available
use { 'nvim-telescope/telescope-fzf-native.nvim', run = 'make', cond = vim.fn.executable 'make' == 1 }
-- Add custom plugins to packer from ~/.config/nvim/lua/custom/plugins.lua
local has_plugins, plugins = pcall(require, 'custom.plugins')
if has_plugins then
plugins(use)
end
if is_bootstrap then
require('packer').sync()
end
end)
-- When we are bootstrapping a configuration, it doesn't
-- make sense to execute the rest of the init.lua.
--
-- You'll need to restart nvim, and then it will work.
if is_bootstrap then
print '=================================='
print ' Plugins are being installed'
print ' Wait until Packer completes,'
print ' then restart nvim'
print '=================================='
return
end
-- Automatically source and re-compile packer whenever you save this init.lua
local packer_group = vim.api.nvim_create_augroup('Packer', { clear = true })
vim.api.nvim_create_autocmd('BufWritePost', {
command = 'source <afile> | silent! LspStop | silent! LspStart | PackerCompile',
group = packer_group,
pattern = vim.fn.expand '$MYVIMRC',
})
-- [[ Setting options ]]
-- See `:help vim.o`
-- Set highlight on search
vim.o.hlsearch = false
-- Make line numbers default
vim.wo.number = true
-- Enable mouse mode
vim.o.mouse = 'a'
-- Enable break indent
vim.o.breakindent = true
-- Save undo history
vim.o.undofile = true
-- Case insensitive searching UNLESS /C or capital in search
vim.o.ignorecase = true
vim.o.smartcase = true
-- Decrease update time
vim.o.updatetime = 250
vim.wo.signcolumn = 'yes'
-- Set colorscheme
vim.o.termguicolors = true
vim.cmd [[colorscheme onedark]]
-- Set completeopt to have a better completion experience
vim.o.completeopt = 'menuone,noselect'
-- [[ Basic Keymaps ]]
-- Set <space> as the leader key
-- See `:help mapleader`
-- NOTE: Must happen before plugins are required (otherwise wrong leader will be used)
vim.g.mapleader = ' '
vim.g.maplocalleader = ' '
-- Keymaps for better default experience
-- See `:help vim.keymap.set()`
vim.keymap.set({ 'n', 'v' }, '<Space>', '<Nop>', { silent = true })
-- Remap for dealing with word wrap
vim.keymap.set('n', 'k', "v:count == 0 ? 'gk' : 'k'", { expr = true, silent = true })
vim.keymap.set('n', 'j', "v:count == 0 ? 'gj' : 'j'", { expr = true, silent = true })
-- [[ Highlight on yank ]]
-- See `:help vim.highlight.on_yank()`
local highlight_group = vim.api.nvim_create_augroup('YankHighlight', { clear = true })
vim.api.nvim_create_autocmd('TextYankPost', {
callback = function()
vim.highlight.on_yank()
end,
group = highlight_group,
pattern = '*',
})
-- Set lualine as statusline
-- See `:help lualine.txt`
require('lualine').setup {
options = {
icons_enabled = false,
theme = 'onedark',
component_separators = '|',
section_separators = '',
},
}
-- Enable Comment.nvim
require('Comment').setup()
-- Enable `lukas-reineke/indent-blankline.nvim`
-- See `:help indent_blankline.txt`
require('indent_blankline').setup {
char = '┊',
show_trailing_blankline_indent = false,
}
-- Gitsigns
-- See `:help gitsigns.txt`
require('gitsigns').setup {
signs = {
add = { text = '+' },
change = { text = '~' },
delete = { text = '_' },
topdelete = { text = '‾' },
changedelete = { text = '~' },
},
}
-- [[ Configure Telescope ]]
-- See `:help telescope` and `:help telescope.setup()`
require('telescope').setup {
defaults = {
mappings = {
i = {
['<C-u>'] = false,
['<C-d>'] = false,
},
},
},
}
-- Enable telescope fzf native, if installed
pcall(require('telescope').load_extension, 'fzf')
-- See `:help telescope.builtin`
vim.keymap.set('n', '<leader>?', require('telescope.builtin').oldfiles, { desc = '[?] Find recently opened files' })
vim.keymap.set('n', '<leader><space>', require('telescope.builtin').buffers, { desc = '[ ] Find existing buffers' })
vim.keymap.set('n', '<leader>/', function()
-- You can pass additional configuration to telescope to change theme, layout, etc.
require('telescope.builtin').current_buffer_fuzzy_find(require('telescope.themes').get_dropdown {
winblend = 10,
previewer = false,
})
end, { desc = '[/] Fuzzily search in current buffer]' })
vim.keymap.set('n', '<leader>sf', require('telescope.builtin').find_files, { desc = '[S]earch [F]iles' })
vim.keymap.set('n', '<leader>sh', require('telescope.builtin').help_tags, { desc = '[S]earch [H]elp' })
vim.keymap.set('n', '<leader>sw', require('telescope.builtin').grep_string, { desc = '[S]earch current [W]ord' })
vim.keymap.set('n', '<leader>sg', require('telescope.builtin').live_grep, { desc = '[S]earch by [G]rep' })
vim.keymap.set('n', '<leader>sd', require('telescope.builtin').diagnostics, { desc = '[S]earch [D]iagnostics' })
-- [[ Configure Treesitter ]]
-- See `:help nvim-treesitter`
require('nvim-treesitter.configs').setup {
-- Add languages to be installed here that you want installed for treesitter
ensure_installed = { 'c', 'cpp', 'go', 'lua', 'python', 'rust', 'typescript', 'help', 'vim' },
highlight = { enable = true },
indent = { enable = true, disable = { 'python' } },
incremental_selection = {
enable = true,
keymaps = {
init_selection = '<c-space>',
node_incremental = '<c-space>',
scope_incremental = '<c-s>',
node_decremental = '<c-backspace>',
},
},
textobjects = {
select = {
enable = true,
lookahead = true, -- Automatically jump forward to textobj, similar to targets.vim
keymaps = {
-- You can use the capture groups defined in textobjects.scm
['aa'] = '@parameter.outer',
['ia'] = '@parameter.inner',
['af'] = '@function.outer',
['if'] = '@function.inner',
['ac'] = '@class.outer',
['ic'] = '@class.inner',
},
},
move = {
enable = true,
set_jumps = true, -- whether to set jumps in the jumplist
goto_next_start = {
[']m'] = '@function.outer',
[']]'] = '@class.outer',
},
goto_next_end = {
[']M'] = '@function.outer',
[']['] = '@class.outer',
},
goto_previous_start = {
['[m'] = '@function.outer',
['[['] = '@class.outer',
},
goto_previous_end = {
['[M'] = '@function.outer',
['[]'] = '@class.outer',
},
},
swap = {
enable = true,
swap_next = {
['<leader>a'] = '@parameter.inner',
},
swap_previous = {
['<leader>A'] = '@parameter.inner',
},
},
},
}
-- Diagnostic keymaps
vim.keymap.set('n', '[d', vim.diagnostic.goto_prev)
vim.keymap.set('n', ']d', vim.diagnostic.goto_next)
vim.keymap.set('n', '<leader>e', vim.diagnostic.open_float)
vim.keymap.set('n', '<leader>q', vim.diagnostic.setloclist)
-- LSP settings.
-- This function gets run when an LSP connects to a particular buffer.
local on_attach = function(_, bufnr)
-- NOTE: Remember that lua is a real programming language, and as such it is possible
-- to define small helper and utility functions so you don't have to repeat yourself
-- many times.
--
-- In this case, we create a function that lets us more easily define mappings specific
-- for LSP related items. It sets the mode, buffer and description for us each time.
local nmap = function(keys, func, desc)
if desc then
desc = 'LSP: ' .. desc
end
vim.keymap.set('n', keys, func, { buffer = bufnr, desc = desc })
end
nmap('<leader>rn', vim.lsp.buf.rename, '[R]e[n]ame')
nmap('<leader>ca', vim.lsp.buf.code_action, '[C]ode [A]ction')
nmap('gd', vim.lsp.buf.definition, '[G]oto [D]efinition')
nmap('gr', require('telescope.builtin').lsp_references, '[G]oto [R]eferences')
nmap('gI', vim.lsp.buf.implementation, '[G]oto [I]mplementation')
nmap('<leader>D', vim.lsp.buf.type_definition, 'Type [D]efinition')
nmap('<leader>ds', require('telescope.builtin').lsp_document_symbols, '[D]ocument [S]ymbols')
nmap('<leader>ws', require('telescope.builtin').lsp_dynamic_workspace_symbols, '[W]orkspace [S]ymbols')
-- See `:help K` for why this keymap
nmap('K', vim.lsp.buf.hover, 'Hover Documentation')
nmap('<C-k>', vim.lsp.buf.signature_help, 'Signature Documentation')
-- Lesser used LSP functionality
nmap('gD', vim.lsp.buf.declaration, '[G]oto [D]eclaration')
nmap('<leader>wa', vim.lsp.buf.add_workspace_folder, '[W]orkspace [A]dd Folder')
nmap('<leader>wr', vim.lsp.buf.remove_workspace_folder, '[W]orkspace [R]emove Folder')
nmap('<leader>wl', function()
print(vim.inspect(vim.lsp.buf.list_workspace_folders()))
end, '[W]orkspace [L]ist Folders')
-- Create a command `:Format` local to the LSP buffer
vim.api.nvim_buf_create_user_command(bufnr, 'Format', function(_)
vim.lsp.buf.format()
end, { desc = 'Format current buffer with LSP' })
end
-- Enable the following language servers
-- Feel free to add/remove any LSPs that you want here. They will automatically be installed.
--
-- Add any additional override configuration in the following tables. They will be passed to
-- the `settings` field of the server config. You must look up that documentation yourself.
local servers = {
-- clangd = {},
-- gopls = {},
-- pyright = {},
-- rust_analyzer = {},
-- tsserver = {},
sumneko_lua = {
Lua = {
workspace = { checkThirdParty = false },
telemetry = { enable = false },
},
},
}
-- Setup neovim lua configuration
require('neodev').setup()
--
-- nvim-cmp supports additional completion capabilities, so broadcast that to servers
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities = require('cmp_nvim_lsp').default_capabilities(capabilities)
-- Setup mason so it can manage external tooling
require('mason').setup()
-- Ensure the servers above are installed
local mason_lspconfig = require 'mason-lspconfig'
mason_lspconfig.setup {
ensure_installed = vim.tbl_keys(servers),
}
mason_lspconfig.setup_handlers {
function(server_name)
require('lspconfig')[server_name].setup {
capabilities = capabilities,
on_attach = on_attach,
settings = servers[server_name],
}
end,
}
-- Turn on lsp status information
require('fidget').setup()
-- nvim-cmp setup
local cmp = require 'cmp'
local luasnip = require 'luasnip'
cmp.setup {
snippet = {
expand = function(args)
luasnip.lsp_expand(args.body)
end,
},
mapping = cmp.mapping.preset.insert {
['<C-d>'] = cmp.mapping.scroll_docs(-4),
['<C-f>'] = cmp.mapping.scroll_docs(4),
['<C-Space>'] = cmp.mapping.complete(),
['<CR>'] = cmp.mapping.confirm {
behavior = cmp.ConfirmBehavior.Replace,
select = true,
},
['<Tab>'] = cmp.mapping(function(fallback)
if cmp.visible() then
cmp.select_next_item()
elseif luasnip.expand_or_jumpable() then
luasnip.expand_or_jump()
else
fallback()
end
end, { 'i', 's' }),
['<S-Tab>'] = cmp.mapping(function(fallback)
if cmp.visible() then
cmp.select_prev_item()
elseif luasnip.jumpable(-1) then
luasnip.jump(-1)
else
fallback()
end
end, { 'i', 's' }),
},
sources = {
{ name = 'nvim_lsp' },
{ name = 'luasnip' },
},
}
-- The line beneath this is called `modeline`. See `:help modeline`
-- vim: ts=2 sts=2 sw=2 et
Additional Packages
I have added VimTeX and luasnip-latex-snippets.nvim as recommended by kickstart.nvim in the file ~/.config/nvim/lua/custom/plugins.lua:
return function(use)
use "lervag/vimtex"
use {
"iurimateus/luasnip-latex-snippets.nvim",
requires = { "L3MON4D3/LuaSnip", "lervag/vimtex" },
config = function()
require'luasnip-latex-snippets'.setup()
end,
ft = "tex",
}
end
Customized settings
in ~/.config/nvim/after/plugin/defaults.lua
require'nvim-treesitter.configs'.setup {
highlight = {
-- `false` will disable the whole extension
enable = true,
-- NOTE: these are the names of the parsers and not the filetype. (for example if you want to
-- disable highlighting for the `tex` filetype, you need to include `latex` in this list as this is
-- the name of the parser)
-- list of language that will be disabled
disable = { "latex" },
},
}
vim.g.tex_flavor = 'latex' -- IMPORTANT FOR snippets when using an empty file
local luasnip = require('luasnip')
luasnip.config.set_config {
history = true,
updateevents = 'TextChanged,TextChangedI',
}
However, no snippets are available when I edit a LaTeX file:
$ nvim demo.tex
:LuaSnipListAvailable
:lua require"luasnip.extras.snippet_list".open()
{
all = {},
tex = {}
}
What did I miss?
Not sure. I can't try rn, but could you try not lazy loading the plugin?
Remove ft = "tex" from packer.
| gharchive/issue | 2023-02-02T11:39:02 | 2025-04-01T06:39:09.399893 | {
"authors": [
"iurimateus",
"kiryph"
],
"repo": "iurimateus/luasnip-latex-snippets.nvim",
"url": "https://github.com/iurimateus/luasnip-latex-snippets.nvim/issues/8",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2629666162 | Evaluation of existing SCT methods
In this PR, we evaluate the SCT methods for MS lesion segmentation:
sct_deepseg_lesion
sct_deepseg PSIR/STIR
sct_deepseg MP2RAGE
We perform evaluation on the test split of the MSD dataset and on the external dataset.
Reviewed ! Ready to be merged !
| gharchive/pull-request | 2024-11-01T18:48:02 | 2025-04-01T06:39:09.432396 | {
"authors": [
"plbenveniste"
],
"repo": "ivadomed/ms-lesion-agnostic",
"url": "https://github.com/ivadomed/ms-lesion-agnostic/pull/35",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1729314711 | [FR] Support for vim mode commands "x", "p"
Currently, it doesn't work with vim mode.
I have set clipboard=unnamed " Use system clipboard in my .obsidian.vimrc
| gharchive/issue | 2023-05-28T08:53:23 | 2025-04-01T06:39:09.433756 | {
"authors": [
"yan42685"
],
"repo": "ivan-lednev/obsidian-persistent-links",
"url": "https://github.com/ivan-lednev/obsidian-persistent-links/issues/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2171905359 | Is there a way to access the socket that emitted event?
I need to broadcast whatever changes happened from user1 to user2 (working on the same document) , i couldn't access the socket that emitted the event i'm pretty sure i'm missing something. Thanks in advance.
+1 here
| gharchive/issue | 2024-03-06T16:18:27 | 2025-04-01T06:39:09.434645 | {
"authors": [
"abdousfayhi",
"odufuwa-segun"
],
"repo": "ivan-topp/y-socket.io",
"url": "https://github.com/ivan-topp/y-socket.io/issues/13",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1138277610 | ci(release): 3.0.1 [skip ci]
Automated changes by create-pull-request GitHub action
:tada: This PR is included in version 3.0.2 :tada:
The release is available on:
GitHub release
npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:
| gharchive/pull-request | 2022-02-15T07:10:59 | 2025-04-01T06:39:09.439375 | {
"authors": [
"ivangabriele"
],
"repo": "ivangabriele/bhala",
"url": "https://github.com/ivangabriele/bhala/pull/38",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1605536065 | extendDictionary is not switching translations properly
Version
5.24.1
Describe the bug
If creating en-US as an extension of en, via extendDictionary, the locale switcher is not switching between en and en-US:
https://user-images.githubusercontent.com/84905165/222242546-a487a4a9-519e-436e-a56b-ded3c88a1299.mp4
Reproduction
Use the svelteKit example app (https://github.com/ivanhofer/typesafe-i18n-demo-sveltekit) and update all dependencies (ncu -u) and add en-US:
Logs
No response
Config
No response
Additional information
No response
My bad. I assumed lodash.merge works in an immutable way. But instead it alters the orginal object. I will need to find a replacement for this line: https://github.com/ivanhofer/typesafe-i18n/blob/main/packages/utils/src/extendDictionary.mts#L24
It seems merge({}, obj1, obj2) is the solution.
Should be fixed in version 5.24.3. Thanks for reporting this issue.
Thanks for the quick fix!
| gharchive/issue | 2023-03-01T19:24:14 | 2025-04-01T06:39:09.444598 | {
"authors": [
"Cluster2a",
"ivanhofer"
],
"repo": "ivanhofer/typesafe-i18n",
"url": "https://github.com/ivanhofer/typesafe-i18n/issues/618",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
419350879 | [Bug Report]npm install出现异常
Environment
Ubuntu18.04.1 64位
Reproduction link
https://github.com/iview/iview-admin
Steps to reproduce
git clone https://github.com/iview/iview-admin.git
npm install
What is expected?
执行完成，无致命错误
What is actually happening?
报error错误，命令执行未完成，报错如下：
root@ubuntu:/home/tmp/iview-admin# npm install
npm WARN deprecated hoek@2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles@2.0.5: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated boom@2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
> nodent-runtime@3.2.1 install /home/tmp/iview-admin/node_modules/nodent-runtime
> node build.js
fs.js:114
throw err;
^
Error: EACCES: permission denied, open '/home/tmp/iview-admin/node_modules/nodent-runtime/dist/index.js'
at Object.openSync (fs.js:438:3)
at Object.writeFileSync (fs.js:1189:35)
at Object.<anonymous> (/home/tmp/iview-admin/node_modules/nodent-runtime/build.js:5:4)
at Module._compile (internal/modules/cjs/loader.js:701:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
at Module.load (internal/modules/cjs/loader.js:600:32)
at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
at Function.Module._load (internal/modules/cjs/loader.js:531:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
at startup (internal/bootstrap/node.js:283:19)
npm WARN eslint-config-standard@12.0.0 requires a peer of eslint@>=5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-standard@12.0.0 requires a peer of eslint-plugin-node@>=7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-standard@12.0.0 requires a peer of eslint-plugin-promise@>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-standard@12.0.0 requires a peer of eslint-plugin-standard@>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN iview-admin@2.0.0 No repository field.
npm WARN iview-admin@2.0.0 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nodent-runtime@3.2.1 install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nodent-runtime@3.2.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-03-11T07_59_47_560Z-debug.log
已经是用root的权限了。
解决了 ，还是权限问题。
因为是以root用户命令运行的npm install，但实际上还不行，需要加sudo
但是我从node官网下载最新的node软件，包含了npm。我的安装方式是，只是把node的路径/xxx/xxx/bin加入环境变量中，但在Ubuntu下，此时因为系统安全限制，非/usr/bin或/usr/local/bin下的可执行文件，是没法使用sudo作为命令前缀的。
解决办法，就是将node,npm的可执行文件放入/usr/bin或/usr/local/bin下。以这种方法安装的node和npm，是可以使用sudo npm install执行成功
it can work , npm install --unsafe-perm=true
| gharchive/issue | 2019-03-11T08:41:34 | 2025-04-01T06:39:09.451548 | {
"authors": [
"suhanyujie",
"woshihaoren"
],
"repo": "iview/iview-admin",
"url": "https://github.com/iview/iview-admin/issues/1222",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
133601054 | Set typescript as peerDependency
This way we don't depend on gulp-typescript to be updated each time a new TypeScript version is released, we can choose the exact version we want and we don't get it installed twice (which causes awkward moments like "why does it work in console but not in gulp-typescript?".)
Cheers. :smiley:
I agree that it's better to have typescript as a peerDependency, though that would be a breaking change. I plan to change this in the next major release, at the same time when TypeScript 2.0 is released. Closing for now, I will revisit this later.
| gharchive/pull-request | 2016-02-15T01:29:39 | 2025-04-01T06:39:09.472227 | {
"authors": [
"ivogabe",
"ntrrgc"
],
"repo": "ivogabe/gulp-typescript",
"url": "https://github.com/ivogabe/gulp-typescript/pull/284",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1936057152 | simple auctioning functionality
code
function().function() pass
| gharchive/issue | 2023-10-10T19:21:03 | 2025-04-01T06:39:09.480649 | {
"authors": [
"iwanmunro"
],
"repo": "iwanmunro/isam_nea",
"url": "https://github.com/iwanmunro/isam_nea/issues/7",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2080496211 | 🛑 BALLERISTO.COM is down
In 061b3f2, BALLERISTO.COM (https://www.balleristo.com) was down:
HTTP code: 502
Response time: 2319 ms
Resolved: BALLERISTO.COM is back up in 4342ff0 after 9 minutes.
| gharchive/issue | 2024-01-13T22:23:32 | 2025-04-01T06:39:09.483685 | {
"authors": [
"iwhp"
],
"repo": "iwhp/upptime",
"url": "https://github.com/iwhp/upptime/issues/182",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1190484346 | 🛑 Akilarの糖果屋 is down
In ba403e9, Akilarの糖果屋 (https://akilar.top) was down:
HTTP code: 403
Response time: 1061 ms
Resolved: Akilarの糖果屋 is back up in 33806ba.
| gharchive/issue | 2022-04-02T03:44:12 | 2025-04-01T06:39:09.487086 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/1138",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1367291373 | 🛑 10大大的小蜗牛 is down
In db667ce, 10大大的小蜗牛 (https://eallion.com) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 10大大的小蜗牛 is back up in 70ebdd8.
| gharchive/issue | 2022-09-09T05:03:11 | 2025-04-01T06:39:09.489434 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/1866",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1751621554 | 🛑 28mao is down
In 87887a7, 28mao (https://meuicat.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 28mao is back up in 9213ae7.
| gharchive/issue | 2023-06-11T21:55:39 | 2025-04-01T06:39:09.491845 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/3665",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2439500862 | 🛑 21Eurkon is down
In e51cc79, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in d650ec8 after 19 minutes.
| gharchive/issue | 2024-07-31T08:53:43 | 2025-04-01T06:39:09.494158 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/8683",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2456147742 | 🛑 21Eurkon is down
In ced0cab, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in fa77ff4 after 24 minutes.
| gharchive/issue | 2024-08-08T15:57:01 | 2025-04-01T06:39:09.496498 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/8849",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2458952918 | 🛑 21Eurkon is down
In e1661c5, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in 36ca5f6 after 9 minutes.
| gharchive/issue | 2024-08-10T07:21:14 | 2025-04-01T06:39:09.498985 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/8884",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2518439424 | 🛑 21Eurkon is down
In 6550204, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in 3d78b4d after 11 minutes.
| gharchive/issue | 2024-09-11T04:37:16 | 2025-04-01T06:39:09.501339 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/9523",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2572018559 | 🛑 21Eurkon is down
In d662bb6, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in 0591a7b after 24 minutes.
| gharchive/issue | 2024-10-08T04:27:45 | 2025-04-01T06:39:09.503641 | {
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/9997",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1819603317 | [BUG] Some bugs in shadow presentation in RenderableContentControl
The default value for CHAR in ShadowDisplay seems problematic.
DATE and LDATE as shown as format in ShadowDisplay
DATE_AND_TIME and DATE can not be changed in ShadowControl
Some LONG TYPE doesnt have type in render in SHadowControl
/cib
Branch 199-_BUG_Some_bugs_in_shadow_presentation_in_RenderableContentControl created!
| gharchive/issue | 2023-07-25T05:55:29 | 2025-04-01T06:39:09.507040 | {
"authors": [
"Brano5",
"IX-BOT"
],
"repo": "ix-ax/axsharp",
"url": "https://github.com/ix-ax/axsharp/issues/199",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1301783178 | Non-intuitive plotting range when combining EC and MS data
When combining .tsv and .mpt files in any ECMSMeasurement object it will plot from when EC data starts (when the potential column starts), contrary to what is ususally the case when reading in pure .tsv data (all data from time=0 until whenever .tsv file time stamp runs out. Would be nice if the format of plotting range, vs time of the ECMS object had the same time range as the pure MS object. This would also make sense as backgrounds are are somewhat easier defined prior any EC data collection, i.e. not having to define a new time range fro the plot (could of course be done using tspan=[0,np.max(full_ECMS_data.grab("time/s"))] or similar in the ECMS plotting command).
This depends on the workflow.
When doing EC-MS I and, I think, my colleagues here at ICL, start recording MS data while setting up and leaving MS data acquisition running until we go home. During the day we then run one or more EC measurements, which we think of as the actual experiments. When analizying data, we'll often have something like the following:
ms = Measurement.read(...) # all the MS data
ec_1 = Measurement.read(...) # experiment 1, with sample A
ec_2 = Measurement.read(...) # experiment 2, with sample B
ecms_1 = ec_1 + ms
ecms_2 = ec_2 + ms
ecms_1.plot() # plot 1
ecms_2.plot() # plot 2
If we used the tspan of the full data, then plot 1 and plot 2 have the same range and identical top panels. Yes, they show different ec data, but the part of the experiment I actually want to look at might be too small to resolve.
I've now updated the plotting function to accept the following strings as tspan specification:
"ec": use the timespan of the EC data (this will remain the default)
"ms": use the timespan of the MS data
"all": use a timespan containing all of the data.
So if you want the whole MS data plotted, you'll be able to just call ecms_1.plot(tspan="all"). Hope this is satisfactory?
The change is here: https://github.com/ixdat/ixdat/commit/8ced531ae42ecd844c28260b2fd5681ff3184b2d
I'll open the PR with it now, and hopefully soon distribute in ixdat 0.2.4
| gharchive/issue | 2022-07-12T09:18:34 | 2025-04-01T06:39:09.511216 | {
"authors": [
"KimDegnJensen",
"ScottSoren"
],
"repo": "ixdat/ixdat",
"url": "https://github.com/ixdat/ixdat/issues/91",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2121460288 | astro dev support
Is it possible to get this to work with astro dev?
I use a project called code-server which proxies ports through a '/proxy/portnumber' url. So when running the url of the homepage would look something like http://localhost:4080/proxy/4321/. Since the proxy port can change relative paths are needed.
This project works fine when doing astro build then astro preview, however astro dev doesn't work at all. All of the asset's ignore the relative paths ans use absolute paths such as http://localhost:4080/node_modules when it should be http://localhost:4080/proxy/4321/node_modules
Hello,
I think a base path should help you:
https://docs.astro.build/en/reference/configuration-reference/#base
| gharchive/issue | 2024-02-06T18:48:38 | 2025-04-01T06:39:09.515219 | {
"authors": [
"masterwendu",
"nlvw"
],
"repo": "ixkaito/astro-relative-links",
"url": "https://github.com/ixkaito/astro-relative-links/issues/13",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1829947351 | 🛑 Ixtanet SAT is down
In aa688f3, Ixtanet SAT ($MEDIA_SAT) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Ixtanet SAT is back up in f7c8d38.
| gharchive/issue | 2023-07-31T20:12:01 | 2025-04-01T06:39:09.517404 | {
"authors": [
"aalonzolu"
],
"repo": "ixtanet/upptime",
"url": "https://github.com/ixtanet/upptime/issues/795",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1248501115 | File Uploading - First Steps
Not fully functional, but first steps toward implementing a file upload functionality.
Great points, @j-andrews7! These are all resolved in the new commit, c8f845c.
File uploads working properly, hurray! Thanks for the help!
| gharchive/pull-request | 2022-05-25T18:20:41 | 2025-04-01T06:39:09.557298 | {
"authors": [
"j-andrews7",
"jake-steele"
],
"repo": "j-andrews7/CRISPRball",
"url": "https://github.com/j-andrews7/CRISPRball/pull/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2542858184 | BABEL_PARSER_SYNTAX_ERROR / REASONCODE: UNEXPECTEDTOKEN
Describe the bug
Expected Behaviour
To Start the Process
Code
https://raw.githubusercontent.com/NextGenerationHackers/WCJSDECODER/refs/heads/main/Game%20Files/Decoded%20Game%20File%20V1/VIPDecoded.js
Logs
No response
it is invalid syntax, there are many ? . in the script
[__w9_L3y[_0xd0709e(0x1b0)]]] ? . [__w9_L3y[_0xd0709e(0x18e)]]
| gharchive/issue | 2024-09-23T14:32:52 | 2025-04-01T06:39:09.568895 | {
"authors": [
"NextGenerationHackers",
"j4k0xb"
],
"repo": "j4k0xb/webcrack",
"url": "https://github.com/j4k0xb/webcrack/issues/116",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
258259129 | Modules gradient issue
My bar have gradient with two colors. When I used version 3.0.5 bar looked like this:
But after aur-git update to version 3.0.5-44-ga682d2a I got this:
Modules has no gradients now. I read the wiki, but there is nothing about it and I tried some combinations with format-background etc. Any help, please? Should I use one color for the bar?
P. S. Sorry about my English, it isn't my primary language.
There is some color weirdness in the latest commits, the issue is tracked in #639.
To confirm that this is actually the issue, could you post the output, when you run polybar with the -s option (for both versions)
Version 3.0.5:
%{l}%{A5:i3wm-wsprev: A4:i3wm-wsnext: A1:i3wm-wsfocus-1:} %{A A A} %{A1:thunar / &:A3:terminator --working-directory / &: F#38A1E3} %{F#252229}140%{F- A A F-} %{A1:thunar ~ &:A3:terminator --working-directory ~ &: F#38A1E3} %{F#252229}343%{F- A A F-} %{F#38A1E3} %{F- A1:terminator -x htop &:}42%{A} %{F#38A1E3} %{F- A1:terminator -x htop &:}19%{A} %{F#38A1E3} %{F- A1:~/.config/polybar/output.sh --battery:}100%{A}%{c}%{A1:~/.config/polybar/output.sh --date:}03:07:16%{A}%{r}%{A1:volmute: A4:volup: A5:voldown: F#38A1E3} %{F-}61%{A A A} %{F#38A1E3}%{F-} %{A1:~/.config/polybar/output.sh --interfaces &:A3:terminator -x nmtui &:}192.168.0.47%{A A} %{A1:xkblayout-state set +1 &: F#38A1E3} %{F#252229} 0%{A F-} %{A1:~/.config/polybar/output.sh --dropbox-notification &:A3:thunar ~/Downloads/Dropbox &: F#38A1E3} %{F#252229}R%{A A F-} %{F#38A1E3} %{F#252229}1%{F-} %{A1:xkblayout-state set +1 &: F#252229}EN%{F#D81A1C A F-}
Version 3.0.5-44-ga682d2a:
%{l}%{A5:i3wm-wsprev: A4:i3wm-wsnext: A1:i3wm-wsfocus-1:} %{A A A} %{A1:thunar / &:A3:terminator --working-directory / &: F#38A1E3} %{F#252229}140%{F- A A F-} %{A1:thunar ~ &:A3:terminator --working-directory ~ &: F#38A1E3} %{F#252229}343%{F- A A F-} %{F#38A1E3} %{F- A1:terminator -x htop &:}41%{A} %{F#38A1E3} %{F- A1:terminator -x htop &:}22%{A} %{F#38A1E3} %{F- A1:~/.config/polybar/output.sh --battery:}100%{A}%{c}%{A1:~/.config/polybar/output.sh --date:}03:05:38%{A}%{r}%{A1:volmute: A4:volup: A5:voldown: F#38A1E3} %{F-}61%{A A A} %{F#38A1E3}%{F-} %{A1:~/.config/polybar/output.sh --interfaces &:A3:terminator -x nmtui &:}192.168.0.47%{A A} %{A1:xkblayout-state set +1 &: F#38A1E3} %{F#252229} 0%{A F-} %{A1:~/.config/polybar/output.sh --dropbox-notification &:A3:thunar ~/Downloads/Dropbox &: F#38A1E3} %{F#252229}R%{A A F-} %{F#38A1E3} %{F#252229}1%{F-} %{A1:xkblayout-state set +1 &: F#252229}EN%{F#D81A1C A F-}
See no difference.
Yeah I don't see any either.
I think I have tracked down the issue. Can you locally revert commit https://github.com/jaagr/polybar/commit/0bd8f1f69a8dfdb2f2800a6612c8acb7e6c86ed2 and recompile and test if that fixes it.
Sorry for delay. I just did read some manuals about git, because I'm not so friendly with it. I reverted commit as you said, recompiled it and it works fine now:
What's now?
Now, we have figured out what the problem is. That commit you reverted sets the background color when rendering a module to the bar background and doesn't consider a gradient here.
I will try to fix this as soon as we merge #729 as it also messes with the colors.
OK! Thanks for help by the way!
@patrick96 Any updates on a fix? Just wanted to know if you've started working on it, because as it stands, this is the only issue left on the 3.1.0 milestone.
Sorry, I forgot about this. I think we can release version 3.1.0 without this fix and just schedule it for 3.2.0, it isn't really a critical bug
@patrick96 hey, I seem to have managed to fix this, do you mind if I submit a PR?
@TonCherAmi Yes! Please do.
| gharchive/issue | 2017-09-16T21:14:31 | 2025-04-01T06:39:09.605978 | {
"authors": [
"NBonaparte",
"TonCherAmi",
"flameshikari",
"patrick96"
],
"repo": "jaagr/polybar",
"url": "https://github.com/jaagr/polybar/issues/759",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
760961947 | fix bubble tab
menyesuaikan padding pada komponen bubble tab
menambahkan dokumentasi pada komponen bubble tab
[S15 App] Konsistensi margin/padding pada bubble tab di halaman homescreen
review gan @anandarh @aldiiii @jaluowen
| gharchive/pull-request | 2020-12-10T06:46:59 | 2025-04-01T06:39:09.612014 | {
"authors": [
"gaganugraha33"
],
"repo": "jabardigitalservice/pikobar-flutter",
"url": "https://github.com/jabardigitalservice/pikobar-flutter/pull/473",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1057324846 | Release v6.2.0?
Can we get a release of this package so we get the latest aiohttp pinning into Home Assistant?
Currently, this package (on the latest release) conflict with the aiohttp version used by Home Assistant. Releasing a newer version would solve that.
Yes, no problem. I'll do that tonight
v6.2.0 was just released https://pypi.org/project/pyatmo/6.2.0/
| gharchive/issue | 2021-11-18T12:55:33 | 2025-04-01T06:39:09.621030 | {
"authors": [
"frenck",
"jabesq"
],
"repo": "jabesq/pyatmo",
"url": "https://github.com/jabesq/pyatmo/issues/163",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
390470343 | Bus death method #1
Summary:
Unplugging a usb connected device while still connected to the jacdac bus seems to kill the bus entirely, until it is replugged, at which point anything else that was connected to the bus no longer connects except for the replugged device.
Hardware Setup:
CPX running a Button service (sample code here).
CPX running an Accelerometer service connected to USB battery, with only ground and tx connected to audio jack (sample code here).
Arcade running logging service.
Reproduction Steps:
Leave services / clients running and connected to the bus.
Unplug CPX Accelerometer from USB, but leave audio jack connected.
The bus has died!
Replug the USB battery into the CPX Accelerometer .
CPX acclerometer is connected to bus, but CPX Button no longer connected to bus.
Thanks Teddy.
Just for my info, are we filing JACDAC issues here @pelikhan @teddyseyed ?
I think this is samd specific from the sounds of it? I certainly didn't robustly test CPX...
I assume there are more than one bus death methods by the title? :smile:
Where do you want them?
Get Outlook for iOShttps://aka.ms/o0ukef
From: James Devine notifications@github.com
Sent: Thursday, December 13, 2018 6:37:52 AM
To: jamesadevine/jacdac
Cc: Peli de Halleux; Mention
Subject: Re: [jamesadevine/jacdac] Bus death method #1 (#3)
Just for my info, are we filing JACDAC issues here @pelikhanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpelikhan&data=02|01|jhalleux%40microsoft.com|8242843aaa0c4b521caa08d661089037|72f988bf86f141af91ab2d7cd011db47|1|0|636803086740808449&sdata=uh0xbZU6gO332YbXX0X2FnlUIKFwIqxrJdAeYf0FrIE%3D&reserved=0 @teddyseyedhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fteddyseyed&data=02|01|jhalleux%40microsoft.com|8242843aaa0c4b521caa08d661089037|72f988bf86f141af91ab2d7cd011db47|1|0|636803086740818457&sdata=awKj5X1Z1p%2FzUelCbcqCKnj%2FaRf8jZ54eN9mN6OGrN4%3D&reserved=0 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjamesadevine%2Fjacdac%2Fissues%2F3%23issuecomment-446990423&data=02|01|jhalleux%40microsoft.com|8242843aaa0c4b521caa08d661089037|72f988bf86f141af91ab2d7cd011db47|1|0|636803086740828461&sdata=5jdsRB9mhhOEIWUKefvChaoPQyp8XhaSUninWb0G2hs%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KRZkzRR8HVVecY2dGMu9zivPczbtks5u4mZAgaJpZM4ZQtx6&data=02|01|jhalleux%40microsoft.com|8242843aaa0c4b521caa08d661089037|72f988bf86f141af91ab2d7cd011db47|1|0|636803086740828461&sdata=79tcgG0OVCtq3MlG5Q8FoYrbmqog8zw%2FH2Yw17I%2ByPY%3D&reserved=0.
It's probably best to unify all jacdac issues here, rather than across the billion codal repos! :smile:
V-1 is not supported :smile: I'm sure V0 will bring a whole host of issues.
| gharchive/issue | 2018-12-13T00:43:01 | 2025-04-01T06:39:09.630299 | {
"authors": [
"jamesadevine",
"pelikhan",
"teddyseyed"
],
"repo": "jacdac/jacdac",
"url": "https://github.com/jacdac/jacdac/issues/3",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1366193128 | Fix zap logging adapter to work with latest pgx v5
Also update zap dependency to latest version
Thanks!
| gharchive/pull-request | 2022-09-08T12:13:11 | 2025-04-01T06:39:09.646097 | {
"authors": [
"jackc",
"lafriks"
],
"repo": "jackc/pgx-zap",
"url": "https://github.com/jackc/pgx-zap/pull/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
60277717 | Cursor isn't properly aligned with canvas
The black box around the drawing cursor isn't aligned properly with what's drawn. I think the cursor it should be shifted one pixel to the left, so the black box is centered around the area that gets painted. See attached image.
...the image that I meant to upload was
| gharchive/issue | 2015-03-08T21:39:41 | 2025-04-01T06:39:09.647997 | {
"authors": [
"DanGoldbach"
],
"repo": "jackhou-chromium/bitmapper",
"url": "https://github.com/jackhou-chromium/bitmapper/issues/91",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.