Android memory leaks until it is killed by the system

We tested the latest version, as well as beta version, and found that if any animation on the APP plus a picture, it would lead to a constant increase in memory. The more complex the UI, the faster the memory grows (Native memory).
The simplest version below, with only one picture and one animation

When APP goes back to the background, Native memory decreases slightly. In the background, the memory will not change, but when it goes back to the front, Native memory will be higher than before.
[√] Flutter (Channel unknown, v1.5.2, on Microsoft Windows [Version 10.0.17134.706], locale zh-CN)
    • Flutter version 1.5.2 at C:\tool\flutter
    • Framework revision efe744a360 (2 days ago), 2019-04-17 10:43:19 -0400
    • Engine revision fdd427241b
    • Dart version 2.2.1 (build 2.2.1-dev.4.2 8e73b3c006)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\xxx\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = C:\Users\xxx\AppData\Local\Android\sdk
    • Java binary at: C:\tool\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.3)
    • Android Studio at C:\tool\android-studio
    • Flutter plugin version 34.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[√] IntelliJ IDEA Community Edition (version 2018.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2018.2.1
    • Flutter plugin version 34.0.1
    • Dart plugin version 182.5215

[√] VS Code, 64-bit edition (version 1.31.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 2.25.1

[√] Connected device (1 available)
    • KNT AL10 • 69DDU16511000544 • android-arm64 • Android 6.0 (API 23)

import 'package:flutter/material.dart';
import 'package:flutter/cupertino.dart';

void main() async {
	runApp(App());
}

class App extends StatefulWidget {
	App() {
		print("new App");
	}

	@override
	_AppState createState() => new _AppState();

}

class _AppState extends State<App> {
	@override
	void initState() {
		super.initState();
	}

	@override
	void dispose() {
		super.dispose();
	}

	@override
	Widget build(BuildContext context) {
		print("App Build");
		return new MaterialApp(
			title: "test",
			home: Boot()
		);
	}
}

class Boot extends StatefulWidget {
	Boot({Key key}) : super(key: key);

	@override
	BootState createState() => new BootState();
}

class BootState extends State<Boot> {
	@override
	void initState() {
		super.initState();
	}

	@override
	void dispose() {
		super.dispose();
	}

	@override
	Widget build(BuildContext context) {
		List<Widget> res = [];
		for(int i = 0; i < 200; i++){
			res.add(
				new Container(
					height: 20.0,
					decoration: new BoxDecoration(
						border: new Border(
							bottom: new BorderSide(
								color: Theme.of(context).dividerColor
							)
						)
					),
					child: new Text(
						i.toString()
					),
				)
			);
		}
		return new Scaffold(
			body: new Stack(
				children: <Widget>[
					new Positioned(
						child: new Image.network(
							"http://<IP_ADDRESS>/background.png",
							fit: BoxFit.cover,
						),
						left: 0.0,
						top: 0.0,
						width: MediaQuery.of(context).size.width,
						height: MediaQuery.of(context).size.height,
					),
					new Positioned(
						left: 0.0,
						top: 0.0,
						width: MediaQuery.of(context).size.width,
						height: MediaQuery.of(context).size.height,
						child: new Center(
							child: new CupertinoActivityIndicator(
								animating: true,
								radius: 50.0,
							),
						),
					)
				],
			),
		);
	}
}

@mklim @kangwang1988

Thanks for reporting the bug!
In debug mode I'm seeing memory climbing just from combining the loop/array with the animation even without any image.
So far I've been unable to reproduce any kind of memory climb at all in release mode though.
Just making sure, are you seeing this leak in both release mode and debug mode?

@mklim We also found this problem in profile and release modes, as long as the time is long enough (the screen is not closed, less than the background, hours) memory will continue to grow, when the UI is very complex, memory growth is very fast.

Profile Mode
A more complex UI was redone and ran for more than an hour (the screen was always on in the front desk).
You'll find that Native memory keeps going up.

This is the test code.
Two resource images are needed in the assets/images/directory, as shown in the annex.
import 'package:flutter/material.dart';
import 'package:flutter/cupertino.dart';
import 'package:flutter/foundation.dart';
import 'dart:async';
import 'dart:math';

void main() async {
	runApp(App());
}

class App extends StatefulWidget {
	App() {
		print("new App");
	}

	@override
	_AppState createState() => new _AppState();

}

class _AppState extends State<App> {
	@override
	void initState() {
		super.initState();
	}

	@override
	void dispose() {
		super.dispose();
	}

	@override
	Widget build(BuildContext context) {
		print("App Build");
		return new MaterialApp(
			title: "test",
			home: Boot()
		);
	}
}

class Boot extends StatefulWidget {
	Boot({Key key}) : super(key: key);

	@override
	BootState createState() => new BootState();
}

class BootState extends State<Boot> {
	int _index = 0;
	@override
	void initState() {
		super.initState();
		new Timer.periodic(new Duration(seconds: 3), (Timer timer){
			this.setState((){
				this._index = (this._index + 1) % 8;
			});
		});
	}

	@override
	void dispose() {
		super.dispose();
	}

	@override
	Widget build(BuildContext context) {
		return new Scaffold(
			body: new Stack(
				children: <Widget>[
					new Positioned(
						child: new Image.asset(
							"assets/images/background.png",
							fit: BoxFit.cover,
						),
						left: 0.0,
						top: 0.0,
						width: MediaQuery.of(context).size.width,
						height: MediaQuery.of(context).size.height,
					),
					new Container(
						width: MediaQuery.of(context).size.width,
						child: new Column(
							children: <Widget>[
								new AppBar(
									automaticallyImplyLeading: false,
									leading: new BackButton(),
									title: new Text("test"),
									backgroundColor: Colors.transparent,
									elevation: 0.0,
								),
								new Padding(
									child: new Wrap(
										runSpacing: 15.0,
										children: List.generate(8, (int index){
											return new HeadIcon(
												isSpeaking : index == this._index
											);
										}),
									),
									padding: new EdgeInsets.only(
										top: 15.0,
										bottom: 15.0
									),
								),
								new Expanded(
									child: new MessageList(),
								)
							],
						),
					),
				],
			),
		);
	}
}

class MessageList extends StatefulWidget {
	MessageList({Key key}):super(key: key);
	MessageListState createState() => new MessageListState();
}

class MessageListState extends State<MessageList> {
	Timer _timer;
	List<int> _data = [];
	ScrollController _controller;
	Random _random = new Random();

	@override
  void initState() {
    super.initState();
    this._controller = new ScrollController(keepScrollOffset: true);
    this._controller.addListener(this._onScroll);
    this._timer = Timer.periodic(new Duration(milliseconds: 200), this._onTimer);
  }

  @override
  void dispose() {
		if(this._timer != null){
			this._timer.cancel();
			this._timer = null;
		}
		this._controller.removeListener(this._onScroll);
		this._controller.dispose();
    super.dispose();
  }

	_onTimer(Timer timer){
		this.setState((){
			this._data.add(this._random.nextInt(20));
			if(this._data.length > 200){
				this._data.removeRange(0, this._data.length - 200);
			}
		});
		//for test
		this._scrollEnd();
	}

	void _onScroll(){

	}

	void _scrollEnd(){
		if(!this._controller.hasClients) return;
		if(this._controller.position == null) return;
		if(this._controller.position.maxScrollExtent == null) return;
		if(this._controller.position.maxScrollExtent > this._controller.offset){
			this._scrollToEnd();
		}
	}

	void _scrollToEnd() {
		if(!this._controller.hasClients) return;
		this._controller.jumpTo(
			this._controller.position.maxScrollExtent
		);
	}

	@override
	Widget build(BuildContext context) {
    return new ListView.builder(
	    controller: this._controller,
	    itemCount: this._data.length,
	    itemBuilder: (BuildContext context, int index){
	    	return new Container(
			    height: 42.0 + this._data.elementAt(index),
			    padding: new EdgeInsets.only(
				    left: 15.0,
				    top: 6.0,
				    bottom: 6.0
			    ),
			    child: new Row(
				    children: <Widget>[
							new ClipRRect(
								borderRadius: new BorderRadius.all(
									new Radius.circular(15.0)
								),
								child: new Image.asset(
									"assets/images/head.jpg",
									width: 30.0,
									height: 30.0,
								),
							),
					    new Padding(
						    padding: new EdgeInsets.only(
							    left: 12.0
						    ),
						    child: new Text(
							    "number ${this._data.elementAt(index)} => data len = ${this._data.length} => max len = 200",
							    style: new TextStyle(
								    fontSize: 12.0
							    ),
						    ),
					    )
				    ],
			    ),
		    );
    });
  }
}

class HeadIcon extends StatelessWidget {
	final bool isSpeaking;
	HeadIcon({Key key, this.isSpeaking = false}):super(key: key);

	@override
	Widget build(BuildContext context) {
    return new Container(
	    width: MediaQuery.of(context).size.width / 4,
	    alignment: Alignment.topCenter,
	    child: new Stack(
		    overflow: Overflow.visible,
		    children: <Widget>[
		    	new ClipRRect(
				    borderRadius: new BorderRadius.all(
					    new Radius.circular(33.0)
				    ),
				    child: new Image.asset(
					    "assets/images/head.jpg",
					    width: 66.0,
					    height: 66.0,
				    ),
			    ),
			    new SoundFastWare(
				    isSpeaking: this.isSpeaking,
			    )
		    ],
	    ),
    );
  }
}

class SoundFastWare extends StatefulWidget {
	final bool isSpeaking;
	SoundFastWare({Key key, this.isSpeaking}):super(key: key);

	@override
	_SoundFastWareState createState() => new _SoundFastWareState();
}

class _SoundFastWareState extends State<SoundFastWare> with SingleTickerProviderStateMixin {
	AnimationController _controller;
	Animation _opacity;
	Animation _scale;

	@override
	void initState() {
		super.initState();
		this._controller = new AnimationController(
			duration: const Duration(milliseconds: 800),
			vsync: this,
		);
		this._opacity = Tween(
			begin: 1.0,
			end: 0.0,
		).animate(
			CurvedAnimation(
				parent: this._controller,
				curve: Interval(
					0.0,
					1.0,
					curve: Curves.linear,
				),
			),
		);
		this._scale = Tween(
			begin: 1.0,
			end: 1.25,
		).animate(
			CurvedAnimation(
				parent: this._controller,
				curve: Interval(
					0.0,
					1.0,
					curve: Curves.linear,
				),
			),
		);
		this._scale.addListener(this._onChanged);
		if(this.widget.isSpeaking){
			this._controller.forward();
		}
	}

	@override
	void didUpdateWidget(SoundFastWare old){
		super.didUpdateWidget(old);
		if(old.isSpeaking != this.widget.isSpeaking){
			if(this.widget.isSpeaking){
				this._controller.forward(from: 0.0);
			}
		}
	}

	@override
	void dispose() {
		this._scale.removeListener(this._onChanged);
		this._controller.dispose();
		super.dispose();
	}

	_onChanged() async {
		setState(() {

		});
		if(this._controller.status == AnimationStatus.completed && this.widget.isSpeaking){
			this._controller.forward(from: 0.0);
		}
	}

	Widget _buildAni(BuildContext context, Widget child) {
		double width = 66.0;
		double translate = 0.0 - ((this._scale.value - 1.0) * width / 2 / this._scale.value);
		return new Container(
			width: width,
			height: width,
			decoration: new BoxDecoration(
				border: new Border.all(
					color: this.widget.isSpeaking ?
					Colors.amberAccent.withOpacity(this._opacity.value) :
					Colors.transparent,
					width: 3.0,
					style: BorderStyle.solid,
				),
				borderRadius: new BorderRadius.circular(width / 2),
			),
			transform: Matrix4.identity()
				..scale(this._scale.value, this._scale.value)
				..translate(translate, translate),
		);
	}

	@override
	Widget build(BuildContext context) {
		double width = 66.0;
		return new Positioned(
			left: 0.0,
			top: 0.0,
			width: width,
			height: width,
			child: new IgnorePointer(
				child: new AnimatedBuilder(
					animation: this._controller,
					builder: _buildAni
				),
			),
		);
	}
}

@mklim Very anxious, online project

Got it, thanks for the clarification. And it's not a problem, thanks for the extra info. Looking into it again.

I'm seeing a leak with the latest sample case. No OOM crash yet, but I can see it climbing just from letting it run for a couple minutes. /cc @jason-simmons

I think ImageCache is likely related here. I'm not seeing the same linear climb with maximumSize = 0.

I noticed that a lot of EngineLayer objects are not being garbage collected promptly when running this app.  Increasing EngineLayer::GetAllocationSize to something much higher seems to help.

Thank you very much. We will adjust Engine Layer:: GetAllocation Size and then test it.

When we set Layer:: GetAllocation to 200,000, we found that there were still problems on some mobile phones.
Setting Layer:: GetAllocation to 1 million works well

We found that when we set Engine Layer:: GetAllocation to a large value, the performance of different mobile phones varies greatly. One can maintain 300 MB of memory in use, but some will maintain around 1G.

Is there some other way we can clue the VM to GC these objects without spoofing the size?
Is this just a Dart VM bug on Android that it's not collecting something with no references left to it?  Or are we retaining a refernece somewhere?

@jason-simmons @mklim @dnfield
We tested the release version again today, and we found that memory leaks still exist, memory will continue to rise, will not stop, Profile mode is much better.

Just talked with @jason-simmons a bit more about this.
He's seeing that this app just never goes idle, so the GC doesn't get a chance to collect these items. But making them look bigger forces GCs too often in apps that don't need it, which slows some other key performance metrics we can't afford.
A few thoughs on this:

@mraleph - is there some way the Garbage Collector can be smarter about this?  Is there a deadline we can give it that says "collect this stuff even if we're saying we're not idle after this much time"?
It may make sense to pool EngineLayers instead of collecting them.  I'm not sure about the model there, @liyuqian probably knows more.  The idea would be that instead of creating a new EngineLayer for each frame, we only create them if the pool has been exhausted.  This should keep our memory usage more constent and limit GC churn during animations.
I don't like this idea, but it may make sense to give users an option to "try to force" a GC.

I don't like the third option because .NET has it and it almost never works the way you think it will.  It can only ever be a suggestion to the GC, it's really hard to test or predict, and the cases where a user actually knows when to do a GC are very, very, very rare.
/cc @Hixie

(As far as whether this is a retain cycle, I'm pretty sure it's not - Jason says that forcing a GC fixes it, which shouldn't be the case if it was actually a retain cycle)

@dnfield Thanks for the clarification and ideas. It appears the first two options need some time to resolve and test, since our app has already been delivered to lots of users, it's urgent for us to deliver a hotfix, so the third option might be a solution for us right now.   Would you please share some more on how to force a GC manually? We have the ability to re-compile the engine.
Thanks a lot.

For the really "quick" fix, modify the engine to always return a null EngineLayer. That way, you won't have any memory cost by discarding the retained rendering performance optimization. If you have any questions, I'll implement the hack and post the git diff here.

In the long run, I'll raise the priority of https://github.com/flutter/flutter/issues/31498 and hopefully fix it in a week or two.

Looking at your code, there are a few optimiztions you might try - locally they get better memory performance for me and probably better frame builds.  See https://gist.github.com/dnfield/b6e5b4ada9f79f98243628e361567f00
Things I did:

Try to avoid building the whole Scaffold on every tick.
Try to avoid creating more animations than needed (e.g. don't create those SoundFastWare animations if they won't draw anything).
Try to avoid creating more ClipRects than necessary.  clipping is expensive - Try to only create the ones you need and reuse them in the tree; if you have multiple images in your actuall application and can't do it the way I did it in the gist, maybe you can use some GlobalKeys based on the avatar you want to show so that the framework will reuse them a bit more.
Avoid repeatedly calling List.removeRange.  It's not got great performance characteristics.  You could probably do better than a Queue here - it has O(1) add and remove, but O(N) lookup.  With a better circular list/queue class, you could probably get O(1) lookup and O(1) add and remove (e.g. a list of 200 items with a pointer to the head and tail that just keeps cycling through the buffer and does quick addition to figure out how to look up an index).

In other words, I would first try to tune the performance of your app so you don't have to resort to things like trying to force more garbage collections. I suspect your framerates are already on the slower side - anything you do to make GCs happen more frequently without changing that will only make your app slower :(

Thanks for your reply.
I'll try to modify the engine by your way, but it would be great if you could post the git diff. :)

@liyuqian Thanks for your reply.
We will try to modify the engine by the your way. But it would be great if you could post the hacked code. :)

@dnfield Very appreciated for your detail explanation, advises and the gist.
Since the demo code we provided is not part of our product app, we made it to demonstrate the memory increasement issue deliberately, the optimization suggestions are helpful but still cannot resolve the memory issue in our product app.So we would try liyuqian's hack way. :)
Thank you.

@zhileichen Here's the diff that I just tested:
diff --git a/lib/ui/painting/engine_layer.h b/lib/ui/painting/engine_layer.h
index 1dc565c51..5c008e7dd 100644
--- a/lib/ui/painting/engine_layer.h
+++ b/lib/ui/painting/engine_layer.h
@@ -27,7 +27,8 @@ class EngineLayer : public RefCountedDartWrappable<EngineLayer> {

   static fml::RefPtr<EngineLayer> MakeRetained(
       std::shared_ptr<flutter::ContainerLayer> layer) {
-    return fml::MakeRefCounted<EngineLayer>(layer);
+    return nullptr;
+    // return fml::MakeRefCounted<EngineLayer>(layer);
   }

I'm sorry that I didn't have a chance to test and post this on Friday because there was a TODAY issue (the highest priority issue of Flutter) on that day.
Please let me know if this alleviates your memory usage or not. If not, maybe something other than EngineLayer is causing the issue.

@liyuqian Thanks for your code. We have modified the engine as same as your code last friday, but it did not alleviate the memory usage, the memory still increase linearly. It turns out it's not the EngineLayer causing the issue?
And we found that, increasing EngineLayer::GetAllocationSize to 10,000,000  works well in the Profile mode, but not works in the Release mode.  When set EngineLayer::GetAllocationSize to 10,000,000 and compile the engine in Profile mode, the memory usage of our app would increased linearly at first, after a period  the usage would stay smooth and steady in a level.

Are any optimizations turned on to disable the modification of EngineLayer::GetAllocationSize in the  Release mode ?

@dnfield I don't think there is any amazing GC based solution here - it a fairly classical issue when GC managed heap retains native resources of unknown size. If you have an object which is managed by GC then you need to periodically trigger full GC to collect it. For GC to trigger VM needs to understand that heap is too large. However if full GC triggers too often - you get performance degradation.
/cc @rmacnak-google

@zhileichen I think huge EngineLayer::GetAllocationSize in the profile mode may be triggering full GC to collect memory in other places. It seems that doesn't happen in release mode so you may need to find another way. @mraleph and @rmacnak-google from the Dart team may have better suggestions to that end.

@jason-simmons @mklim @dnfield
I'm sorry to interrupt. Is there any progress to solve this problem?

@jason-simmons @mklim @dnfield
I'm sorry to interrupt. Is there any progress to solve this problem?

Bringing this back to our attentions. This is already a "customer: crowd" issue, and I just heard from @cbracken that Fuchsia is also experiencing this kind of memory issue (the memory usage keeps going up). So this issue is becoming more and more important.
Here's one potential strategy to fix this:

Confirm the reproduction of this issue on master Flutter today. @mklim : since you've tried reproduced it earlier, can you please confirm if it's still reproducible today?
Once reproduced, turn the reproduction into a device lab memory test so everyone can reproduce this issue with a minimum effort, and we can continuously track our working progress. Either I, @dnfield , or @jason-simmons can take this once the reproduction is confirmed.
Collaborate with the DevTools (CC @cobblest @terrylucas ) and Dart teams to figure out exactly where the memory goes. The engine may need to provide better APIs for that.

Since this bug was opened, we've reduced the size of the Skia resource cache significantly.  Is it significantly increasing beyond that?
We should take a look at where the allocated memory is going.

@dnfield : if it never increases beyond that point, which means that this issue is no longer reproducible, then we can close this issue without further work :D That's the best case and I do hope Michael would give us that good news. And if that's indeed the case, we'll probably just file a separate issue on Fuchsia only as they may not set the resource cache properly.

I'm not seeing an obvious leak given the earlier repro case from issuecomment-485139640. I am seeing an initial spike in memory, but the usage seems to drop back down to around 9400KB on my test device given enough time. Test data is in this spreadsheet.
Given that I think we should close this and re-open new issues about leaks in the future with specific reproduction cases. Memory leaks can come from basically anywhere, so it's likely whatever was root causing this initially has been fixed like @dnfield suggested and the leaks @cbracken is reporting on Fuchsia are from a different path.

Thanks for the detailed analysis @mklim .  A quick look at your data suggests to me that https://github.com/flutter/engine/pull/10434 probably helped this case significantly.  The graphics cache is not getting larger than 50mb (assuming I have the scale right) in your sheet, whereas previously it would have been allowed to grow to about 10x that.


Tracking issue for new features

pre 1.0

string interpolation (https://github.com/jonathandturner/rhai/issues/121)

1.0

futures (https://github.com/jonathandturner/rhai/issues/52)
basic threads (https://github.com/jonathandturner/rhai/issues/36)
advanced threads + actors (https://github.com/jonathandturner/rhai/issues/32)
formal grammar and formal parser (https://github.com/jonathandturner/rhai/issues/4)
rudimentary error recovery (https://github.com/jonathandturner/rhai/issues/119)
rudimentary type checking  (https://github.com/jonathandturner/rhai/issues/117)
compiling to byte-codes  (https://github.com/jonathandturner/rhai/issues/161)
reverse-format an AST back into code (why would anyone want this?) - if this can be pretty-printed, then we can have a rhaifmt formatter.

closed

stdlib opt-in (https://github.com/jonathandturner/rhai/issues/27) closed by https://github.com/jonathandturner/rhai/pull/104
throw errors (https://github.com/jonathandturner/rhai/issues/78) closed by https://github.com/jonathandturner/rhai/pull/104
support minimal builds (for size) via turning off language features closed by https://github.com/jonathandturner/rhai/pull/106
support constants closed by https://github.com/jonathandturner/rhai/pull/108
no-std (https://github.com/jonathandturner/rhai/issues/19) closed by https://github.com/jonathandturner/rhai/pull/103
eval closed by https://github.com/jonathandturner/rhai/pull/110
evaluate expressions only (https://github.com/jonathandturner/rhai/issues/113) closed by https://github.com/jonathandturner/rhai/pull/114
objects (https://github.com/jonathandturner/rhai/issues/73) closed by https://github.com/jonathandturner/rhai/pull/120
Send + Sync (https://github.com/jonathandturner/rhai/issues/91 https://github.com/jonathandturner/rhai/issues/95) closed by https://github.com/jonathandturner/rhai/pull/123
in operator (https://github.com/jonathandturner/rhai/issues/124) closed by https://github.com/jonathandturner/rhai/pull/128
export anonymous functions to Rust (https://github.com/jonathandturner/rhai/issues/11) closed by https://github.com/jonathandturner/rhai/pull/128
arbitrary number of indexing levels within a dot-setter chain for assignments (right now only supports one level of indexing) closed by https://github.com/jonathandturner/rhai/pull/144
optimizing the AST to improve evaluation speed and reduce memory footprint closed by https://github.com/jonathandturner/rhai/pull/105 https://github.com/jonathandturner/rhai/pull/108 https://github.com/jonathandturner/rhai/pull/108
modules (https://github.com/schungx/rhai/issues/7 https://github.com/jonathandturner/rhai/issues/122) closed by https://github.com/jonathandturner/rhai/pull/150
indexer support for custom types closed by https://github.com/jonathandturner/rhai/pull/150
custom operators (https://github.com/jonathandturner/rhai/issues/166) closed by https://github.com/jonathandturner/rhai/pull/176
serde support (https://github.com/jonathandturner/rhai/issues/174) closed by https://github.com/jonathandturner/rhai/issues/176
ruggedization - no script should ever be able to panic the whole system (https://github.com/jonathandturner/rhai/issues/102)

checked math https://github.com/jonathandturner/rhai/pull/105
guard against stack overflows due to infinite recursion https://github.com/jonathandturner/rhai/pull/116
guard against infinite loops, limit on operations count https://github.com/jonathandturner/rhai/pull/154
protect against panics during parsing https://github.com/jonathandturner/rhai/pull/156
protect against really deep expression trees which may overflow the stack https://github.com/jonathandturner/rhai/pull/156
protect against over-sized data https://github.com/jonathandturner/rhai/pull/163
check script run progress and ability to force-terminate script run https://github.com/jonathandturner/rhai/pull/154
disable certain language keywords https://github.com/jonathandturner/rhai/pull/176

better documentation (https://github.com/jonathandturner/rhai/issues/37, https://github.com/jonathandturner/rhai/issues/15)

https://github.com/jonathandturner/rhai/pull/105
more cleanup https://github.com/jonathandturner/rhai/pull/108
even more cleanup https://github.com/jonathandturner/rhai/pull/109
use mdbook to convert the README into The Rhai Book

Builder-style API to setup Engine and environment (https://github.com/jonathandturner/rhai/issues/19#issuecomment-593901726) closed by https://github.com/jonathandturner/rhai/pull/176
Unicode Standard Annex #31 Identifiers (https://github.com/jonathandturner/rhai/issues/204) closed by https://github.com/jonathandturner/rhai/pull/205
first-class functions and closures (https://github.com/jonathandturner/rhai/issues/159 )

poor man's OOP closed by https://github.com/jonathandturner/rhai/pull/172
anonymous functions (https://github.com/jonathandturner/rhai/issues/175) closed by https://github.com/jonathandturner/rhai/pull/188
currying closed by https://github.com/jonathandturner/rhai/pull/189
full closures via automatic currying and sharing closed by https://github.com/jonathandturner/rhai/pull/206

Plugins system closed by https://github.com/jonathandturner/rhai/pull/229
benchmarks (https://github.com/jonathandturner/rhai/issues/101)
Rhai playground (https://github.com/jonathandturner/rhai/issues/169)

prototype playground: https://alvinhochun.github.io/rhai-demo

persistence of AST format?  Useful?  It may be easier to just persist the script... - won't fix
++/-- operators (https://github.com/jonathandturner/rhai/issues/30) - won't fix
more numeric literals for different sizes/signed (https://github.com/jonathandturner/rhai/issues/2) - won't fix
try-catch closed by https://github.com/jonathandturner/rhai/pull/265

Oh wow, there's been a lot of neat development that eluded my sight. That's awesome :D I'll see if I can help with some of these in the future!

Kudos to the team that laid all the superb groundwork beforehand!

I'm probably spending way more time on this than I really should... but...
it seems like the language is at a reasonably stable state with most of the low hanging fruits already picked.  To speed up Rhai further will really require some hefty architectural changes, time for which may be productively spent on implementing other useful features instead.
So... what feature do you fancy to be added to Rhai next?
I would probably pick one of the following:

first-class functions and closures
string interpolation (and maybe overhaul entirely the way strings are handled, or mis-handled right now)
threads/fibers/actors?  coroutines?
go-for-it: byte-codes. I profiled a number of benchmarks and it seems like most of the time are now spent in eval_expr and eval_stmt as predicted.  there are no more low-hanging fruits...

Is version 1.0 (or next intermediate semver-incompatible version) a good change to fix Cargo features to be positive instead of negative?

I am still divided on this - on the one hand, it may break a lot of existing code.  On the other hand, it conforms to "standard".
I think I'll let the community ponder it more before deciding to change it for 1.0...

@schungx Personally I would vote for this one:

first-class functions and closures

Even having first-class functions without closures would be very good. This is something I need to make structural data constructions more concise in my project that is using rhai extensively.
I would suggest a syntax in a form conformed with Rust, so something like |x, y, z| (x + y) / z and/or |x, y, z| {let sum = x + y; sum / z}.
Will be happy to help with this implementation if you need more hands. LMK. Thanks!

Actually I've already put in place all the mechanism needed to parse the closure syntax.
The current idea is |x, y, z| expr will create an anonymous function based on the hash of the function body.  Say it is fn abcdefg1234567(x, y, z).  Then it will replace the closure with Fn("abcdefg1234567").
Then other than not being able to capture the running environment, this will looks almost like standard OOP.

Anonymous functions (not closures) support already in, together with the ability to curry a function.

Anonymous functions (not closures) support already in, together with the ability to curry a function.

Full closures with capturing merged in.

And I want to say thank you to @schungx for his great work in development and maintenance of Rhai! Without his help in stabilizing of my prototype and implementing of other related features it wouldn't be possible to deliver this feature that fast.
Rhai in my opinion is the most promising and well maintained embedded scripting project in Rust ecosystem.

Plugins system (powered by procedural macros) merged in.
Thanks to @jhwgh1968

A minor new feature lands: try ... catch statements.
A try block catches most catchable errors, other than non-catchable ones...  well...

Deprecating this list in favor of new feature requests as new issues.

Deprecating this list in favor of new feature requests as new issues.


The Work Items Page in TFS 2018.2 is Missing

The documentation states that the new Work Item pages is available in TFS 2018.2 but I am not seeing it.  Is this feature actually available on premises or cloud only?
https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/boards/work-items/view-add-work-items.md

@scottkuhl - Thank you for your inquiry. The Work Items page isn't available from TFS 2018.2. It will be available with the RC1 release of TFS 2019, now known as Azure DevOps Server 2019. My apologies for the confusion. I'm updating the topic now.

Thanks
Scott

From: KathrynEE<EMAIL_ADDRESS>Sent: Friday, October 19, 2018 3:33:45 PM
To: MicrosoftDocs/vsts-docs
Cc: Scott Kuhl; Mention
Subject: Re: [MicrosoftDocs/vsts-docs] The Work Items Page in TFS 2018.2 is Missing (#2134)
@scottkuhlhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fscottkuhl&data=02|01||92554f2bd937434a714a08d636022b6b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636755780269480532&sdata=6L%2ByKlcOprR7onVdm%2FuDQnmAaeODBNwvTHcZ7LMmIT8%3D&reserved=0 - Thank you for your inquiry. The Work Items page isn't available from TFS 2018.2. It will be available with the RC1 release of TFS 2019, now known as Azure DevOps Server 2019. My apologies for the confusion. I'm updating the topic now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fvsts-docs%2Fissues%2F2134%23issuecomment-431490814&data=02|01||92554f2bd937434a714a08d636022b6b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636755780269480532&sdata=RIMi5aa40d9wpkBQ76yjtMdTkhyGzvVb6huLsuHoU1U%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEQj0HQF1IbyoSlZktulGxeBhdyaKvD_ks5umjcpgaJpZM4Xm3Mq&data=02|01||92554f2bd937434a714a08d636022b6b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636755780269480532&sdata=qZH%2BKucW0jvNmTv3%2BeIKmZ%2FnzktAQwHZgtZMoGijQ8s%3D&reserved=0.


Remove unnecessary console.info

hey @Accir thanks for the fix.
If you'd like to have a small gift in return, please send us a mail to<EMAIL_ADDRESS>We will send you a form with questions about your address and shirt size.


No published analyzer available for language version 2.13.0

Now that we have a 2.13.0 dev release we will need a new analyzer published that has support for that language version.
This causes a warning currently for build_runner users on dev and is making our builds red (https://github.com/dart-lang/build/runs/1881198737#step:5:33).

AFAIK analyzer 1.0.0 reports 2.13.0 as its ExperimentStatus.currentVersion.

Oh ok - thanks! We probably just need to update that then, I will close this and re-open if that doesn't seem to be the case.


backup conflict

We simplified the backup to create only a folder for the day. Now if you backup the same filename again for that day it already exists in the backup and the operation fails.
The simplification is nice but in that edge-case it should still work so we can then fallback to the old approach.

Fixed with PR #223.


Application VM Healthchecking

VM Healthchecking.
Design Doc (@howardjohn): https://docs.google.com/document/d/1G4s_PrmvkwCKoH_kXVeSUAszsaj3ZfpIlraSdeTSPKU
Original PR: #26997
Envoy Health Checks will be in a separate PR.
Need to add Unit tests.
Kubernetes refs:
Prober Entrypoint: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/prober/prober.go#L91
HTTP Prober: https://github.com/kubernetes/kubernetes/blob/master/pkg/probe/http/http.go#L90
TCP Prober: https://github.com/kubernetes/kubernetes/blob/master/pkg/probe/tcp/tcp.go#L50
Exec Prober: https://github.com/kubernetes/kubernetes/blob/master/pkg/probe/exec/exec.go#L48
I tried to more or less mirror k8s here, and it worked for HTTP and TCP. However, for exec, there is a lot of k8s-specific logic I could not mimic. Need @istio/wg-security-maintainers to review to safeguard against arbitrary command execution in Exec.

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test gencheck_istio

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test gencheck_istio

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test gencheck_istio

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-multicluster-k8s-tests_istio

lint_istio
64b14719903ce4a80613cb16477659a8352110f3
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
22bc612940551b0b65f7e6088f7aaacc78ef8894
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4cd83dfcd3b5a8963a63db9f06e4eb8d520710ae
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-telemetry-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-security-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
1c32a00c70587494d8ceea527b5c20e39444b4e6
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

lint_istio
731db08c4a8521d517d15e4a3c2980fa0cc695b7
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

lint_istio
731db08c4a8521d517d15e4a3c2980fa0cc695b7
link
/test lint_istio

integ-ipv6-k8s-tests_istio
731db08c4a8521d517d15e4a3c2980fa0cc695b7
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
731db08c4a8521d517d15e4a3c2980fa0cc695b7
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

lint_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

lint_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test lint_istio

unit-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

lint_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test lint_istio

unit-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

lint_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test lint_istio

unit-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-ipv6-k8s-tests_istio

lint_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-ipv6-k8s-tests_istio

lint_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test lint_istio

gencheck_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
866ec67287cc8a0d5af2564beacc5cb9cfe6b9e2
link
/test integ-distroless-k8s-tests_istio

lint_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test lint_istio

gencheck_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
668e8fc0249f9242f43dbdb90ef50802c453a5b2
link
/test integ-multicluster-k8s-tests_istio

lint_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test lint_istio

gencheck_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

lint_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test lint_istio

gencheck_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
b13cd1c0ceb8448db19ecd1600340c0799b46161
link
/test integ-security-k8s-tests_istio

gencheck_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2b6a9da5bdb5ce4d8046fd1499ee24cd0acdf973
link
/test integ-multicluster-k8s-tests_istio

lint_istio
7356c2ada21b4f5f4f597083472aee39ecc8d848
link
/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.

i have no idea why tests are failing, it only happens once I uncomment https://github.com/istio/istio/pull/27273/files#diff-ebdf1ebc35e7e6b4ac1be116e0808b8dR98. Apparently, ingress&egress gateways fail to build. I dont know why.

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
ba5a48d56e4af8ca0319c03fb0b8d25c9a4c98fb
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-k8s-tests_istio

unit-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-k8s-tests_istio

unit-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-k8s-tests_istio

unit-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-k8s-tests_istio

unit-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-k8s-tests_istio

unit-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
f1d1291033a9ce0de3a5363e339c50ad5fd34f42
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
9c98480e15e38af02d06df7355c66cc36534d45a
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
aa5f6952a458fee32ca94bc5629776a391f67a94
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.

Will give @ramaraochavali @hzxuzhonghu @rshriram @ZhiHanZ a chance to take a look, but LGTM!

/retest

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-ipv6-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-distroless-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-multicluster-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-telemetry-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.

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test release-notes_istio

unit-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
62ce22fd614b8d45d807f9959cff0f2951e12143
link
/test integ-security-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.

can someone add the release-notes-none label to this PR, now that the releasenotes are deleted? @rshriram

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
234517d772a7cfb37005bfc1b559bed86892b0bc
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.

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
d6b0127fbf981b33ae5cdd55091d24ef54778bf9
link
/test integ-multicluster-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.

/retest

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
d6b0127fbf981b33ae5cdd55091d24ef54778bf9
link
/test integ-multicluster-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.

/retest

@adiprerepa: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
d6b0127fbf981b33ae5cdd55091d24ef54778bf9
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.

/retest

@adiprerepa: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
d6b0127fbf981b33ae5cdd55091d24ef54778bf9
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
d6b0127fbf981b33ae5cdd55091d24ef54778bf9
link
/test integ-telemetry-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.

/retest